olafalders.com

Dependabot’s defaults can make it look like an agent of chaos. Here’s how cooldowns, dependency groups, and a Claude skill turn down the churn — fewer rebases, boring CI, and a few extra days for the world to flag the bad actors.

Notes from an informal Zoom session where developers shared AI tools, automation techniques, and projects. Topics included using Claude in headless mode to manage version bumps across 20+ packages, an overnight bot that processes GitHub issues and responds to PR comments, the “Talk About Us” copy-auditing skill, and a lively debate about whether the future of development is writing specs rather than code.

It’s easy to fall into a trap of using jargon when discussing what you’re working on. Sometimes we need help expressing our thoughts in interesting and meaningful ways—using our own voices, in a way that’s memorable and repeatable. A blog post by Anil Dash helped me rethink my writing. I’ve turned those principles into an AI skill, so you can try it too.

I rarely use git-bisect, but thinking about it has changed how I structure my commits. The principle is simple: don’t break git-bisect. If a change breaks something, the fix should belong in that same change. This mental model helps avoid common anti-patterns like splitting a bug fix into two commits—one with a failing test, one with the fix. Even if you never run bisect, thinking “would this commit work in isolation?” creates a provably linear set of working changes rather than an aspirational attempt at correctness.

On getting a more readable $PATH, installing “is” in GitHub Actions and using $GITHUB_STEP_SUMMARY to put it all together.

When multiple versions of the same executable exist in your $PATH, the ‘is’ utility provides a clean way to discover all versions and their locations. This post demonstrates how ‘is’ can help identify version conflicts, clean up redundant installations, and streamline executable management with tabular and JSON output formats.