The rate limiting command provided by redis-cell is now available in DragonflyDB.

Thoughts on whether it’s possible to get most of the value from RFC-driven engineering, but save on the committees and heavy process.

When I’m working on a feature or refactor, I often leave @todo comments to remain in flow and deal with other points later.

I don’t mind committing them to my feature branch, as long as I work them away before merging in.

On large branches, it can be easy to forget about that todo I left in there a few days ago.

class PodcastController
{
public function process(Podcast $podcast): void
{
$podcast->process();
// @todo Broadcast event to trigger webhooks
return $podcast;
}

Before I merge, I pipe git diff into a grep call to scan for changes that include @todo.

git --no-pager diff main..feature-branch | grep -i "^\+[^$]*@todo"

+ // @todo Broadcast event to trigger webhooks

Highlights

• I left the country for two weeks, and TinyPilot ran smoothly without me.
• A pipe burst in the TinyPilot office, leading to a near-disaster.
• I’m searching for the right balance between reactive and proactive work.

Goal grades

At the start of each month, I declare what I’d like to accomplish. Here’s how I did against those goals: