Why a good programmer can also be a good CEO

What? You don't believe me?
Here are some arguments supporting this idea:

So, similarities:

- both work with an abstract model of the system
- both give directives to some executing subroutines
- both ( supposedly ) understand the underlying, complex, intricate implications that a minor change can have in the system
- both have an overall view of their program
- both know that nothing is perfect, so they accept that debugging/optimizing their program is a necessity
- they are both masters of their domains
- their will is always fulfilled, even if is good or bad
- they both have red eyes from too many logs/reports they've read
- in many software start-ups the CEO is also the programmer and all in between..

Differences:

A lot probably, but they are all irrelevant.

So, know tell me that companies didn't screw up badly by not making a career path like this:
junior programmer -> programmer -> CEO.