Then half of your job is dealing with a shitty company and not being a developer. Half of your job is being wasted on overhead you can’t manage. That is half of your capability wasted on a lack of collaboration. How else to describe it than you are half the dev you could be while you blame everyone else. Shit as a director I’m not mixing words.
What you’re tracing the edges of is not being able manage complexity in a collaborative environment. If you can’t break the problem down part of is on the team but a lot of it is on you. If you want to architect a solution you have to be able to explain it.
That’s antithetical to you keeping on about how shitty (everyone else is) aka the other half of the world.
It’s pretty bad having to explain this to coddled engineers learning how the other half of the company works. Talking as if everyone else doesn’t get it while they can’t even perceive their own bubble. It’s not magic. It’s code. It’s nothing crazy so why be an asshole about it? Why do I get more bs from coders than I do contractors working on my roof? And don’t get me wrong the roofers piss in a shingles box and leave it for me to dispose… My grandfather worked on the Apollo missions so why is C# black fucking magic and suddenly you’re Gandalf? To YOU it’s magic. To the rest of us it’s a fucking job and you talk too much.
Yea the delta is important. And the mythical man month also counts ramp up time and not people just being generally incompetent.
Been through lots of engineers that can’t make it past ramp up, where everything is unpossible. Had many pms that couldn’t speak past the problem to save their lives so I feel that. But let’s be clear if there is a way forward don’t obscure the value. Don’t talk down. I work with post docs, principal engineers etc and they seem to be able to break down the problem, meanwhile lower level techs keep up with this shit.