Comment by nobodyandproud

I found it’s great for: 1. Exploring new code bases or understanding PRs. 2. Prototyping new ideas. 3. Second opinion on problems and troubleshooting. 4. Rubber ducking. 5. Parallelize rote/boiler plate, while my deep focus is elsewhere. 6. First draft of documentation and reviews.

What I don’t understand is how some people can parallelize 5-10 engineering changes at once, and expect to support and maintain that code in the future.

The difficulty has always been in support and maintenance, not building something new, and that requires a deeper understanding.