I agree somewhat with the "developer's journey" diagram, but I noticed the reason given for the "frustration" step is that senior devs get roped into fixing oth

I agree somewhat with the "developer's journey" diagram, but I noticed the reason given for the "frustration" step is that senior devs get roped into fixing others bad code. This hasn't been my experience. The frustration typically comes from a lack of autonomy. I think scrum is great for guiding junior devs, but as you become more senior, it seems to ensure the company only makes use of your "junior dev" qualities. I don't know why so many companies seem so terrified of letting go of the reins on their senior devs for a few weeks at a time and see what they come up with on their own. I mean, that's where gmail came from...