3 ms·
To be exact, the article said > coding, architecting, or doing technical work that requires engineering prowess. As a software engineer, I don't even spend 80
by Aperocky 6y ago
To be exact, the article said
> coding, architecting, or doing technical work that requires engineering prowess.
As a software engineer, I don't even spend 80% of the time working coding, in fact it's more like 30%. But I do spend almost 100% of the time doing the stated things above.
However, I do agree with you (mostly). My position is that having an understanding of computer science make them much more efficient in the activities you described, some of which falls into the stated camp. Micromanagement is universally regarded as bad.
- paxys 6y agoStill, all those should be the responsibility of senior engineers on the team, not management.
- Aperocky 6y agoI think you have a point. But should making decision that require an intimate understanding of the technical stack be part of those activities? Should drafting new features be considered under architecting? I understand that my managers are heavily engaged in these activities and their decisions are challenged by very technically minded people before they are put to work.
- falcolas 6y agoNew feature requests are certainly within a manager’s purview, but designing how those features are implemented is not - that’s your engineer or architects. Of course, if your organization expects a manager to also be a tech lead, that’s something else entirely (and not common in most non-startup companies).
- falcolas 6y agoAnd, appropriately enough, you’re not a manager. :)
- Decker87 6y agoFair point, but there's just no way all the management work fits in 20% of one's time unless they are managing like 2 people in a very narrow problem space.