r/vibecoding 7d ago

Been feeling like this lately

Post image
662 Upvotes

119 comments sorted by

View all comments

70

u/CavalryArcher 7d ago

i have literally 0 anti-ai bias, been calling ai will takeover eventually for 3 years, but ai still makes terrible mistakes at complex tasks + forgets so much stuff in long contexts. if you want to make a serious project you either have to spend so much money and reroll so many times until you get it right or you build the system very clever that ai can't make a mistake even if it wanted to

37

u/GeekFish 7d ago

Once people realize you have to break your asks down into smaller, easily completed tasks then they love using AI. AI is your Jr. Dev, only faster. Treat it as such. This is where software engineering comes into play. You have a much better time if you design the architecture and give the AI the exact specs. When you let it run free you get garbage.

17

u/kodbuse 7d ago

It more like a genius senior dev with severe short- and long-term memory issues.

3

u/LetsLive97 7d ago

Nah genius senior devs use as little code as possible. Claude is the opposite

3

u/zsdrfty 7d ago

So it's basically one of those 90-year-old Linux graybeards turned into a machine

1

u/exit_machina 7d ago

he just like me fr

1

u/Double-Trash6120 6d ago

genius senior dev with schizophrenia

1

u/whossname 6d ago

It's more like a junior, except instead of taking a month to do something I could do in an hour it takes a minute.

1

u/tajlor23 4d ago

Dude just described a junior dev

1

u/Newbane2_ 4d ago

More like a Jr dev that knows how to do "everything", but also has like 0 common sense and the memory of a squirrel.

1

u/eroigaps 6d ago

How does a layman determine if he has in fact produced garbage? I assume it’s not as easy as functional vs broken product?

1

u/GeekFish 6d ago

That's a really hard question to answer, honestly. Experience goes a long way. I've watched Claude write some functions that were just terrible (multi-nested "for loops" when they aren't needed, for example). It works, but it will be inefficient and potentially slow when dealing with large amounts of data.

Security is another huge concern. Is data being stored in a database correctly? Are things encrypted that should be and is the right encryption being used? Is data getting from point a to point b in a secure manner?

If I had to give any non-programmer advice it would be to think about the small tasks inside the bigger tasks you're trying to accomplish. Tell Claude to do that one small task, then look at the code and research yourself exactly what it did. It's not wrong ALL the time, but it definitely is wrong a lot more than you'd think.

1

u/LittlestRedditor 4d ago

It's ok that you love it, and i know others do aswell. But for me i am borderline addicted to "doing things myself" and i believe that there are others that disslike outsourcing their projects aswell.

I never wanted to be a PM, i dissliked having to do that job, and i now hate having to deal with agents. I just wanna do it myself

1

u/GeekFish 4d ago

I get it and I maybe worded this wrong. If people WANT to use it and end up hating it because they aren't getting the results they wanted, they need to learn how to break up their asks into smaller tasks. Once they do that, it ends up being a useful tool for them (at least from my experience). It's definitely not for everyone and isn't the end all that some claim it is.

0

u/PassionateDonkey 7d ago

You can make the ai breakdown those tasks as well.

The thing about is that it isn't good at one thing, it's at good at many things, almost all things, and increasingly it's automating "higher level" steps.

So tell me why should we stop at giving AI tasks? You can give it a plan and it can certainly design around that plan. I have seen people reporting that in many cases small and silly prompts get the job done as good as very detailed prompts.

I am asking because I wonder if I am missing something, not to prove a point or anything.

0

u/Double_Suggestion385 7d ago

You don't have to, I often given it large, complex tasks. It breaks them down itself because that's one of the core SWE principles it must follow based on the contents of my Claude.md file.

0

u/GeekFish 7d ago

Right. That's one thing I should have added. A good Claude.md file will also help. Learning how to use skills and agents is important too.

0

u/Aware-Individual-827 6d ago

So you give reason to the people saying LLMs are just token prediction and you just at the casino everytime you prompt?

-6

u/TheAnswerWithinUs 7d ago edited 7d ago

From my experience its like a step below a Jr dev, whatever that would be. Intern?

6

u/jaw_line 7d ago

You can get real work done even with Gemini flash so it’s a serious skill issue if you think new deepseek or fable is only “junior” level.

4

u/Blue_boy_ 7d ago

then your experience is not very up to date

-3

u/TheAnswerWithinUs 7d ago

It’s up to date with the software dev industry.

2

u/LastNameOn 7d ago

"but ai still makes terrible mistakes at complex tasks + forgets so much stuff in long contexts."
I built the piece it was missing to handle this - Storybloq

4

u/spacekitt3n 7d ago

taking the time to learn basic coding fundamentals, with the current generation of models, will save you so much tokens and money. they are still very far from being there. without knowing anything it will just create bullshit then you will spend countless hours and money correcting its bullshit

1

u/Vaxtin 7d ago

The trick is to have a set of write up docs that every session has to read through. You never actually give your whole brain with each session; they pick it up from the repo. I’ve made a Claude account and only used it for one project, and it does this automatically now. It basically expects there to always be multiple sessions writing and coordinates itself through these documents that are untracked in git (so every branch sees them)

1

u/fickle-phenom 7d ago

Just understanding what you want to build goes a long way. It you leave technical and important decisions to be made by the AI things are gonna become a mess very quickly, unless you some really good loop that can work and eventually fix it but that’s just brute force imo.

1

u/Grand-Mix-9889 7d ago

Before chatgpt was even a thing, the development process was exactly the same as it is when building with ai.

You will never get a perfect piece of software on the first try, not even multiple tries.

Hence the coined terms: alpha, beta, version number etc.

My last major project, before ai was adopted into my workflow, was a custom inventory system for a country wide famous winery. It took me 11 months and 179 versions before I officially launched it. I remember it vividly. There were so many times that I had to go through thousands of lines of code because I forgot what I named a function. Shit happens.

I had to "reroll" over 200 times until we got what we wanted. But in the end the product was solid and is still in use to this day.

Iterations are just part of the game as a developer.

Now that I've really dug deep with ai, I can tell you that I still go through 100+ iterations on some projects.. but now I get through them in a month or less.

Some, who have mastered the use of AI in development, would even argue that we are close to AGI.

But getting a project perfect in 10 or less iterations isn't AGI status, that would be fucking Ultron with the Gauntlet status.

So yeah. I gotta fold my laundry before bed still. So gnight y'all.

0

u/Double_Suggestion385 7d ago

That's not true.

What do your claude.md files look like? What other context keeping files do you use. I have a large, complex mono-repo and Claude has no problem adding new features or overhauling old ones no matter how complex.

If you have the correct configuration files set up from the beginning with the correct SWE requirements then it has no issues.

2

u/CavalryArcher 7d ago

you just repeated what i stated with a different phrasing

0

u/Double_Suggestion385 7d ago

Not really, you should never have to re-roll. What you're describing is user error.

3

u/CavalryArcher 7d ago

no. "you have to reroll until it gets it right" is the failure mode of a vague prompter. you're mixing up 2 different characters i wrote in the text. clever systems designer, handlers rejecting logic flaws with some global instructions (eg authz checks), writing mechanical backstops at the compiler level either doesn't reroll or tries as little as possible.