Claude Code in your CI/CD pipeline
Claude Code isn’t just for your terminal. Plug it into your CI/CD pipeline and it reviews every PR, catches issues before merge, and enforces your team’s standards automatically.
Multi-agent development: three AI agents, one feature
A single AI agent loses context after a few hours. Three specialized agents — a planner, a generator, and an evaluator — hand off structured artifacts and keep going. Anthropic’s three-agent harness changes how autonomous coding works, and .NET developers should pay attention.
The LLM Wiki: Karpathy's pattern for compounding knowledge
Andrej Karpathy dropped a GitHub Gist that got 5,000+ stars in days. Not a framework. Not a library. An idea file. Here’s what the LLM Wiki pattern is, why it’s different from RAG, and what it means for developers who use AI agents daily.
Computer Use: Claude Code controls your screen
Claude Code can now control your screen — opening apps, clicking through UI, taking screenshots. No Playwright setup, no test harness. Just tell Claude what to check and watch it work. Here’s how Computer Use works and why it matters for .NET developers.
Scheduled Tasks — Claude Code keeps working while you sleep
Claude Code can now run prompts on a schedule — from quick polling in a session to fully autonomous cloud tasks that run while your laptop is closed. Three scheduling options, one goal: automate the work you keep forgetting to do.
What Claude Opus 4.6 means for your .NET code
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.
Auto Mode — the end of approve, approve, approve
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.
Git worktrees with Claude Code
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.
From code writer to software architect
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?’
Multiple Claude Code sessions at once
One Claude Code session is powerful. Two or three running simultaneously, each focused on a different part of your solution? That’s a multiplier.