Hacker Newsnew | past | comments | ask | show | jobs | submitlogin
Even as a fast dev, I wasn't fast enough for my ideas. Then came Vibe Coding
2 points by derverstand 73 days ago | hide | past | favorite | 8 comments
The Speed Trap of Modern Dev

I’ve always been a fast developer. I know my stack, I know my shortcuts. But there was still a painful latency between my mental architecture and the screen. My ideas always outpaced my output. No matter how fast I typed, the "Implementation Friction" was a tax on my creativity.

The 10x Shift: Moving at the Speed of Thought

Vibe Coding didn't just make me "better" — it removed the mechanical bottleneck. I’m no longer translating thoughts into code; I’m describing the vibe of the system and watching it manifest.

The Result: I’m building things alone that previously required a dedicated team or a month-long sprint.

The High: The dopamine hit isn't just about "it works." It’s the rush of zero latency. It's the feeling of your brain being directly plugged into the compiler.

The "Dark Side" of Hyper-Flow

But here’s the rub: When you remove the friction, you remove the "sanity check."

The Addiction: The feedback loop is so fast that it becomes a slot machine. Each prompt is a pull of the lever. Because I'm fast, I can pull that lever 100 times an hour.

The Loss of Friction: Typing was a form of "slow thinking." It forced me to vet my own architecture while my fingers moved. Now, I’m building at the speed of light, but am I outrunning my own ability to reason about the system?

The speed is a drug, and I'm fully addicted. For the first time in my career, my output matches my imagination. But as the friction of implementation hits zero, the value of 'knowing how to code' is being replaced by the value of 'knowing what to build.' If you could manifest any system in an hour, would you actually know what to build, or would you just get lost in the 10x dopamine loop of pure iteration?



Shouldn't even be typing code while planning. There's no software idea that needs to be coded as it's planned. It's just a waste of time, and potentially harmful. The devs I've worked with that "think" in classes, or tables, or whatever code structure they're most comfortable with, inevitably end up creating garbage in the first 10 minutes that ends up lasting the lifetime of the project, confusing the hell out of everyone that looks at it, including themselves a week later.


This reads like it was written using a prompt.


In the software business for over 40 years. I never thought serious programmers would use words like "describing the vibe" and "watching it manifest." Or to see pseudo-meaningful phrases like "dopamine hit" and "hyper-flow" in an article about programming.

The humblebrags alone turn me off: You think too fast and have too many ideas pouring out of your "speed of thought" brain. Mere software design and coding impose "drag" and "friction," like a shark forced to swim in mud with the rest of us with less-hyperactive minds. Lay off the Adderall.

I raised three kids. Children go through a period of intense curiosity where they try to make sense of the world, ask what feels like a hundred questions an hour, and present random thoughts and ideas and theories at the "speed of thought," or a speed faster than an adult can pay attention. I think of that as fun and charming with children, not aware of what they don't know, and interpreting their random theories as novel ideas. Then they grow up and learn to focus their mental faculties, and with some luck and skill discern signal from noise.


"Don't be curmudgeonly. Thoughtful criticism is fine, but please don't be rigidly or generically negative."

https://news.ycombinator.com/newsguidelines.html

Also, please don't cross into personal attack. That is in no way allowed here.


@dang I appreciate the tireless and thankless work you do in HN, sincerely, but I don't always agree.

> Don't be curmudgeonly.

I feel flattered to get identified as a curmudgeon in company with Socrates, Samuel Johnson, Mark Twain, and George Carlin. I might take offense at the implicit ageism but at my age I roll with it. HN teems with unchallenged insults directed at the elderly, grating on us old people, but in line with the HN demographic.

> Thoughtful criticism is fine, but please don't be rigidly or generically negative.

No one can "be" those things since that implies an identity. One can write in a negative tone. Accusations of rigidity and genericity would require a large sample. No one who knows me would describe me as "rigid or generically negative" so I will let that go as an ignorant judgment.

> please don't cross into personal attack.

Refuting the OP's claims can't count as personal attack, unless we hollow out all argument and rhetoric. I apologize for the Adderall comment, should have left that out.

> That is in no way allowed here.

Ironic given the personal nature of the moderator scolding, attacking my age and identity by telling me what not to "be."


I realize it's a distinction without a difference in this case, but the reason that guideline says "Don't be curmudgeonly" as opposed to "Don't be a curmudgeon" is precisely to avoid giving the impression of labeling the person themselves. It's a transient quality that anyone can have. But I get that it didn't land that way and I'm sorry.

Actually you put it quite nicely when you say: "No one can "be" those things since that implies an identity" - I quite agree, and that's exactly what that guideline was trying (but evidently failing) to avoid. To my ear it sounds analogous to the "Don't be snarky" guideline. If I say I was "being" snarky at a certain moment (or impatient or rude or what have you), it doesn't follow that I "am" a snarky (etc.) person. That's how I meant it anyhow - I hear your point and do not mean to persuade you out of it.

The Adderall comment was the worst bit, but 'You think too fast and have too many ideas pouring out of your "speed of thought" brain' was also crossing into personal attack, and so were the last two sentences comparing the other person to a child that failed to grow up. The trouble is that these sorts of swipes accrue like mercury in the bloodstream and the ecosystem can only handle so much.


@dang Thanks for the thoughtful reply. I abandoned all other social media years ago, I stick around on HN largely because of the moderation.

You probably know that I did not actually feel insulted or attacked. One of the few advantages of getting older: I care less and less what people appear to think about me, or what they say. And I don't think you intended insult. I alert at language using forms of "to be," to the annoyance of people who argue with me.

I understand how my comment can read like a personal attack, and I could have interpreted the OP more generously, or kept my mouth shut. I will try to do better. Something about the "I have too many ideas popping into my head" and "I think too fast" -- posted daily in one form or another, or spouted in co-working spaces, sets me off. My problem, which I will blame on cognitive decline and general feeling that I have reached the end of my road in the tech industry.


You’re fair to call out the wording. I agree some of it reads more buzzword-y than intended.

My point wasn’t that thinking fast is inherently good or that coding is “drag.” Quite the opposite: the friction of implementation used to be a form of thinking time for me. Typing forced pacing and reflection.

What I’m noticing now is that when iteration becomes extremely cheap, the bottleneck shifts from “can I build this?” to “should I build this?” That’s not about hyperactivity. It’s about decision quality.

The “dopamine” part wasn’t meant as a brag but as a caution. Fast feedback loops can encourage shallow iteration instead of deeper design if you’re not careful.

So if anything, I’m arguing for more deliberate thinking, not less.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: