Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

An AI Vibe Coding Horror Story

tobru.ch

Post reply on HN
Print view View original

181–190 of 224 posts

Re: An AI Vibe Coding Horror Story

#181

Post by consumer451 »

BitsAndObjects wrote: post #175
consumer451 wrote: post #116

Earlier quoted context omitted.

There are all kinds of memory hacks, tools that index your code, etc. The thing I have found that makes things work much better is, wait for it... Jira. Everyone loves to hate on Jira, but it is a mature platform for managing large projects. First, I use the Jira Rovo MCP (or cli, I don't wanna argue about that) to have Claude Code plan and document my architecture, features, etc. I then manually review and edit all…

Doesn't require Jira but yes, specification-first is the way to get better (albeit still not reliably good) results out of AI tools. Some people may call this "design-first" or "architecture-first". The point is really to think through what is being built before asking AI to write the implementation (i.e. code), and to review the code to make sure it matches the intended design. Most people run into problems (with or…

I used to manually curate a whole set of .md files for specs, implementation logs, docs, etc. I operated like this for a year. In the end, I realized that I was rolling my own crappy version of Jira.

One of the key improvements for me when using Jira was that it has well defined patterns for all of these things, and Claude knows all about the various types of Jira tickets, and the patterns to use them.

Also, the spec driven approach is not enough in itself. The specs need sub-items, linked bug reports and fixes. I need comments on all of these tickets as we go with implementation decisions, commit SHAs, etc.

When I come back to some particular feature later, giving Claude the appropriate context in a way it knows how to use is super easy, and is a huge leap ahead in consistency.

I know I sound like some caveman talking about Jira here, but having Claude write and read from it really helped me out a lot.

It turns out that dumb ole Jira is an excellent "project memory" storage system for agentic coding tools.

Re: An AI Vibe Coding Horror Story

#182

Post by BrissyCoder »

kuboble wrote: post #170
BrissyCoder wrote: post #152

Earlier quoted context omitted.

Yeah sure, as a matter of rule, every time I visit any health provider I am always discussing with the medical receptionist: the software they use, the challenges the business as a whole faces, the tensions between insurers and third parties. Things that absolutely 100% happen everytime I - a tech guy - experiences when I go to the doctor/phyiso-therapist etc... etc... These are discussions that are happening.

Ok. So can I conclude that your point boils down to: "Your claimed experience is different than my experience so you are lying"?

No I'm just straight up saying this post is fake.

Don't try to bring social justice warrior talk onto a tech forum please.

Re: An AI Vibe Coding Horror Story

#183

Post by fatata123 »

consumer451 wrote: post #116
freakynit wrote: post #57

I think vibe-coding is cool, but it runs into limits pretty fast (at least right now). It kinda falls apart once you get past a few thousand lines of code... and real systems aren't just big, they're actually messy...shit loads of components, services, edge cases, things breaking in weird ways. Getting all of that to work together reliably is a different game altogether. And you still need solid software engineering…

There are all kinds of memory hacks, tools that index your code, etc. The thing I have found that makes things work much better is, wait for it... Jira. Everyone loves to hate on Jira, but it is a mature platform for managing large projects. First, I use the Jira Rovo MCP (or cli, I don't wanna argue about that) to have Claude Code plan and document my architecture, features, etc. I then manually review and edit all…

[dead]

Re: An AI Vibe Coding Horror Story

#184

Post by orwin »

consumer451 wrote: post #116
freakynit wrote: post #57

I think vibe-coding is cool, but it runs into limits pretty fast (at least right now). It kinda falls apart once you get past a few thousand lines of code... and real systems aren't just big, they're actually messy...shit loads of components, services, edge cases, things breaking in weird ways. Getting all of that to work together reliably is a different game altogether. And you still need solid software engineering…

There are all kinds of memory hacks, tools that index your code, etc. The thing I have found that makes things work much better is, wait for it... Jira. Everyone loves to hate on Jira, but it is a mature platform for managing large projects. First, I use the Jira Rovo MCP (or cli, I don't wanna argue about that) to have Claude Code plan and document my architecture, features, etc. I then manually review and edit all…

But even spec-first, using opus4.6 with plan, the output is merely good, and not great. It isn't bad though, and the fixes are often minors, but you _have_ to read the output to keep the quality decent. Notably, I found that LLM dislike removing code that doesn't serve active purpose. Completely dead code, that they remove, but if the dead code have tests that still call it, it stays.

And small quality stuff. Just yesterday it used a static method where a class method was optimal. A lot of very small stuff I used to call my juniors on during reviews.

On another hand, it used an elegant trick to make the code more readable, but failed to use the same trick elsewhere for no reason. I'm not saying it's bad: I probably wouldn't have thought about it by myself, and kept the worse solution. But even when Claude is smarter than I am, I still have to overview it.

(All the discourse around AI did wonder for my imposter syndrome though)

Re: An AI Vibe Coding Horror Story

#185

Post by chrisjj »

chrisjj wrote: post #37
ginko wrote: post #16

Earlier quoted context omitted.

There's lack of security theater and there's: > All "access control" logic lived in the JavaScript on the client side, meaning the data was literally one curl command away from anyone who looked. They are not the same thing.

You've got to wonder from where did the "AI" parroted that.

A Stackoverflow wrong answer?

Re: An AI Vibe Coding Horror Story

#186

Post by thisisit »

spaniard89277 wrote: post #7

I did something similar to a local company here in Spain. Not medical, but a small insurance company. Believe it or not, yes, they vibecoded their CRM. I sent them an email and they threatened to sue me. I was a bit in shock from such dumb response, but I guess some people only learn the hard way, so I filed a report to the AEPD (Data protection agency in Spain) for starters, known to be brutal. I've also sent them a…

People building these apps often have no idea about various data privacy rules.

I am part of a forum with many small business owners. One particular owner has been gung-ho about how he built his entire business app using vibe coding. And my first reaction was - All the power to him. It’s his business and he is free to do so.

But then came the question of data privacy rules and he had no clue. This was concerning because the impact went beyond his business. His response when the oversight was pointed out to him was that being ignorant of the law was enough to save him. Still he went to one of the vibe coding Reddit subs to get help. Then came back fuming because devs on Reddit asked him to hire real developers. He believes that these developers are delusional and a dying breed and AI is so ahead that developers are going to be dead in a years time.

Re: An AI Vibe Coding Horror Story

#188

Post by kuboble »

BrissyCoder wrote: post #182
kuboble wrote: post #170

Earlier quoted context omitted.

Ok. So can I conclude that your point boils down to: "Your claimed experience is different than my experience so you are lying"?

No I'm just straight up saying this post is fake. Don't try to bring social justice warrior talk onto a tech forum please.

What kind of nonsense are you talking about? What social justice? What kind of argument is that?

you also claim that I am lying.

Are you willing to put money to be proven wrong? that it's normal to have a tech discussion with your doctor in Switzerland?

Re: An AI Vibe Coding Horror Story

#189

Post by BrissyCoder »

kuboble wrote: post #188
BrissyCoder wrote: post #182

Earlier quoted context omitted.

No I'm just straight up saying this post is fake. Don't try to bring social justice warrior talk onto a tech forum please.

What kind of nonsense are you talking about? What social justice? What kind of argument is that? you also claim that I am lying. Are you willing to put money to be proven wrong? that it's normal to have a tech discussion with your doctor in Switzerland?

Yes in good faith I will one hundred percent no-lie wire you 100AUD if you can prove beyond doubt that you had a discussion like that with a Swiss health provider. Not one that you contrive now after the fact - one that happened before this wager.

Spoiler: you didn't mate and you are full of shit.

Re: An AI Vibe Coding Horror Story

#190

Post by j_w »

BitsAndObjects wrote: post #173
kjksf wrote: post #166

Earlier quoted context omitted.

Nothing would be more effective at killing open source and commercial software business that requiring everyone that writes and ships software to users, directly or indirectly (e.g. an open-source library) to have License To Program from Software Licensing Organization. > aware of existing and new laws, standards and codes of practice Yeah, because software business is not at all ruled by fads. 1997: you have to foll…

What complete nonsense. Professional bodies don't mandate fads. Get a grip.

A software engineering licensing body would require licensed individuals to understand things about security and accessibility, which would be a huge improvement. If you are responsible for a trivial security vulnerability you and the company should actually be liable for it.

Sysadmins/other adjacent roles should likely have the same requirements. An unmaintained/unsecured server can create a huge liability.

Post reply on HN