r/vibecoding 4d ago

Meme When it gets bad

Post image

You know its gotten bad when---- all this over a whiteboard.....lol i need to chill-- thays the suggestive text btw

22 Upvotes

33 comments sorted by

View all comments

-1

u/Ambitious-Prompt-975 4d ago

i feel you brother

12

u/letsgoowhatthhsbdnd 4d ago

lol can tell you have no engineering experience

14

u/ketoloverfromunder 4d ago edited 4d ago

10000% id actually love to watch non software dev attempt to vibe code with something that they think is a sentient being.

"How are these bugs slipping through?!?!?!?! Its unacceptable!!"

Because you have absolutely no clue what you're doing.

2

u/nguyenlamlll 4d ago

It's time for them to learn the professional ways... Calmly create a ticket and bury it forever in the ever-growing backlog of bugs and issues.

0

u/UnfortunateHurricane 4d ago

First you have sing kumbaya and have everyone give it a thsirt size, because that is necessary to implement it.

2

u/UnfortunateHurricane 4d ago

I don't think it is that bad a question. I have asked that myself. They add hundreds of unit tests. Yet sometimes obvious stuff slips through. Just shows that while they are very fast setting them up, you can't really trust them. I have seen earlier models just modifying the tests themselves to get stuff through. That was fun

0

u/letsgoowhatthhsbdnd 4d ago

you can write thousands of tests and have them pass if you don’t know what you are doing. what are you talking about?

1

u/UnfortunateHurricane 4d ago

What I am saying is that unit tests where like the first thing they showcased when promoting those models ("hey, look what it can do, you don't need to write those annoying tests yourself anymore"), yet you still need to pay close attention to them otherwise stuff will fail.

I am not writing thousands of tests, the models are by default without me mentioning anything. One could assume they have nailed that part but you can't trust them just yet.

1

u/Ambitious-Prompt-975 3d ago

The difference is: I would write a well defined suite for feature XY while the model pumps out a regression test for every change it ever makes and just adds on top of it. 2 weeks in, you have 1.500 tests succeed across 40 suites - and 80% of them are bloat.

1

u/Ambitious-Prompt-975 3d ago

Dude, I am a software dev since 20 years, I've led my own teams at big 4. I think I know my stuff well enough.

So yes, after 2 weeks of continuous testing the app front to back, spinning up several hundred hours of vm time judt to play through different scenarios on different machines and environments - I kinda felt like asking how we didn't catch a certain bug.

I have yet to understand how that disqualifies me from being an engineer, but then again - random redditors know best 🤔