I would like to point out that there is a practical third option given that some people say "Pay Employees A Market Salary", whereas some companies may not yet be able to afford it.

In practice when you're a technical founder (or cofounder with one), you might have three fantastic people you can't afford, great technical roles. They'd do great work for 40 hours per week, they believe in your vision and you, because your vision has a competitive advantage they can execute well with, and you can essentially generate equity value out of thin air together. They cost way less than the amount of value that could be generated, so they make sense from a business investment perspective.

But the company just might not have the funds yet.

So, besides giving out options as compensation, or giving out a market salary, the third, practical alternative, is not to hire any of the three persons, but instead work for 130 hours per week doing their 3 jobs and your job, and sleep 5.4 hours per day.

This divides to 32.5 hours per "job" (130 / (3+1)). In practice by not hiring these great engineers, you've also not hired their coffee breaks, lunches, not hired the time they spend reading Hacker News, reading about new technologies, trying various stuff such as a new framework they'd like to try, you've not hired the time they spend writing documentation or any kind of testing whatsoever, and you've not hired any downtime they spend waiting for anything whatsoever. In fact, with these concessions, the 130 hours turns out to be an exaggeration.

So, some people call the results of this "technical debt", which is a bit of a misnomer.

It's a misnomer because if the project doesn't start generating value, you can kill it and nobody has to clean up anything. So in this sense, rather than a "technical debt" - it's more of a technical option. Instead of generating employee stock options, you've created technical stock options, where if the technical results actually make it rain, then at that point the project is investable, people can be hired for a market salary, and they can rewrite all the code that you've optioned. In this very real sense it really is an option, rather than debt.

So, in practice a lot of silicon valley seems to work this way. A lot of successful people have succeeded using more or less this formula.

We've all heard lots of stories of seasoned developers being brought on to clean up spaghetti code written by a founder or cofounder, that proved the business case but was hideous, poorly documented, structured, tested, with even security and backup policies and redundancy policies making it a miracle that nothing melted down.

So when one wonders why some founders work so much - well, this is the reason.

The people who could have written all this properly from the start, weren't available given the finances the company had at the time.

Often other people aren't willing to share the vision, and if you want something built, regardless of its value, at times you just have to do it - before anyone has funded you.

So this is a very real third possibility that many people do not realize really is a kind of "option".

An essay on this is here:

http://higherorderlogic.com/2010/07/bad-code-isnt-technical-...