Hacker News Reader

Parent Full thread

noisy_boy

1. Implement feature and write tests for the code

2. Make sure tests pass

3. <Every now and then> Review code for quality and fix - make sure tests pass.

4. Go to #1

Overly simplistic? Yes. But I would wager that this can go a long way, even for vibe coders.

View on HN

I keep seeing this but I'm not sure it is effective in the long run *if unsupervised*.

"Review quality and fix" doesn't mean a lot without context.

Does it mean to remove unused features and simplify the underlaying code? Does it mean changing the data structures to better support future development? Does it mean improving performance because of bottlenecks?

You are supposed to tell an LLM what your codebase needs, but if you just vibe code without knowing the code, "review quality and fix" will have unexpected results

It's glaring to see who's still buying the positivists AI hype and who's done actual work with it.

AI is amazing, but people need to realise meaning and intention can't exist in a vacuum.

Reply on news.ycombinator.com