For me the key things are: (1) understanding from a project management perspective how to cut out little tasks and questions
PaulHoule on Hacker News
In the thread “Ask HN: How can I get better at using AI for programming?”, replying to this comment
Helped: Cutting tasks small, understanding code to verify, and recognizing context poisoning.
Got in the way: Context poisoning causing arguments, circles, or new bugs.
… It doesn't bother me so much that the tests are too tightly coupled because I can tell Junie to fix or replace the tests if I run into trouble. For me the key things are: (1) understanding from a project management perspective how to cut out little tasks and questions, (2) understanding enough coding to know if it is on the right track (my non-technical boss has tried vibe coding and gets nowhere), (3) accepting that it works sometimes and sometimes it doesn't, and (4) recognizing context poisoning -- sometimes you ask it to do something and it gets it 95% right and you can tell it to fix the last bit and it is golden, …