|
I've never been a manager, so I might well be completely wrong about this. Anyway, I think that, even as a manager, you have the option of being involved in the design aspect of things, even though that heavily depends on the kind of developer you are.
If you're anything like me, you love designing new features and writing specs that are as detailed as needed.
That's something I've been doing quite frequently, to the point where, for the project I've been
assigned to, I do most of the design of new features besides helping turning them into working code.
I sit down and think through the problem at hand, jotting down ideas in plain text files and commit them to a dedicated folder in our project's source code repo, iterating over them as I think of more efficient/elegant/fast/simple ways to implement the feature and taking into account inputs from the other guys in the team.
Again, I've never been a manager, but I think one could retain at least part of this role, provided she can cut through all the bullshit that working for a company entails (meetings where you decide nothing, chiefly). OTOH, if management is not your thing it's not your thing, I guess.
Then again, why not give it a try? Give it some time and see how that works out for you.
If you like it, great. If you don't, you can always quit and the best that can happen is that your resume will look more interesting. If I had to hire someone, I would give bonus points to someone who knows about managing and communicating with people, not only machines. |