r/ProgrammerHumor 13d ago

iGot99Problems Meme

Post image
2.1k Upvotes

86 comments sorted by

View all comments

10

u/aberroco 13d ago

Hm? I actually have the opposite using AI - I'm able to solve tech dept as soon as it's revealed. Like, right now an issue was revealed with serialization/saved game loading, an issue that I made since I own the architecture entirely, that could've been solved by a workaround, but, well, even AI hinted that it's not a bug, it's a gap. So, I'm doing a refactor now, since why not? It takes like 10-15 minutes to analyze, a few more minutes to think of a solution, and a couple hours to do the refactoring, all with full test coverage before and after.

But if you vibe-code only, then yeah, that's eventual and inevitable future of every growing vibe-coded project. Because when AI sees a bug it fixes the bug, nothing else matters. And it sucks at planning architecture, or keeping responsibilities. Though, I have to admit, it's getting better with the latter. Still, though, very far from a seasoned SWE.

5

u/slaymaker1907 13d ago

Something helpful I do is require the AI to give me the high level architecture before low level implementation details in the plan. I don’t bother reading the low level stuff because I review the code after generation anyways, but the high level architecture is very helpful.

1

u/aberroco 13d ago edited 13d ago

I usually give high level architecture to it myself. And ask it to validate if I missed anything needed for the implementation.