Comment

Comment by cmrdporcupine

You're not setting good enough boundaries or reviewing what it's doing closely enough.

Police it, and give it explicit instructions.

Then after it's done its work prompt it with something like "You're the staff engineer or team lead on this project, and I want you to go over your own git diff like it's a contribution from a junior team member. Think critically and apply judgement based on the architecture of the project describes @HERE.md and @THERE.md."

Discussion

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton