AI on Sander Knape

The Organization of the Future: Smaller Teams, Harder Constraints

Tue, 07 Apr 2026 09:00:00 +0000

The first post in this series argued that AI is moving engineering up the stack, away from implementation and toward systems, architecture, and governance. The second argued that this changes what engineers do: judgment replaces implementation as the primary constraint, and the best engineers become orchestrators rather than builders.

The third question—the one boards and executive teams most need to answer—is what this means for how engineering organizations are designed.

It’s not mainly a question of how many engineers to hire, or which AI tools to buy. It’s a structural question about how organizations produce, govern, and sustain software at all.

The Engineer of the Future: From Builder to Orchestrator

Tue, 07 Apr 2026 08:00:00 +0000

The previous post argued that AI is moving engineering up the stack, shifting effort from writing code to designing systems and governing software in production. That has implications for strategy and organizational design. But it also changes something more personal: what it actually means to do this job.

If implementation is no longer the constraint, what is? My argument is judgment. And if judgment is the constraint, the engineer’s role has to change around that.

Engineering Is Moving Up the Stack

Tue, 07 Apr 2026 07:00:00 +0000

The debate about AI and software development is stuck on the wrong question.

Most discussions ask whether AI writes good enough code, whether it matches human craftsmanship, whether it introduces bugs, whether developers can trust it. Reasonable questions. Increasingly beside the point.

The shift that matters more isn’t about code quality. It’s about where engineering effort is required at all.

AI is moving engineering up the stack, from writing code to designing systems to managing the lifecycle of software in production. The work doesn’t disappear. It shifts upward, toward broader and more structural concerns.