|
|
|
|
|
by ookblah
371 days ago
|
|
do you let it generate lots of code before review? i find this feeling you describe if i let it run wild and then have to sit there and figure out what it did and slog through every line. the happy medium for me is either giving it very defined small tasks that i can review (think small edits or refactors over a few files). or i baby sit it and review every change its about to make. doesn't always pan out but it's basically a super powered auto-complete and i can "steer" it the direction i want. i can validate chunks much faster and it's typically of good quality. that or i make mental notes of what i want it to fix after the first pass and run it thru again with the edits. in that way it does feel more collaborative and less like reviewing some unknown piece of code from someone else. |
|