Things worth writing down

Auditing a large code estate for compliance has always been priced out of reach. I ran one with Claude Code across more than 300 repositories. The interesting

Legacy Modernization

I once proposed strangling a PHP front end endpoint by endpoint behind a pass-through layer. Most of that plan was scaffolding built to be thrown away. If

Technical Leadership

Scrum tells developers to self-organise while the business around them stays fixed. Nobody in the framework can overrule a bad technical decision. Governance

Most teams say they run Scrum because it is the best known name, not because it fits. Each process comes with its own brake on overcommitment. Run one under

An agent that has spent an hour building something stops reading the requirement as a requirement and starts reading it as a description of what it built. Here

Every project rescue reaches a point where the evidence leads to a person, usually someone respected. How you name them decides whether anyone listens, and

Boris Cherny's five archetypes describe how roles are collapsing in AI-native teams. They fit solo work well. On shared, established codebases the picture

.NET Aspire earns its keep on multi-service .NET projects with mixed dependencies and junior-heavy teams. It is a compile-time, type-safe alternative to Docker

Fractional CTO Insights

Most commentary on AI and financial markets focuses on the productivity upside. Corporate earnings, margin expansion, efficiency gains. That story is probably

Junior developers adopting AI tools face a specific risk: they accept plausible-sounding output before they have the instincts to push back. Here is how I

Some architecture decisions have linear consequences. Others compound. Which early choices constrain what's economically possible later, and why the decisions

If you are the senior on a fixed engagement with a junior-heavy team, your real deliverable is a team that can reason about the architecture without you. Here