> If you mean being the primary implementer of features, then probably not.
It's my belief that any engineering manager worth their salt should push back on this and argue for a seat at this table, every single time. I don't want to work for someone who is disinterested in new functionality in codebases under their purview.
I want my manager to manage. I need them to play the politics to get what I need as far as resources, to set business priorities and to make sure I’m aligned with those priorities.
I need them to then trust me to accomplish the objectives myself on smaller implementations or to lead the team on larger implementations.
I'm not asserting anything about if a manager should code, but rather calling out a statement in the article. A good engineering manager should never be surprised by some new functionality.
It's my belief that any engineering manager worth their salt should push back on this and argue for a seat at this table, every single time. I don't want to work for someone who is disinterested in new functionality in codebases under their purview.