I enjoyed those parts too, for multiple reasons. Typos often forced me to ask a colleague for a fresh pair of eyes (who'd almost always spot the problem immediately. Humbling, and great for team cohesion) manually running git bisect to isolate a problem helped me understand how different changesets interact, making me better at reviewing code. Debugging race conditions taught me resilience, and deepened my understanding of the code base, and the satisfaction from fixing a gnarly problem was fantastic. I also enjoyed gaining mastery and becoming the go-to person for a certain class of problem. These are all gone now, sacrificed on the altar of efficiency gains. Now it's "BTW, I noticed a subtle race condition while refactoring variable names, and fixed it. Review my 6,000 line diff now please."
The unexpected variety of activities gave texture to my working day, and was probably good for the brain. Does anyone actually achieve flow state while using agentic AI? I don't[1], and I hate it.
1. except occasionally during design, which isn't thr same. AI side quests inevitably overflow detailed mental models.