I am Back to the Code World

I am happy to be able to code for few days, in a closed office.

Why a CEO code? Because I love it.

Is it all? Not really.

I was educated thousands of times by everyone that “you should not code”. A CEO should not code. The more neutral version was: “A CEO of a company of your size should not code”. But after few years, I realized that the traditional wisdom is wrong.

Imagine this. No matter how seasoned, and high-ranked, when a person leave a company, he has to start a new company, and in the first months, the time was spent coding for the guy. Let’s take my favorite programmer Bred Tayler as example. He wrote Google Maps, and he was famous, but when he started FriendFeed, he was a programmer again, and write the first line of code. Then he went on to be acquired by Facebook, and became a CTO. CTO of Facebook is a good position, but I suspect when he starts his next startup, he may well become the first programmer, and start to write code again.

How do you justify an hour of Bred in Facebook as CTO, and the one hour of Bred as the first programmer in a new startup, especially when the second hour comes after the first hour? He is the same person, and his value of time is the same, and how do you justify that writing code is not the duty of a CTO?

A code-writing CEO’s advantage is that if he has some expertise in coding,