4 ms·
I tend to agree that managers of engineers should have engineering experience. I think my reasons would differ from those of the author and many other engineers
by sidlls 9y ago
I tend to agree that managers of engineers should have engineering experience. I think my reasons would differ from those of the author and many other engineers: it's much less charitable toward engineers. One of the best reasons to select managers who have been engineers, in my opinion, is because they know how much bullshit engineers engage in with respect to fad chasing, bikeshedding and other negative practices. It's important to know what the work of an engineer really entails: that includes the aspects of it that negatively impact the business and how as much as it does the aspects that contribute value and how.
- atmartins 9y agoThis is a valid point. In my mind, ideally, at least one or two trusted members on the team can help with this since they're even closer to the actual engineering taking place. It's helpful for management to understand the tradeoffs that are discussed, so I agree that some experience is very helpful, but hopefully the team has a few mature members as well.
- jackhack 9y agoYes, 100% agree! I've seen such a thing, taken to an extreme where lazy, underskilled developers were running the show; overcomplicating, underdelivering, yet showered with praise -- and it's horrible to witness. A word of warning for anyone entering such a world: you will not change this environment and any attempts to do so will trigger an immune system response. The developers and clueless managers will circle the wagons in defense of the existing culture. Lesson learned: don't interfere with "resume-driven development" organizations. I suggest the following interview question: "Tell me about the technical capability of your management chain."
- dominotw 9y ago> I tend to agree that managers of engineers should have engineering experience. What about managers who have had experience like a decade ago and don't do much tech experience anymore. I am stuck in such management chain at work where some guy up top thinks he is technical enough to dictate solutions based on couple conference youtube videos that he watches. Half knowledge and false sense of technical prowess is more dangerous imo.
- euroclydon 9y agoA manager should not be dictating architecture unless it’s some really small operation, and even then, it’s dicey. Rather, anyone who is capable of writing up a white paper that describes the problem, solution and rational for the choices should be able to propose a solution, and then have a meeting to discuss and decide whether to move forward. A manager should have the big picture and communicate it to the team. Then you could avoid a team member wasting time on something that’s not in the greater objectives or roadmap.
- sidlls 9y agoMost of the technology in use today isn't that different from what it was 10 years ago. It's a bit faster and has slightly different packaging. Any manager who last did engineering as an individual contributor ten years ago should be perfectly fine engaging in a technical discussion today at the level a manager should be doing so.
- chrisan 9y ago> What about managers who have had experience like a decade ago and don't do much tech experience anymore. Do you think any of the "bullshit engineers engage in with respect to fad chasing, bikeshedding and other negative practices." will change in 20 years? Its been almost 20 years since first coined and we _still_ have bike shedding problems