> most programmers will stop at age 35 and become management level.

That's not going to happen to "most" anything. There are always fewer spaces at the next level up the pyramid. Usually drastically so. What's the "programmer" to "manager" ratio where you are?

A common misconception here is that we all get to be CTO someday.

Most of the CTO's I know quit from somewhere to become the CTO at their current place of employment. I don't recall meeting anyone who "moved up through the ranks", but perhaps I'm not fully informed or can't recall those instances.

I'm not even talking about "moving up" to become CTO or some other exec. I'm talking about just getting into that game.

Especially with inverted demographics hurting anyone under 30.

Not to mention that lots of programmers make bad managers.

Okay, I hit 35 on June 2nd, and become a 'Risk Manager' on June 1st. Why? Because I realise that, in corporate life, technical skills are a serious roadblock to a career.

(Okay, I'm drafting a business plan on the side for a consultancy. I am hoping the non-programming job will allow me capacity to work outside my liberal flexitime hours. All advice welcome)

"technical skills are a serious roadblock to a career". You've discovered Putt's law: http://en.wikipedia.org/wiki/Putt%27s_Law_and_the_Successful...

Software engineers shouldn't undervalue having vertical business domain knowledge.

Beware of the "Peter Principle" though (people rise to their level of incompetence).