Re:We promoted developers into architects without informing ...
by markus_zhang on Friday November 20, 2026 @10:52PM
(#50585749)
Some people are not interested in some roles. I feel so disgusted trying to get the exact requirements from a stakeholder that I really hate my job. I’d argue it’s also a very bad use of my ability. It’s a lot easier to train someone who vaguely knows what they want to clarify what they want, then someone who doesn’t know what others want to clarify what others want.
I don’t hate the PM role but some stakeholders are so…ah don’t want HR to find me here, right?
The more I play this game the more I want to squeeze into lower level programming careers where stakeholders are more technical.
More often than not, one person does the majority of this, and does their best to break up the responsibilities. A good CTO does that at the top, and it flows down through the ranks depending on how big the org is. Perhaps it's just a CTO and 5 engineers, perhaps it's a CTO with 5 divisions, each with 10 groups, with many teams.
Flatter structures of engaged members works best from what I've seen, but you need to have a critical mass of people not only willing to take initiative, but empowered by leadership.