Harkins

So there's a fourth reason: there's enough of these startups that small business owners are sick of you.

I've been runing a site the last five years for tabletop gamers to do exactly this. It's busier than ever, I'm spending my nights and weekends hacking on it to keep up, and I expect some of the features I'm working on now to make that growth curve noticeably steeper.

There's huge chicken-and-egg problems in this sort of project, but that difficulty is also why they're valuable.

I didn't find him to be misrepresenting studies, and I didn't find research that disproved the claims I found implausible. I was underwhelemed by the rigor of a few of the studies he cited, but he was either citing them as historical curiosities or alongside other, more rigorous notes.

I regularly pull sources for the science I read and Taubes fared far better than usual.

This does not seem like a worthwhile tradeoff to me. And the author doesn't address loops, which often want to have special treatment of first or last elements, even/odd rows, and other small bits of logic. When you combine these things, you're going to have a combinatorial problem, I can just imagine a shopping cart table with templates like shopping_cart_item_list__table_row__last_item__logged_in__even_row__multiple_quantities__discounted_item.html

And what's with the really confrontational tone? This article would've been improved by spending a couple hundred fewer words putting words in the reader's mouth and insulting their tools/code. There's a chance this could be useful in some situations, but I sure don't want to spend any time talking to this guy.

The iPad has an SDK and app store. The Kindle has an SDK that's been in closed beta for something like two years and a bookstore that also happens to sell apps from a handful of companies.

It would be best to see a specific "We expect to spay $x to $y for this position". Even "Our salaries are in the 80th percentire (based on data from A, B, C)".

This doesn't even try to say, "We'll pay you well", it says "We'll bargain you down."

Running a small domain registry is an easy job. There are good RFCs for all the technology, your customers are a few dozen tech-savvy registrars, and you have low scaling demands. There are some availability concerns, but the knowledge for doing that right is now common. You hire a coder/support engineer to keep the servers humming and a business guy to create and maintain registrar relationships and otherwise just print money.

I thought about getting into the business in '07 but realized the entire thing depended on ICANN advancing the gTLD expansion and was a bit too risky. Four years later with minimal progress (.xxx isn't one of these, it's been kicking around over a decade) I'm glad I didn't start that business. Though ICANN has moved that along this summer...