Tips for switching from A Project Manager to a Developer [closed]

Closed. This question is opinion-based. It is not currently accepting answers.

---

Want to improve this question? Update the question so 开发者_C百科it can be answered with facts and citations by editing this post.

Closed 3 years ago.

Improve this question

I am currently trying to make the transition from a technical PM to a Developer.

Obviously this depends very much on current level of knowledge / experience, but are there some key things that a PM (who also codes regularly) might have missed from not strictly working as a Developer.

Also would a course like this help in the right direction?

http://www3.imperial.ac.uk/computing/teaching/postgraduate/msc-computing-science/description

Considering I want to work on Audio/Video/3D ideally, I feel this course could be a good leg up?

---

As a technical PM you have the advantage of knowing the terminology etc so that is at least a heads start. As to making the switch check out information on areas such as

• computing fundamentals - low level concepts on computer hardware, network and protocols.
• algorithms - for an understanding of sorting, graphs, networks, trees, etc.
• architecture and design - web application architecture, messaging architecture, UML, use cases, documentation.
• programming languages - OO, scripting and AI (at least to get a feel for the types and applications)
• business end of programming - software estimation

This is a broad spectrum of areas that you would need to have at least some exposure to for the transition. In fact it might even be useful if your current employer allowed you to work as the developer on a small part of a project. You'd certainly gain respect from the developers on a project coming from the technical PM role and could even enlighten the developers.

---

If you have a passion for working in an area, seriously consider the amount of creative freedom, in your experience, developers have as compared to PMs. Make sure that's acceptable to you.

Nothing is worse than having passion in an area, but little or no influence.

As far as technical abilities go, the only thing to do is to code. Any classes primarily will act as ways to ensure that you do so, and do so in ways that will teach you. But at the end of the day, it's going to boil down to time spent writing software.

If you really want to become a great developer, learn at least one language radically different from the languages you know. If you're a Java/C++/C# kind of guy, learn something that will really torque your brain like Haskell, Erlang, or Scheme. To just learn really good OO techniques, learn, read, and write some Smalltalk.

---

The best thing to do is to spend ten years or so programming during every waking moment. That's what worked for me!

---

First of all get start practicing to type all day ! Then get ready to work on minute details which a developer works on everyday like... code shortcuts, coding styles, commenting etc.