Responsibility doesn't scale
Output can be parallelized, understanding can't. Why organizations are quietly converting responsibility into risk right now — and why it only surfaces when something breaks.
Blog
On technical responsibility, existing systems, and software that has to hold up in real operation.
Output can be parallelized, understanding can't. Why organizations are quietly converting responsibility into risk right now — and why it only surfaces when something breaks.
When mere execution proves nothing anymore, how does anyone still recognize you? On professional identity you've rented — and the one decision that's left to you.
As standardized implementation accelerates, consulting can no longer justify itself through headcount. The valuable part is responsible engineering.
AI code looks clean. But whether it fits the system can't be seen in the diff — only when you know what to check against.
Scrum measures progress in completed tasks. But what if the real bottleneck isn’t delivery — it’s the decisions your team isn’t making?
AI didn't take away the hard work. It took away the easy work and left only the hard part behind.
When everything is cheap to build, the most expensive thing will be deciding what not to build.
The bridge into the AI era leads from mere execution to technical responsibility — with code as evidence.
What happens to time-boxed processes when implementation accelerates and decisions become the bottleneck?