AI didn't change the economics of software engineering
AI made writing code faster, but the real economics of software engineering were never about typing code in the first place.
AI made writing code faster, but the real economics of software engineering were never about typing code in the first place.
LLMs are built for conversation, not incantations. The value isn't in your opening message, it's in the back-and-forth: clarifying, correcting, refining. Iteration is cheap. The conversation is the work.
Founders juggle endless demands, investors, sales, suppliers, and employees, all while building the plane mid-flight. But with engineering often being your biggest expense, there's one responsibility you can't delegate: ensuring your team builds the right thing.
AI won't make software engineers redundant. It will expose what engineering was always supposed to be about: understanding systems, not just writing code.
Here's part one of a post I shared with our team on the radical change and evolution of our jobs. AI won't make software engineers redundant. It will expose what engineering was always supposed to be about: understanding systems, not just writing code.
Reflecting on whether teaching traditional coding skills still makes sense in 2026. Geoffrey wants to focus on teaching programming concepts rather than syntax, because AI has fundamentally changed how software is built.
By 2030, nobody will write code anymore and here is why. The difference between agent-powered engineers and those who handcraft code is huge. Here's our prediction on software engineering.
Go for one codebase or multiple repositories? A question multiple CTOs and technical founders have asked. It can be a surprisingly expensive decision nobody warns you about.
LLMs generate code on demand, but they do not replace maintainers, communities, or years of shared learning. This piece explores how AI-assisted coding risks fragmenting logic, increasing technical debt, and slowly eroding the open source ecosystem.