Stack · Published 2026-07-27 · 1 min read
ADHD coding
I rarely hold forth on vibe coding in general: your feed is full of general reasoning about it without my help. Setting the supporters aside and looking only at the critics, I see two categories.
Category 1: architecture
A developer asks a model to write some code. The model writes it. The developer opens the result, does not recognise their own architecture in it, and writes a post about how vibe coding does not work.
Category 2: bugs
The code was run, some of the bugs remained. Same conclusion.
Vibe coding is being measured with a software development ruler. Inside that frame it really does lose. For now.
What I think
Vibe coding is not a replacement for development. The gain appears when you apply it not to code in isolation, and not even to the product, but to the whole process: development, testing, growth, user acquisition.
I like how it is done in Nikolay's channel. To my taste that is the best attitude to vibe coding, and the one closest to mine. Today he is making an animation for an app. Tomorrow, a site that brings in free organic traffic.
ADHD here is not a diagnosis but a mode of working. In that sense Nikolay caught the right vibe.
Subscribe: @sexyllm
Not an ad. I genuinely like Nikolay's channel.