Git

Yesterday I wrote a commit message with Claude Code. The diff was a one-line change: a typo in a comment. Claude Opus read the diff, thought for two seconds, and generated fix: correct typo in auth comment. That consumed about 800 input tokens and 30 output tokens, at $15 and $75 per million respectively. Cost: a fraction of a cent. But multiply that by 40 commits per day, 250 days per year, across a company with 200 developers using coding agents, and the fraction of a cent becomes thousands of dollars spent on the intellectual equivalent of applying band-aids. ...

I currently have three Claude Code sessions open. One is translating blog posts. Another is writing tests for a CLI. The third is helping me debug a data pipeline. Each one runs in its own worktree, each one in its own Ghostty split, while I jump between them using Cmd+Alt+Arrow. I haven’t opened iTerm2 in months. I haven’t touched tmux in weeks. Everything lives in a single Ghostty window. Is it the perfect setup? No. Is it the most productive setup I’ve ever had? Absolutely. ...

If you’ve read my post about worktrees in Claude Code, you know the key to parallel workflows is a simple flag: --worktree. Run it, and you get an agent working in its own isolated repo copy. Launch three, and you’ve got three agents working in parallel without clashing. Magic. Now you open Codex CLI, look for an equivalent flag… and it doesn’t exist. There’s no --worktree. No --tmux. No isolation: worktree for custom agents. Issue #12862 has been open on GitHub asking for exactly this, with community members proposing their own implementations in forks, but nothing has been merged. Native parallelism for Codex CLI doesn’t exist — not yet. ...

A few weeks ago, I wrote about git worktrees — what they are, how to create them, and why they’re better than cloning a repo three times. The basics. But the basics are only half the story. Because Claude Code doesn’t just work with worktrees — it has native support for them. Dedicated flags, automatic isolation, integration with tmux. And the difference between knowing worktrees exist and knowing how Claude Code uses them is like the difference between having a car and knowing it has sport mode. ...

107 commits. Impeccable conventional commits from day one. Feat, fix, refactor, chore — everything perfectly labeled. And the CHANGELOG? Empty. Non-existent. A file that “I’ll write tomorrow” for two months straight. If this sounds familiar, you’re not alone. Writing a changelog by hand is an Olympic-level pain in the ass. It’s not that it’s difficult — it’s just tedious, repetitive, and there’s always something more urgent to do. And that’s exactly why git-cliff exists. ...

The Single Checkout Bottleneck I’m developing a macOS menu bar app. I have three features in the backlog: a consumption sparkline, native notifications, and a desktop widget. All three are independent. I’m building all three with Claude Code. The problem: Claude Code works in one directory. One directory has one branch. And git checkout is like a single-lane roundabout: only one gets through. If I want to advance all three simultaneously, my classic options are: ...

5 minutes. That’s how long it took. A security researcher publishes an AWS access key on a public GitHub repository. They do it on purpose, as an experiment. Five minutes later, someone was already using it to mine cryptocurrency. Five. Minutes. There are bots scanning GitHub 24/7 looking for exactly that: exposed credentials. And they’re fast. Much faster than you realizing you screwed up. The numbers are scary According to GitHub, 39 million secrets were leaked in public repositories in 2024. A 67% increase from the previous year. ...

The awakening of slowness You’ve been working on your data science project for a while. You have twenty notebooks, a few images, and the typical folder structure that seemed like a good idea three months ago. You run git status to see what you’ve changed and… you wait. And wait. And while you wait, you have time to wonder if the computer froze or if it’s just contemplating life. Spoiler: it’s not contemplating. It’s suffering. ...