Comment by sarchertech

I’ve predicted the future and I’ve figured out where vibe coding is going to go based on this article.

1. People are going to come in and vibe code a replacement for some shitty component in a morning. They aren’t going to take time to verify and understand the code.

2. The new code will fix most of the problems with the original component, but it will have a whole new set of issues.

3. People will use AI to fix the bugs, but they won’t take the time to understand the fixes or the regression tests that they tell AI to add.

4. The new system will get so complicated that it’s hard for even AI to work on it. The “test suite” will be so full of tests that are redundant, and nonsensical that the run time will be too high to meaningfully guide AI. And even in the cases where AI does use it, many of the tests are just reimplementing the code under test in the test (Claude does this about 25% of the time based on what I’ve seen if you don’t catch it).

5. Goto 1

This is the same cycle I’ve seen in 90% of companies I’ve worked at, it will just be on a faster cadence.

And that is how we’ll get to a place where we output 100x lines of code, and spend 2x developers salaries on tokens, with little meaningful impact on the outside world.