Blog
Insights on AI-driven development, from getting started to orchestrating the future
Run Ollama in Docker: a local fallback for your AI orchestration stack
Why your stack needs a local fallback The case for a local model isn't that it beats the frontier. It doesn't. The c...
GPT-5.5, Opus 4.7, or both: the new model decision
Eight days separated Opus 4.7 (16 April) from GPT-5.5 (24 April). Two vendor pages. Two leaderboard claims. Three gro...
The MCP audit checklist your team needs this week
Last week we wrote about what MCP gives you. This week the question is what you give up. The two are the same protoco...
What you actually buy when you adopt MCP
You've been hearing about MCP for nine months. Someone on your team has installed three servers from a list. Someone ...
The Conductor's Map: Why Graph Curation Is Your Next Core Skill
You wrote a CLAUDE.md file that describes your project's stack, conventions, and architecture. You maintain a doc tha...
Your Codebase Is a Graph: Start Treating It Like One
You read "context is everything" eight months ago. You started writing better project docs, curating your CLAUDE.md f...
The Four Behaviours That Separate AI-Fluent Developers
You installed the tools. You watched the tutorials. You've been using AI for months. So why does it still feel like y...
From Prompt Engineering to AI Orchestration
Remember when "prompt engineering" was the hottest skill on LinkedIn? When people charged thousands for courses on ma...
Your First Hour with Claude Code
You've heard the hype. Developers shipping entire features in minutes. Codebases refactored overnight. But you opened...
The Coductor Manifesto
Software development is being rewritten. Not by AI, but by the developers who learned to wield it. We are those deve...