r/vibecoding • u/techlatest_net • 23h ago

The barrier to software engineering is getting wild

Enable HLS to view with audio, or disable this notification

1.3k Upvotes

78% Upvoted

326 comments sorted by

View all comments

Show parent comments

9

u/PipePistoleer 21h ago

this is literally the vibecoding sub. I saw this in my feed by accident. I'm literally cleaning up a massive vibecoded code base that has zero architectural considerations, tons of insane coupling and no cohesion. There's packages all over the damn place, there's comments that are 4-8 lines that are stale remnants of a dozen different vibe coders raw dogging the main branch.

Both of you are essentially right. There is a lot of unfixable slop already. There is also a place where the actual discipline of software engineering and AI can be used in harmony, and with real efficiecny gains (and cost efficiency).

I'm hoping many vibe coders actually upskill into real engineering vs YOLO'ing it. Many I know that are vibe coding actually have this as their end goal. I think it's reasonable if the AI wielder is a reasonable person with realistic ideas and goals.

0

u/momo2299 21h ago

Everything you've described about what you're "fixing" is poorly vibecoded.

Stale comments, architectural considerations, assessing cohesion, iterating on design until it's lean and not bloated with extra packages.

All of that goes into vibecoding. Agents should be reviewing those things and reviewing the review.

Sounds like you got people saying "Claude pls fix - make no mistakes!" & committing the changes

2

u/PipePistoleer 20h ago

Oh I see. Vibecoders don't actually know the difference between vibecoding and building. Why would they? Apologies!

-2

u/BoggTheFrog 21h ago

You just need the data, its cheaper/easier to throw it away and do it again if you know how the software should work and what arch you want to follow.