Software Development

Anyone Can Prompt. Not Everyone Can Engineer. What the AI coding revolution actually changes, and what it doesn’t. The Translation Layer Is Gone I recently watched an IBM video that made a point I’ve been thinking about ever since. The speaker walked through the entire history of programming languages, from machine code and assembler, through COBOL and FORTRAN, to object-oriented, web, and scripting languages, and made a simple observation: every generation moved a little closer to the way humans actually think and speak. ...

In the previous post, I argued that defining decision boundaries is necessary if we want judgment to survive in an AI-accelerated development environment. When execution becomes cheap, the number of decisions explodes. Without clarity around who decides what, speed simply amplifies risk. But defining boundaries alone is not enough. The next question is more practical: how does work actually flow through those boundaries? How does an idea move from a conversation with a customer to something running in production, while AI accelerates the process without collapsing responsibility across roles? ...

Early in my career, coming from industrial engineering, I learned a simple rule that has shaped the way I think about software development ever since. Software may look abstract, creative, fluid. But underneath, it behaves like a production system. The best articulation of this idea appears in The Goal by Eliyahu M. Goldratt, one of the most influential books I have ever read. In production, every system revolves around three outputs you can influence: ...