Productivity

You get a feature request. Maybe a ticket, maybe just a Slack message. You open your IDE, create a branch, and start building. Claude Code writes the code, you review it, things move fast. Then, three hours in, you discover you’ve made five architectural decisions you never consciously made. The subscription entity is attached to the User because Claude assumed that. The tier check happens in the controller because that’s where it fit. There’s no audit trail because you never said you needed one. ...

Boris Cherny ships 10–30 pull requests a day and writes essentially zero lines of code by hand. That number spread across developer Twitter in January 2026, and since then I’ve watched teams respond in the worst possible way: spin up ten Claude sessions, produce ten times the chaos. The workflow matters. What makes it work is not the session count. Why this is worth your attention Cherny created Claude Code and leads it at Anthropic. Before that he was a Principal Engineer at Meta. He is not a productivity influencer who dabbled with AI for a week — he built the tool, uses it at extreme volume, and has been candid about what actually drives the numbers. ...

Eight days after publishing a guide to tuning Claude Code, a single week of releases — Claude Fable 5, a one-flag safe mode, Stop hooks that talk back, and guardrails that used to be your job — forced a re-tune. Here’s the delta, mapped onto the same layers, and what we changed in our .NET codebase.

Out of the box, Claude Code treats every repository the same. The difference between autocomplete and a coworker is configuration: layered memory, deterministic hooks, skills, MCP servers, and worktrees. Here’s how to build each layer — and how we applied it to a large .NET codebase.

What does it actually look like to build a real feature with Claude Code? Not a toy example — a complete ASP.NET Core feature from ticket to PR. Here’s the full walkthrough.

Opus 4.6 is now the default model in Claude Code. With 1M tokens of context and an 80.8% SWE-bench score, it’s the biggest single-generation jump yet. Here’s what changes for .NET developers.

Every Claude Code user knows the drill: approve the file edit, approve the build command, approve the test run. Auto Mode replaces that click-fest with a background safety classifier — so you can actually focus on building.

You’re deep in a feature branch. An urgent bug comes in. Instead of stashing, switching, and losing your flow — you open a second directory and keep going. Git worktrees make this possible, and Claude Code makes it powerful.

I write less code than ever. And yet I’m more productive. The question is no longer ‘how do I implement this?’ but ‘what should be built here and why?’

One Claude Code session is powerful. Two or three running simultaneously, each focused on a different part of your solution? That’s a multiplier.