Operations | Monitoring | ITSM | DevOps | Cloud

Merge conflicts rarely make it into a sprint retrospective, but they should. They’re one of the most reliable ways to lose an hour of flow without anyone noticing it’s gone. Every developer expects them eventually, but almost nobody questions the workflow around resolving them.

GitBench is our attempt to see how well LLMs handle git-specific tasks. We put together a suite of 17 benchmark categories with a total of 204 specific test cases. We ran these benchmarks against 43 (and counting) different models with all of their supported effort/reasoning levels.

This minor update has a one big new feature.

Since I started using Claude Code more frequently, I kept noticing a “worktree” checkbox popping up whenever I started a session in a Git repository. I had no idea what it meant, so I did what any curious developer would do and started digging. What I found was a Git feature I somehow never came across before: git worktrees.

From plan to main. Software is no longer just a tool. It is the infrastructure of modern life. Software keeps airplanes in the sky and power flowing into our homes. It helps doctors save lives, scientists discover cures, farmers feed cities, and astronauts navigate space. It powers economies, protects supply chains, and connects billions of people across the world. Every major system humanity depends on now depends on software. Which means developers are no longer just building applications.