I do not know why a developer do not know the whole picture of a system sometimes.
In my world view, technical architect knows (should know) the whole picture of the system. Managers usually deal with "other" issues, hiring, taking status/reporting status etc. which I found boring.
(So now I am a software architect)
Maybe I want to own something for businesses.
If you want to learn "business" side of things (to start your own company someday) identify whether you like "non tech" (I don't)
If you don't like, but still want to start on your own, start networking, and make friends with people who could be potential co-founders.
Finally, it also matters whether you are working in BigCo or a smaller one.
BigCO typically have fixed paths, and fixed responsibilities - even for "managers", smaller companies OTOH are more flexible, and this is where you can show initiative and learn about "business" (and practice PM skills - from your other question)
I do not know why a developer do not know the whole picture of a system sometimes.
I do not know. Maybe I want a better salary. Maybe I want to own something for businesses. Maybe I think I can do better than the manager.
In my world view, technical architect knows (should know) the whole picture of the system. Managers usually deal with "other" issues, hiring, taking status/reporting status etc. which I found boring.
(So now I am a software architect)
If you want to learn "business" side of things (to start your own company someday) identify whether you like "non tech" (I don't)
If you don't like, but still want to start on your own, start networking, and make friends with people who could be potential co-founders.
Finally, it also matters whether you are working in BigCo or a smaller one.
BigCO typically have fixed paths, and fixed responsibilities - even for "managers", smaller companies OTOH are more flexible, and this is where you can show initiative and learn about "business" (and practice PM skills - from your other question)
Haha. Yes. you are right.
One more question. Do you know why some non-technical guys (maybe manager ) do not respect technical people?
They just think IT Task is just a busy job and can create magic. They just want a low cost just high quality.
It does not mean they do not "respect" technical staff.
Driving down the "cost" is part of the "for profit" business. For software product, biggest cost is usually salaries.
So, they would try to cut cost just like cut you. ><