I said code review was dead. Here’s what I got wrong – and right

The response to my original piece about killing the code review was loud. This is my attempt to address the comments.

The response to my original piece about killing the code review was loud. This is my attempt to address the comments.

Teams that treat AI as a code printer will drown in slop and debt. Those who become the best at specifying what they want and verifying that they got it will get the promised 10x productivity boost.

AI coding agents work in isolation. Multiplayer AI coding uses shared specs so teams and their agents stay aligned across sessions and roles.

What's actually working, what’s still vaporware, who should be paying attention, and what the real path forward looks like for teams that want to be ready when orchestration goes mainstream.

Signals from the Hangar DX community on how AI is changing software engineering.

We explored how developer experience is evolving and how AI is reshaping what it means to be an engineer.

Comparing two ways of completing the same upgrade: migrating a Node.js 14 project to Node.js 18 by chatting with an AI assistant and performing the same migration through a spec-driven development approach, with a strict, pre-written plan.

Spec-driven development is not a choice but a necessity as we move from vibe coding a cool app to building real-world brownfield projects.

Building software with AI agents isn’t a solo sport, especially when projects touch multiple repos, services, and prompt engineering knowledge.

Runbooks capture context from repositories or code reviews, combine it with the team's AI prompting knowledge and get smarter with each use.

AI is a developer productivity force multiplier, but poor documentation, unclear ownership and fragmented tooling don’t magically disappear with AI.

Developers’ workflows are fragmented, knowledge is siloed, ownership unclear, and coordination work is eating away at the time saved by AI.

Powered by WordPress