More often than not I've seen founders completely neglect the mundane business of the day to day running of the company. Usually at the expense of their most loyal early employees, if not at the expense of the entire business itself.

It has come to a point where I've pretty much had it with those serial-entrepreneur types who pride themselves on having started an x-number of start-ups.

If you're incapable of, or simply completely uninterested in, running a business, don't start one. It doesn't make you a courageous entrepreneur, it makes you and adrenaline junkie who gets their kicks at the expense of others.

None of this is limited to code or tech in general. I've seen it in all kinds of areas. You may love doing X, but once you start a company doing X, running that company becomes is your job, not doing X.

If you're a founder/CEO and you've hired others to code, for you coding is a now hobby you can pick up in whatever spare time you have (probably none). To do it inside your own company when you should be taking care of your company and the people in it is selfish and self-indulgent.

And I thought he would recommend spending times with family and friends, reading books and taking walks.

I was expecting much more from that headline. The point is that you shouldn't do Don't Break The Chain because you might have other responsibilities? I don't see how it contradicts the original article's advice and I also don't think it was aimed toward CEOs.

While i don't agree with this completely there is some truth to it. I ran an accelerator funded gaming startup for 2 years and was obsessed with development and coding. Most of the real CEO work was done on the side without much focus. In the end i think that played a big part in failing, because ultimately we ran out of money before profits were healthy. This could have been prevented if i had talked to investors earlier and more, focusing on the vision and shorter term goals to keep liquidity in check.

It's not that i didn't see it coming miles away, but it was still too late.

And i thought the article will somehow tell us that jeresig argument to code everyday was wrong.

i genuinely thought that the article should do justice by putting the same effort as jeresig post. Yeah OP argument that "CEO job is not only coding" is not wrong but i expect OP will argue that "code is not the onpy thing developer like jeresig do" based on the headline.

It's so classic that a popular post pops up and the next day we have its inverted version.

The web site has severe UX problems.. It is first loading, then loading and again loading... Go back does not work neither.

"I rarely write code, but when I do..."

Can anybody come up with a good ending? :)

For those who build stuff and hire vendors.. Is it better to hire vendors that know technical stuff or any vendor will do the same job more or less if they are correctly briefed about the product?