This hits home quite hard. I get depressed sometimes working on teams where I'm the most technically proficient on the team and I want to solve a problem in a

This hits home quite hard. I get depressed sometimes working on teams where I'm the most technically proficient on the team and I want to solve a problem in a way which will save everybody not just a little time, but probably save us enough time that we could remove one or two staff. But then I remember how I got the skills to do such things. Hours of work a day for years at work. Hours of interest a way in my personal life. I did that for decades and I had a natural knack for such things. So it turns out the solutions I build would fall apart without me holding them together. As soon as I leave whatever I make will be thrown out. I'm not good enough to unilaterally make so tools that they are easily maintainable, debuggable, extendable, and so on by just anybody you hire off the street. The more I understand how to reconcile these problems, the more I understand managers and architects.