Totally can understand with missing out on a new Greenfield project with that type of scope. Probably a good decision to make the move.
"I know people with 10 years of experience in the IT field that can't architect a medium application." - Not everyone has the ambition you have :) You have no idea it is to breeze through as below average in big corporations.
I understand now with the just, but you should know if people recognize you as the guru of the technologies they are working with, becoming an architect would be a side-effect. (Imagine everyone asking for your opinion for implementation details)
-Grain of salt section-
Hmmm PM tends to be on a more business side of things. They identify what the users want and make the roadmap for the developer team. It gets blurry but more techy people don't like becoming PM's because you end up not programming and just spend your time in meetings.
But as Chris says in his follow up, Stick it out for at least a year and if it doesn't feel like your developing new features time to make the switch again.
Advice on this, keep your data structures and algorithms skills sharpened. Try to do 3 problems a week. By the time you decide to make a move, you'll kill any interview :)
Totally can understand with missing out on a new Greenfield project with that type of scope. Probably a good decision to make the move.
"I know people with 10 years of experience in the IT field that can't architect a medium application." - Not everyone has the ambition you have :) You have no idea it is to breeze through as below average in big corporations.
I understand now with the just, but you should know if people recognize you as the guru of the technologies they are working with, becoming an architect would be a side-effect. (Imagine everyone asking for your opinion for implementation details)
-Grain of salt section-
Hmmm PM tends to be on a more business side of things. They identify what the users want and make the roadmap for the developer team. It gets blurry but more techy people don't like becoming PM's because you end up not programming and just spend your time in meetings.
But as Chris says in his follow up, Stick it out for at least a year and if it doesn't feel like your developing new features time to make the switch again.
Advice on this, keep your data structures and algorithms skills sharpened. Try to do 3 problems a week. By the time you decide to make a move, you'll kill any interview :)
Thanks a lot for this great advice, I will take it in consideration for sure along my career.