Hacker News new | ask | show | jobs
by fainpul 109 days ago
> Six months later, an architectural change required modifying those features. No one on the team could explain why certain components existed or how they interacted.

I thought when you vibe it, you're supposed to keep doing that forever.

If you need an explanation, ask the clanker.

1 comments

And when the clanker can't understand its own code?

This all sounds like the classic path I've seen low quality coders take, coding themselves into a corner until changes effectively become impossible.

For real people, that's when the coder finds a new job, often a promotion off the back of their dreadful architectural decisions, or if it's an agency, abandons the client.

I wonder if it will follow the same failure states, has anyone caught it making multiple versions of the same function yet? With slightly different bugs in them?