| ▲ | PaulHoule 20 hours ago | |
Treat it as a pair programmer. Ask it questions like "How do I?", "When I do X, Y happens, why is that?", "I think Z, prove me wrong" or "I want to do P, how do you think we should do it?" Feed it little tasks (30 s-5 min) and if you don't like this or that about the code it gives you either tell it something like
or edit something yourself and say
If you want to use it as a junior dev who gets sent off to do tickets and comes back with a patch three days later that will fail code review be my guest, but I greatly enjoy working with a tight feedback loop. | ||