It depends on what appeals to you as a person I guess. Being a CTO, architect, etc in an organization definitely gives your opinion more weightage in comparison to a junior developer due to the hierarchy that exists. You will be in a position to make a greater impact in a managerial role. So if that is what appeals to you then go for it. If you're not wanting to be in an organization, want to be the lone wolf, do freelance, write blogs, do podcasts, come out with tutorials, etc then just go crazy my dude :D The world is yours for the taking when you're your own boss :P
P.S. A life lesson: Beauty lies in the little details. Black and white are perfectly good regions on their own but life's a lot more interesting in the grey areas. :)
Would you always recommend a developer to take on the management role (it manager, team lead, or CTO) if he got the opportunity to do so?
It depends on what appeals to you as a person I guess. Being a CTO, architect, etc in an organization definitely gives your opinion more weightage in comparison to a junior developer due to the hierarchy that exists. You will be in a position to make a greater impact in a managerial role. So if that is what appeals to you then go for it. If you're not wanting to be in an organization, want to be the lone wolf, do freelance, write blogs, do podcasts, come out with tutorials, etc then just go crazy my dude :D The world is yours for the taking when you're your own boss :P
P.S. A life lesson: Beauty lies in the little details. Black and white are perfectly good regions on their own but life's a lot more interesting in the grey areas. :)
What does it mean in your post scriptum? I mean, that statement can be applied to all areas of work