Making a lateral Move to make a change (withing the same organization) from developer to more of PM-Analyst Role
-
you sound like Father Jack Hackett! Yes to good or Bad?
-
Good or Bad Idea?
Without context, it could be either I suppose. Developer to PM? doesn't sound that lateral to me.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment "Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst "I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
-
Good or Bad Idea?
Terrible for me, but may be great for you. There's no one size fits all answer to this question. It depends on the individual and the organization in which they work. /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
-
Good or Bad Idea?
I'd say Good, making lateral moves will get you experience in more activities of the company, which may be a gateway to a future vertical move. All this on a purely theoretical basis as we know nothing of the place.
GCS d--(d-) s-/++ a C++++ U+++ P- L+@ E-- W++ N+ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
-
Good or Bad Idea?
MarcusCole6833 wrote:
Good or Bad Idea?
Why might be good or bad?
"Coming soon"
-
Good or Bad Idea?
No context no sensible answer - I do know of a few people who did that move and it was a disaster (me being one of them).
Never underestimate the power of human stupidity - RAH I'm old. I know stuff - JSOP
-
Good or Bad Idea?
It is up to you, but it is not a move that I would make. I made a move from developer to the 'Lead' of developers and all I ended up doing was less coding and more babysitting of other developer projects. To me a PM would be along the same lines, less coding - more babysitting. Just not for me. I went back to my developer role and couldn't be happier. I am 64, so that also plays into my thoughts. Good Luck!
-
Good or Bad Idea?
I can't actually answer for you but I made a lateral move about 16 years ago and it turned into the best choice I made. It lead to a more flexible and rewarding position that then developed into a promotion to a corporate level development team (I work for a fortune 50 company). Now that promotion is potentially setting me up for the likely chance at yet another promotion here in the next few years or less even.
-
Good or Bad Idea?
You ask an impossible question, as the answer depends on you. Project management is a LOT more stress, as you will have infinite responsibility and finite authority with which to handle those responsibilities. Can you be happy shuffling papers and answering the phone and spending even more time in meetings? Are you good at business writing, as you'll do a LOT of it. And herding cats -- did I mention herding cats? If you're a good programmer, finding satisfaction may be difficult. There are also a LOT less PM and analyst jobs than programmers. But it really depends on you. A friend of mine was a good programmer, but he just didn't enjoy it. He went analyst/PM and is happy with the move 2 decades later. He's worked for a PMO (project management organization) and is currently a program manager, managing half a dozen PMs who directly manage a large number of related projects. I made a similar move at the same time, and have some regrets. I've tried moving back into full-time programming, but my experience as a PM/BA/TA keeps pulling me back into the PM side. But it's not all bad -- I'm employed and generally happy with my career, even if there are times I'd like to be sitting in a dark room where the door has a slot for pushing pizza boxes through ...
-
Good or Bad Idea?
My 2 cents is that my previous job was officially titled "Programmer/Systems Analyst," which included the added benefit of being project manager, full stack developer, systems administrator, database administrator, and keeper of the ESX(i) servers. Pretty sure they got their money's worth; I sure learned a lot, too. Basically, make sure roles are much better defined in the future. Also, "Go not to the elves for advise for they will say both yes and no."
-
Good or Bad Idea?
your mileage will vary depending upon your own circumstances. in my career. I went from being a coder to being a Supervisor of a coding team. Then side stepped into a lead dev role in a different organization. Then jumped ship because it sucked to a PM role. It was good for quite awhile. Then was let go and found a full time coder role again. Enjoyed it quite a bit. Now I am a "director" (Very small team) and I get to Code, Lead and Do PM work. It works very well for me. I really love coding. But I find that I also like having lots of influence in company technology decisions. So this role fits for me. Everyone is different.
To err is human to really elephant it up you need a computer
-
Good or Bad Idea?
I am glad to see this question asked as over the last 2 or 3 years, I have started to think about my career. I took a job 9 years ago with the idea that I would progress to a mid level dev, work up to senior role, maybe get into a team lead role. The key was I was not going to be content doing the same thing year 1 as I was year 10. Well I ended up not progressing at my place of employment. I have fixed that problem. But even with greener pastures, I still just don't get that rush and feel writing code fulltime will get me to retirement. My pursuit continues on finding that balance. I feel like there is a niche for analysts and management with the tech background in the weeds of the products and teams one works. I feel could be more valuable than some textbook read PMP or some web certified professional thats efficient at buzzword bingo.