[distalx]

Vibe Coding is accelerating the death of documentation and architectural clarity. Companies are measuring success by tokens generated and time-to-prototype, ignoring the massive, hidden cost of cleanup/maintenance.

The real skill is now cleanup, not generation.

[baq]

The real skill is guiding generation carefully so the generated software isn’t crap. Some people here see Claude code and think it’s state of the art, whereas for best results you need a much more involved process.

It isn’t that different from any other form of engineering, really. Minimize cost, fulfill requirements; smarts-deficient folks won’t put maintainability in their spec and will get exactly what they asked for.

[distalx]

I bought into that idea a month or two ago, that more control and detailed instructions would deliver a clean result. That just led me down a rabbit hole of endless prompt re-runs and optimization loops. Many time I thought I had the final, perfect prompt, the next iteration slightly worsened the output. And sometimes the output was the same.

The last 20-30% of precision is brutal. The time and tokens we burn trying to perfect a prompt is simply not an optimal use of engineering hours. The problem is simple: Companies prioritize profit over the optimal solution, and the initial sales pitch was about replacement then it changed now its all about speed. I'm not making a case against AI or LLMs; I'm saying the current workflow, a path of least resistance means we are inevitably progressing toward more technical debt and cleanup at our hands.

[jplusequalt]

Let me know when aerospace engineers are letting an AI build their planes for them.

[bethekidyouwant]

https://uwaterloo.ca/news/math-innovation/pioneering-future-...

[jplusequalt]

That's an incredibly dishonest reading of my comment. Using ML to build simulations is different than letting an LLM build the plane for you.

[PinguTS]

How is it the death of documentation?

You can start off just with documentation and then in the process check if the code is still in line with the documentation.

You can also generate documentation from the code. Then check yourself, if it fits.