The best project managers I've had have identified and removed obstacles for me (including things like - attending mandatory meetings, so the devs don't have to). Other good managers have also reigned in my ideas enough so that we implement what is attainable. Bad project managers have had an obsession with statistics, spreadsheets and tools like Jira. Most project managers I've had have been bad/indifferent, but wit…
Ask HN: How can I become a proper Project Manager from a Programmer?
51–60 of 66 posts
Re: Ask HN: How can I become a proper Project Manager from a Programmer?
#5299% of the time "Project Manager" means "Project Facilitator." The key aspects of project management are gating, communicating up, and communicating down. Gating: Keeping things that aren't The Project from becoming The Project without being properly defined (time, deliverables, budget, resources). Communicating Up: Letting business owners and stakeholders know the status and cadence of the project, what the project…
I can read code and write it too, but mostly program simple front-end things or hack together side projects.
I'm good at telling people what they actually want from each other when they start arguing in a meeting. I'm the one who gets asked to write, simplify or clarify the concept of a new product. And as a generalist I will be asked about everything out of scope of the others (everything with media, much research, occasionally personal issues).
Regarding gating I have limited experience, but will be the one to try to get things out of the "MVP".
I'm currently in a very small startup and want to stick to it until after the initial launch of the product. Than it should become clear if things work out or not. I'm not sure though if I want to stay with the startup for further products to be launched.
Re: Ask HN: How can I become a proper Project Manager from a Programmer?
#53The best project managers I've had have identified and removed obstacles for me (including things like - attending mandatory meetings, so the devs don't have to). Other good managers have also reigned in my ideas enough so that we implement what is attainable. Bad project managers have had an obsession with statistics, spreadsheets and tools like Jira. Most project managers I've had have been bad/indifferent, but wit…
1) Providing direct input, rather than summarized versions (even good project managers lose track of details and misstate things).
2) Learning what your project manager and others do. This can reveal corporate bullshit, but also enlighten you as to the amount of work that other middle-manager is actually involved with (and you may be surprised by their technical competence, or disappointed).
3) If you want to move out of a managed role in your company as a developer, and into a role that affords more authority and direction of projects (your own vision, if you will), this is a good opportunity to learn and to get face-time with people that you'll be interfacing with later, or that'll give you a promotion.
4) You don't find out secondhand what the corporate decisions are, you were there to witness them.
5) You learn what to say and what not to say to management. Never, ever, say that X is almost done when X is a prototype or subsystem. You speak about the completeness of the whole system, and then break down to the subcomponents. You learn the art of understating progress so that you don't seem to be behind (because you aren't, hopefully) but also to avoid the appearance of being further ahead (because it's just a prototype, or it's only one subsystem, or whatever).
I learned a lot at one of my jobs by being invited, as a lowly new-hire tester, to a few meetings with management. In particular, the smallness of scope of my portion of the project to the project as a whole, while still being on the critical path. Particularly, those meetings sat at the intersection of electrical, chemical, software, and mechanical engineering. That's where I learned what systems engineering was really about. A lot bad about that company, but outside their mismanagement of software, their understanding of systems management was actually pretty solid. That mismanagement was changing, but a lot of us software types didn't realize or understand our role in the whole process either (overvalued ourselves).
Re: Ask HN: How can I become a proper Project Manager from a Programmer?
#54Please take a look at the IEEE's Software Engineering body of knowledge. It will give you an outline of the topic as well as pointers to what reference material you can consult. https://www.computer.org/web/swebok
Now, some people will try to tell you that project management is all about going to 3M with a forklift and getting multiple crates of stupid post-its. It's not. There's much more to it than just sticking post-its.
An engineering manager represents the ENGINEERING interests of a project, not only pushing features and saying "yes". Being a good manager is not about saying "yes", it's also about saying "no"... understanding tradeoffs and balancing them.
Saying yes to features all the time and discouraging quality will only create a culture of checked-out paycheck zombies.
Re: Ask HN: How can I become a proper Project Manager from a Programmer?
#55You don't have to transition. Think hard before you do. I became an engineering manager at around 26, and did it for another 5 years, and thought that was my future. But I transitioned jobs and ended up getting back into development, and realized a few things: - I hate meetings, and PMs go to meetings. A lot. - PMs have less control then you probably think. - Writing code means I get to actually make stuff. At the en…
I became a Project Manager right out of college after completing my CS degree and did it for ~8 years. I believe I was pretty good at it, but I don't think I ever once really enjoyed it. I spent all my free time coding, and eventually realized I probably should have been doing it as a job all along. I then spent about a year self-teaching, moved half-way around the world to San Francisco, and found a job that, more often than not, I actually enjoy going to every day.
I'm sure some people really enjoy Project Management, but each of the three points in the parent comments ring extremely true for me, so for now at least I'd much rather be coding!
Re: Ask HN: How can I become a proper Project Manager from a Programmer?
#56You don't have to transition. Think hard before you do. I became an engineering manager at around 26, and did it for another 5 years, and thought that was my future. But I transitioned jobs and ended up getting back into development, and realized a few things: - I hate meetings, and PMs go to meetings. A lot. - PMs have less control then you probably think. - Writing code means I get to actually make stuff. At the en…
You never feel a sense of accomplishment for making sure your developers are happily productive?
I'm a manager now and my team's high output and positive morale makes me extremely satisfied and proud.
Re: Ask HN: How can I become a proper Project Manager from a Programmer?
#57I've recently gone from Developer to Technical Product Manager, and I believe the following traits are important: 1) Communication on both a technical and product level. This allows you to act as a bridge between sales/marketing/management and the developers. See #2 2) Speaking two languages: Code and Product. This is where being a former developer comes in quite handy, as you can only learn Code through writing it,…
Cheers!
Re: Ask HN: How can I become a proper Project Manager from a Programmer?
#58My only advice is to not simply jump into a management role because it is the only career path you see. You can still be technical and progress your career! I definitely encourage you to try and experiment different roles, though, as this brings you versatility and understanding the lifecycle of a project.
Project management isn't really a management role. They are usually peers, often on a lower payscale than engineers.
Re: Ask HN: How can I become a proper Project Manager from a Programmer?
#59Re: Ask HN: How can I become a proper Project Manager from a Programmer?
#60You don't have to transition. Think hard before you do. I became an engineering manager at around 26, and did it for another 5 years, and thought that was my future. But I transitioned jobs and ended up getting back into development, and realized a few things: - I hate meetings, and PMs go to meetings. A lot. - PMs have less control then you probably think. - Writing code means I get to actually make stuff. At the en…
I think it can be useful to have demonstrable working experience in management, even if it wasn't your career choice.