I probably have been that guy. Especially when younger, and very 'in the weeds' of code. It was laced with my opinions about how to solve the problem. I thought

I probably have been that guy. Especially when younger, and very 'in the weeds' of code. It was laced with my opinions about how to solve the problem. I thought my main outcome was some "pure" sense of well implemented code that stood the test of time. I really prided myself on my craft. Who were these interlopers coming in to my perfect paradise and fouling the place up? Then I became more senior and realized: (a) it turns out not everyone thinks like me and what I think is 'pure' (surprise surprise!) (b) holding tightly to my attitude of good code, means I live by some attitude that only I can solve the problem. Which is a sure way to get overworked and burn out. (c) it's also cool + fulfilling to level other people up and grow them. And often they want to learn. Because then they bring their other fun + hard problems to you, and you also don't have to maintain the original stuff forever - see point (b) (d) I was embarrassingly wrong enough to need to learn some humility (e) Related to (d) I won't grow if I always think the same My guess is that in my case, I experienced some early narcissism - basically all teenagers and young adults - but grew out of it. Especially as I matured, had more leadership roles, and had kids Note though that even to this day, I get the "grumps" when I have to manage some sudden opinion not in line with mine. I eventually swallow my pride and it usually is an educational moment. I've learned I'd rather have a well loved piece of code held together with duct tape and bailing wire with the misery shared with the team, then my own perfect, isolated place where only I understand how things work.