r/vibecoding • • Jun 21 '26

For what

Post image
122 Upvotes

124 comments sorted by

320

u/your_best_1 Jun 21 '26

Perfect example of how this meme is always authored by the left guy.

61

u/Capable-Ad-2065 Jun 21 '26

You don't know what you don't know.

1

u/SenatorCrabHat Jun 25 '26

biggest problem with folks wanting to use AI as tutors etc. too. You wont know the right questions to ask.

16

u/Async-async Jun 21 '26

Perfect example of the comment of the guy in the middle (I am guru on the right, trust me)

10

u/Illustrious-Trick525 Jun 21 '26

So you are implementing things you don’t understand and call yourself guru?

-4

u/Async-async Jun 21 '26

Yes, but only for my personal projects. Work is different, and my personal projects allow me to glance in the way this is going to be in the future. It’s not that you don’t understand how it works. It’s you operating at the level of meeting requirements rather than micro managing your llm which requires you to understand how project works in every detail.

14

u/Illustrious-Trick525 Jun 21 '26

So you contradict yourself because it was said it is good for everything

-2

u/Async-async Jun 21 '26

Not per se. Company requires safety guards, because there is no trust. But I am seeing how it goes and I have trust all the way. Yes you need to know what you’re doing which begs the question what is vibe coding, but I personally don’t write code anymore. I write specifications for llm to write code and validation tests.

2

u/kueso Jun 24 '26

There’s all sorts of problems with specs. People are ignoring the reality that most tickets change as you implement them and you can’t trust a non-deterministic algorithm to make a decision for your domain and system. That’s why most advocate for several philosophies including spec, human in the loop, governance, and multi-agent evaluation. Creating systems fully with AI is just a complex as coding. Just a different level of abstraction.

0

u/[deleted] Jun 21 '26

[deleted]

1

u/Async-async Jun 21 '26

Exactly. But for some reason when these conversations start people assume the starting point is not having foundation. And that is very different in every company.

6

u/your_best_1 Jun 21 '26

Because that is how the term was coined. If you review and understand the code, you are not vibe coding. If vibe coding is just ai assist while you do all the cognitive work, then we don’t need a new term for that.

1

u/oblong_pickle Jun 21 '26

Is there though if you vibe code?

1

u/DowntownLizard Jun 22 '26

I would say it depends on your definition of vibe coding. I would say the LLM can nearly always write all of the code and you don't have to understand all of it. Part of being an engineer is knowing what parts you do need to understand and what is worth your time to review.

I could write it myself but I'm just not going to do it as fast or maybe even as well as an LLM and I felt like I was a very good coder. Vibe coding to me is that you wouldnt have been able to build it yourself or are lacking all the knowledge you should have outside of writing code. Feels like the left side is vibe coding and right side is being a very good engineer leveraging a tool that augments your ability to solve problems and in doing so you barely need to write any code yourself.

1

u/Remake911 Jun 21 '26

Perfect example of the comment from the middle guy 😮‍💨

1

u/Ok_Bug1610 Jun 22 '26

I know it got some hate, but that is the funniest comment... because it's true.

1

u/Remake911 Jun 22 '26

Who is the guy I. The right then?

1

u/No-Addendum-787 Jun 23 '26

Altman and Amodei selling you their newest models

130

u/Particular-Award118 Jun 21 '26

Putting your opinion on the smart guy in a meme doesn't make you smart

-35

u/Icy_Distribution_361 Jun 21 '26

It doesn’t, but it also doesn’t mean it’s not true.

18

u/bigrealaccount Jun 21 '26

vibe coders vs the reality that literally every vibe coded app fails in 50 different ways once you try to deploy it to more than 5 users.

1

u/deruben Jun 22 '26

well thats probably every app ever since the dawn of computers

-3

u/That-Cry3210 Jun 21 '26

False as fuck. Plenty of people making money

13

u/bigrealaccount Jun 21 '26

My bad, 99.9% of vibe coded apps fail, and the remaining 0.1% require help from an actual engineer at some point

2

u/DisasterNarrow4949 Jun 21 '26

I mean "99.9%" of the non vibed apps also fail.

0

u/bigrealaccount Jun 21 '26

Nope

And if they do fail, at least you learned something and carry the engineering skills to the next project.

0

u/[deleted] Jun 21 '26

[deleted]

0

u/bigrealaccount Jun 21 '26

Claude is more competent than founders with no technical skills and can prototype for you, but it's nowhere near the engineering skill of an actual SWE.

1

u/[deleted] Jun 21 '26

[removed] — view removed comment

5

u/bigrealaccount Jun 21 '26

It gets constantly recommend to me sadly

2

u/perfectVoidler Jun 22 '26

reddit decided that I am into shitshows. So this sub was recommanded.

3

u/Appropriate-Draft-91 Jun 21 '26

Correct observation, wrong conclusion. You won't find a senior dev that claims software that falls apart 50 different ways cannot make money.

1

u/Long-Sundae149 Jun 21 '26

Sure, but is anyone making a profit?

-2

u/Icy_Distribution_361 Jun 21 '26

I don’t think that’s true at all. Well at least not literally every one.

40

u/speakerjohnash Jun 21 '26

oh my sweet summer children

37

u/willbdb425 Jun 21 '26

Let me know if you ever write software for something like airplanes or a medical device so that I know not to use it, thanks 👍

10

u/hurricane_news Jun 21 '26

People like that don't graduate beyond building the typical mern crud slop

3

u/havnar- Jun 21 '26

“I just build this great SAAS”

8

u/t3kner Jun 21 '26

SWE is dead, we vibe code all our pacemaker software so now you're dead as well

17

u/Western_Diver_773 Jun 21 '26

I think it really depends on what you are doing.

8

u/TheAnswerWithinUs Jun 21 '26

Holy Dunning-Kruger

2

u/AffectionateBowl1633 Jun 21 '26

AI is machine used by a mediocre to revenge for an actual talented people

2

u/SuperSlowSubie Jun 22 '26

You know I've never thought of it that way, and I definitely agree.

5

u/Weird-Mistake-4968 Jun 21 '26

It’s like the guys how review the assembly code of their built binary with Ghidra to make sure the compiler did the right thing.

3

u/Ameren Jun 21 '26

The difference, of course, is that the compiler is supposed to be deterministic and precisely follow the standards of the language. Even then, in critical embedded applications you have people going through the assembly code with tools like Ghidra. Meanwhile, LLMs are stochastic, so you really do have to check the outputs (if the software is important, that is).

The other thing is that if you give an LLM a spec to implement, you don't want to write something so comprehensive that it's equivalent to writing the code, so you're delegating a lot of choices to the LLM. You're still responsible for the end result though.

2

u/Weird-Mistake-4968 Jun 21 '26

That’s true. On specific systems it makes sense to look at certain time critical functions and check if the compiler used special more performant instructions.

On the other hand you can do it in two steps. Use AI to write a very detailed implementation plan review this plan. Then you create very good unit tests and test die generated implementation. For non critical stuff and small development tools and proof of concepts this is my way to go.

11

u/chipper33 Jun 21 '26

Software isn’t hard to make. Software at scale is.

LLM is just another abstraction. IMO you don’t need to look at the code itself, but you do need to go into great detail about each part of the design of your system.

Practice planning more than vibing. It cost a lot for LLMs to write code, but far less to plan with it.

If you let the LLM make engineering decisions, that’s bad. it has no real concept of the human problem you’re solving. On the other hand, letting it write out the code after you planned out every aspect of what it’s supposed to do and how it will work, is just straight up engineering.

Learn design patterns. Learn Fundamental data structures. Algorithms are good to know as well, but less important than understanding the other two. Algorithms teach you how to use data structures. Design patterns teach you how to build working software systems with data structures.

11

u/hulkklogan Jun 21 '26

IMO you don’t need to look at the code itself

Maybe not for smaller projects but my man, even with the most simple tasks LLMs fuck up in a big codebase. At work, just this week, I was converting sync python functions to async and I had Claude scaffold up async functions and unit tests; something it's usually good at. It did the copy/paste and db access updates correctly, but in the unit tests it used an antipattern in our testing framework that's explicitly called out in CLAUDE.md to not use and causes flaky tests if used. You have to review the code that's produced in an enterprise codebase.

4

u/xCaedusx Jun 21 '26

I've been having the same kind of issues with tests lately. I feel like Claude is getting dumber. For a while it did great writing tests patterned after what I gave it l, but now it seems to completely ignore my MD file. It really does do some helpful things, but man if I didn't read what it tries to do sometimes, I'd be out of a job

1

u/itsamberleafable Jun 22 '26

it used an antipattern in our testing framework that's explicitly called out in CLAUDE.md to not use and causes flaky tests if used

A tip I use for this is I have a skill that I call before I review the code. The skill gets Claude to spin up another agent and get it to review the diff against the CLAUDE.md file and any other relevant skills. The agent then spits out any issues and it has another go.

It doesn't catch everything but I've noticed it's a lot more accurate than hoping the agent your using doesn't break the rules of your MD file. You may already do this but just sharing in case it helps

4

u/Beneficial_Fix_6169 Jun 21 '26

Creating with ai is easy, but maintaining it, especially when you don't understand what the code does, is a lot harder.

7

u/automatedBlogger Jun 21 '26

Vibe coding is def not enough for anything that matters, I would almost invert this chart.

3

u/Substantial_Pin_50 Jun 21 '26

agent coding from experienced coder/developer is pretty cool, vibecoding without it it's definitely not a stable solution that's worth paying for.😉

3

u/Ok_Difficulty6626 Jun 21 '26

The worst thing about these memes isn't that some redditor thinks this way, it's that the upper management inside banks, tech companies and other institutions thinks this way so everything gets enshittified constantly.

3

u/evangelism2 Jun 21 '26

Absolutely nobody on the right side of that graph is saying that vibe coding is good enough for everything

3

u/Hot-Cattle8314 Jun 21 '26

Whoever made this meme has never actually worked as a developer

2

u/KSOYARO Jun 21 '26

I bet you will change your mind if you will be offered to use medical related vibecoded software with the same attitude

2

u/FLIBBIDYDIBBIDYDAWG Jun 21 '26

Trust me i tried vibe coding my current project at work and it cost me more time than rawdogging would have. Maybe if i had fable 5 it would have been better but

2

u/BirdlessFlight Jun 21 '26

Oh sweet summer child.

2

u/uduni Jun 21 '26

Theres always something more sophisticated to build…

2

u/Ozziness Jun 21 '26

I don't know about you, but I dont want my medical device software to be vibe coded

2

u/jack-of-some Jun 21 '26

Context matters

2

u/BillRuddickJrPhd Jun 21 '26

I would like to ask people in the middle a question:

When you add a 3rd party package as a dependency to your project and it does exactly what it's supposed to do, how much of its code do you actually inspect?

2

u/idakale Jun 21 '26

i see so maybe the answer for my emotional break is to lower my iq further it turned out (since I'm super laziest baka that iq increase would become too hard)

Thx OP you're a lifesaver /s (im only half joking really i had been so frustrated with this past two week)

0

u/BitOne2707 Jun 21 '26

I think I'm the one on the right but I'm afraid that I'm actually the one on the left.

-2

u/[deleted] Jun 21 '26

it will not change outside world and how it works only your internal world, so all good :)

1

u/M4NU3L2311 Jun 21 '26

The problem is that it often cheats just to have your expected result and and if you don’t understand what you are doing then you won’t ever realize it

1

u/Gangr3l Jun 21 '26

Yeah, I'm using local llm to help me with coding and this is one of those instances where this meme doesn't apply

1

u/trmnl_cmdr Jun 21 '26

All my code is in plain English now. I just keep the PRD updated and let the agent do the rest. As long as there isn’t a visual UI that’s difficult to write tests for, it gets it done. I’ve been coding since the 90s, it’s just not something we need to do by hand anymore

1

u/chloro9001 Jun 21 '26

Top models with well thought out prompts almost never make mistakes, especially in existing well thought out code bases

1

u/wickedosu Jun 21 '26

Web development is not everything

1

u/TrainingTheory552 Jun 21 '26

except this is not true

1

u/xkalibur3 Jun 21 '26

I'm proudly in the middle of the curve on this one hah.

1

u/smaTc Jun 21 '26

Absolutely do that! I am going to be very rich in the future when I take money for fixing and updating small shit in vibe coded apps.

1

u/madhewprague Jun 21 '26

Making an algoritm is harder than understanding algoritm, thats why great programmer with ai will be always much more productive than oldschool programmer.

1

u/BionikMlc Jun 22 '26

Vibe coding is like buying a car. You don't have to be a mechanic to drive it, but once it breaks down, your neighborhood mechanic becomes your best friend.

The problem with software projects is that they're constantly evolving and expanding, which means the chances of something breaking are much higher.

Relying entirely on vibe coding for your business is a bad idea. It can come back to bite you as the problems pile up like a rolling snowball.

1

u/tjax4376 Jun 22 '26

Personally, test driven development is the only method of reducing bugs, forcing a different instance or sub-agent to take steps back if tests fail more than 3 times is crucial to the outcome. Good harnesses do this for you, self-driven ones need a little help. I perform spec driven developments alongside vibe coding projects, searching for the best outcome. My evidence points to no clear winner. But vibing helps with flow, using /grill-me really helps pull the idea apart though.

1

u/Ok_Raisin_2395 Jun 22 '26

You can vibe code basic functions and, at this point, entire classes depending on their complexity with nearly 100% confidence. You can then use your own brain to put those basic pieces together and build just about anything, yes. 

What you can't do, and will likely never be able to do, is just let an AI loose and trust it'll do the job every time. 

1

u/Tricky-Frame6828 Jun 22 '26

you're probably feeling stuck right now, it's normal to plateau and feel like you're not making progress. I've been there too, and it's just a matter of taking a step back and re-evaluating your approach

1

u/lucid-quiet Jun 22 '26

The right side guy got a lobotomy? Like he's not pro+ai? This meme doesn't say what it thinks it says.

1

u/jerceratops Jun 23 '26

The “vibe coding” on the left and right are completely different things, but also this is spot on.

1

u/Etikoza Jun 24 '26

No this is wrong and dumb.

1

u/Royal_Owl2177 Jun 24 '26

I like the meme template but this is a bad usage.

1

u/ex_gatito Jun 25 '26

People like OP, are the ones who complain that they can’t find a CS job. I wander why…

1

u/ManufacturerNice870 Jun 21 '26

It’s enough for most coding tasks. Trying to use it for things like physics simulations is really hard to get it to work. It hallucinates/cheats unless you have each equation and step and at that point you might as well do it yourself

2

u/hornynnerdy69 Jun 21 '26

Shouldn’t you be asking it to write a program to do the physics simulation? Or are you saying even at writing that sort of program, it falls flat and messes up putting the equations into code

3

u/ManufacturerNice870 Jun 21 '26

Yeah messes up intermediate steps, they look right, but often they’re not

0

u/[deleted] Jun 21 '26

[deleted]

4

u/ManufacturerNice870 Jun 21 '26 edited Jun 21 '26

Oh yeah 100 percent. For neutral-atom physics research. It can get it 90-95 percent of the way but making tweaks or filling in the gaps with it gets you totally buried, only way I was able to start making progress was by totally deleting everything I clanked.

1

u/XlikeX666 Jun 21 '26

better in my opinion.

0

u/Vaxtin Jun 21 '26

Lot of old men yelling at clouds about to have their whole career uplifted when engineering is solved in 6 months and some 22 year old willing to embrace AI replaces him

-2

u/hardscripts Jun 21 '26

I have a CI/CD agent, when my other agents submit a PR, he gets to work. Over 1000 deployments on my current project and no issues so far.

57

u/[deleted] Jun 21 '26

[removed] — view removed comment

27

u/botle Jun 21 '26

Which means it's not enough for everything.

-1

u/Prettypeachrec Jun 21 '26

🤓☝🏼

-1

u/Icy_Distribution_361 Jun 21 '26

Depends what vibe coding definition you maintain, bro.

6

u/[deleted] Jun 21 '26

[removed] — view removed comment

1

u/Rafaell_Saraiva Jun 22 '26

How do you know?

1

u/Murky-Morning-6464 Jun 24 '26

How do you know?

1

u/[deleted] Jun 24 '26 edited Jun 24 '26

[removed] — view removed comment

1

u/Murky-Morning-6464 Jun 24 '26

That was a good read thank you.

0

u/IkuraNugget Jun 22 '26

I mean… unless your goal is to build prototypes all day and not earn a single dollar sure. The reality is if you want to ever make some money and sell a product you’d need to go beyond the prototype phase.

0

u/[deleted] Jun 21 '26

[removed] — view removed comment

0

u/hatekhyr Jun 21 '26

That's it. Solved. Thanks.

0

u/[deleted] Jun 21 '26

[deleted]

1

u/Jaeger_Meister_ Jun 22 '26

Do you all not have a review process? Sounds pretty toxic to blame it all on one guy when multiple people supposedly read and understood the code

2

u/fife_digga Jun 22 '26

Most companies do this - you need a single throat to choke if something breaks. That’s not going to be the code reviewers. If you write the code you should have designed, planned, and tested the PR. You are ultimately responsible. You have a better understanding of your code than the reviewers do, and code reviews don’t absolve you of any responsibility

1

u/Jaeger_Meister_ Jun 22 '26

I think you have a responsibility to adhere to the process and conventions, like testing and such. If you did and you still messed up, that's a team / systematic issue not a personal one IMO. In my company nothing important gets merged unless the code is fully understood by multiple people and mistakes don't get punished harshly, it's a healthier dynamic and lets people grow from their mistakes. It is also exposes faults in process, rather than obfuscating them by blaming a single individual

1

u/fife_digga Jun 22 '26

I mean, I totally agree that reviewers need to understand the code they’re approving. And at places I’ve worked, at least, to keep a blameless culture, where people don’t get into trouble for merging code with bugs (within a reason of course!). But on a personal level, the owner of the story owns what gets merged. So I think we mostly agree, and that culture I’m talking about isn’t as cut throat as it might have sounded.

10

u/[deleted] Jun 21 '26 edited Jun 21 '26

[removed] — view removed comment

1

u/althoradeem Jun 22 '26

yeah... in big enviroments pushing shit from ai live and going "but ai said it was fine" isnt going to save you 😃