Thinking in public
Notes on how AI changes operating models, why APIs become business capabilities, and what helps product and engineering organisations move faster.
By now even the skeptics reluctantly accept that it's indisputable that vibecoding / AI-assisted coding makes it much faster to ship software. But it's equally true that the speed does not make the value last. I'd argue it makes it easier to chase the wrong goal because "it's so easy to progress"
A long time ago, way back when I still had hair, Microsoft introduced Team Foundation Server and one of the productivity metrics commonly reported on was lines of code written per developer. At the time, it seemed like a relevant metric. More code meant more output, no?
A little over a year ago I shared a presentation internally with our CEO, execs and other stakeholders urging action as AI was rapidly accelerating the time to market for new products, creating a threat to incumbents. I outlined several moats I believe we could exploit and I still believe they are valuable space to occupy - for example domain knowledge, compliance capabilities, massive datasets. I did miss one key moat that hindsight allows me to appreciate more fully: Distribution.
If you thought coding was just about clean architecture and efficient logic, vibecoding would like a word (preferably in monospace font, glowing in soft lavender neon, backed by a lo-fi beat). What started as an aesthetic subculture blending programming with mood, visuals, and audio has morphed into something weirder, richer, and more creative.
