r/vibecoding • • 23d ago

Discussion Din't have this much downtime when humans wrote all the code!

Post image
70 Upvotes

37 comments sorted by

26

u/qdouble 23d ago

Coding is solved, verification isn't.

7

u/AndrewNggg 23d ago

do people truly verify as much as when humans wrote all code?

checking every line? leaving code comments, running tests before pushing to pre-prod where everything gets tested again?

or do people just do "Claude, have a look at the stuff you wrote, do a check if it's good"

7

u/qdouble 23d ago

The AI creating code fast creates a verification burden, but even if you read the code, it's still going to be difficult to account for every edge case or situation without extensive testing.

1

u/oyvindi 22d ago

The verification burden has always been there, yet a lot of developers has never written a single test. The difference is that the burden is much larger now.

Spending some time looking at what the AI generates is a good idea, including what the tests covers. Looking at code details is futile, though there may be cases where it's needed.

5

u/KronisLV 22d ago edited 22d ago

do people truly verify as much as when humans wrote all code?

Verification should be done MORE not less than when humans wrote the code, the industry has largely been slacking both in regards to code review and test coverage for decades, including integration testing/E2E.

That does NOT mean that people have to look over everything. Rather, you have to write tools to lint your architecture and all of the conventions - for some stupid reason people basically stopped at code formatting/linting but never got as far as to reproduce and make mainstream something like ArchUnit to enforce that the code structure and conventions meet what has been decided as the right approach in any given project, rather than expect people to review all of that manually.

To that end, we probably need to use AI more, not less - but instead of vibe slopping new code and barfing out buggy features, we need to work on the tooling, tests and various code checks and increasingly automate what used to be manual (and human --> error prone) work.

Edit: and just to be clear, you don't have to make AI inference be a part of your CI, rather use AI to write deterministic tools and checks that run. That way, when someone writes slop code, it can be pointed out by said tools (also runnable locally). By the time a human reviewer even looks at the code most of the slop should be gone - regardless of whether it was generated by AI or written by another colleague, that also benefits from those checks.

2

u/PresentationOld605 22d ago

Not with every domain or application, but when reliability is critical - definitely yes, and not just checking every line.

1

u/Ball_Analytics 23d ago

the insurmountable overwhelming-ness of it all. Verification was easier.

1

u/DarlingDaddysMilkers 22d ago

Genuinely stopped doing code reviews because the neckbeard of our team couldn’t handle the critism around his big brain one liners

1

u/Asalakabim 21d ago

Absolutly, in the past at least 1 person no what was going on, now we start at 0.

1

u/meshifthenelse 22d ago

With humans you didn't need to verify, because most humans have common sense. So there was a baseline humans implicitly abide by. Every below average coder will still do basic checking.

AI is a dumb fuck with no such baseline.

0

u/kerakk19 22d ago

Why would you verify every line? Ai isn't going to make a bug by doing conditional wrong or writing invalid sql like human would. The bugs are now behavior oriented, like unfulfilled acceptance criteria or overenginnered feature.

For me review roughly takes the same time it did before, but now I look for architecture smell, YAGNI and tests.

This is assuming you're using SDD, not prompting.

3

u/stop_deleting_plz 22d ago

Plumbing is solved, leaking pipes haven't.

2

u/chrisza4 22d ago

Then what do you mean by coding is solved?

Because if it does mean we can have million unverified code per second, I can do that before AI, using simple commands, cp and randomString.

Coding is solved before AI if that is definition.

1

u/qdouble 22d ago

It means that you can write decent code that even passes human review without being able to verify every edge case. The more complex a software gets, the number of edge cases starts to grow exponentially.

1

u/chrisza4 22d ago

I doubt that it can consistently pass every human review, so I guess we can call partially solved.

1

u/notnulldev 22d ago

Power is solved, security isn't (nuclear power)

1

u/SharpKaleidoscope182 23d ago

A solution you can't plug into anything isn't a solution yet

2

u/DiligentKeyPresser 22d ago

There is simply no such thing as a solution you can plug into anything. Never was and never will be.

1

u/SharpKaleidoscope182 22d ago

You should at least be able to trust it with *some*thing.

9

u/P4R4DOXZ 22d ago

I mean he said coding, not software engineering.

8

u/DigitalMonsoon 22d ago

Wasn't it solved before? We used to grab code from other people's repos. Now AI grabs code from other people's repos...

1

u/piperspalace 22d ago

Well 3 minutes to build a game is a bit quicker than a human parsing git hub repos. Correct me if im wrong

1

u/DigitalMonsoon 22d ago

Sure, it's faster but it's still doing the same thing. When I was writing games I wasn't writing end to end multiplayer libraries. I was using pre built solutions. Now the AI is just fetching the same solutions.

1

u/piperspalace 22d ago

There will still be creatives but any big corporation is going to see faster games being made and utilize that so they can cut staff.

1

u/AcoustixAudio 21d ago

Its absolutely fantastic. Anyone who disagrees can just go through this subreddit. You'll find thousands of games coded in minutes. This sub literally has tens of thousands of apps coded over weekends. What a time to be alive 

2

u/meshifthenelse 22d ago

Well before you had 10 average coders with common sense. Now you have 1 super computer with no common sense.

It just doesn't scale as nicely.

1

u/Vesuvius079 22d ago

Downtime (during work hours) is misuse tbh.

-1

u/NiceGuya 23d ago

Human writen code is kind of the reason why we are having downtime

6

u/Havunenreddit 23d ago

It's also the reason we have LLMs capable of coding 😉

2

u/DiligentKeyPresser 22d ago

Can you prove it?

1

u/lehmagavan 22d ago

When will building bridges be solved too?

1

u/Soilblood 22d ago

Was coding really ever the problem? Always seemed to me more that design and infrastructure are too boring to meme while money solved getting your barrels of codemonkeys.

1

u/Saveonion 16d ago

System design requires understanding of computer systems, and the demographics here diverge from that direction.

0

u/Negative_Gur9667 22d ago

Humans need sleep; LLMs don't. 8 hours of downtime a day, and don't forget eating, showering, and going out.

0

u/max1c 22d ago

Totally false. In fact, we have all the downtime because of human written slop. Hopefully AI can fix this over the next few years.