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.
Tuesday, October 20, 2009
Why a good programmer can also be a good CEO
Subscribe to:
Post Comments (Atom)
2 comments:
i would like to point out another similarity: both live in a fantasy world, therefore have surrealist visions about the surroundings and, especially, about their capability
Hehe, although I'll have to agree with you about that fact that they both may have an augmented image about their capabilities( which probably allows them in the first place to exceed their limits) , I'm going to disagree that they both live in a fantasy world.
The CEO may live in a more ethereal world, but the programmer, knows what it means to confront a concrete system, although with minimal interaction.
It still needs a little practice though, to reach the level of the CEO, for it is, you see, sublime art, to control the seen with the unseen, the concrete with the abstract, the matter with the mind!
Post a Comment