This is a good example of why you should always send your content over the wire.<p>As a dozen people have noticed, this article is unreadable. But it doesn't have to be. The piece coming from venturebeat.com is transferring fine. But the CDN hosting their css and jQuery is down, and they've built their site using that baffling pattern of loading nothing but an empty shell, then populating it later.<p>So we get the name of their "chief reliability officer" and a bunch of links to other articles that we won't be able to read, but no article.<p>Now suppose they had built their site like we used to build sites, and actually sent the 760 bytes of content that make up the text of the article as part of that shell. I know, I know. We'd have to download that <i>entire</i> 3kb html page every single pageload (before then downloading four megabytes of sidebar nonesense). And think of the extra engineering time they'd need to spend so that they could not only send that article at load time, but also use their (presumably) fancy article-changing mechanism that we were so near to seeing today.<p>But at least then people would be able to read things on their website.<p>We'd have one comment at the bottom asking if anybody else had seen the borked CSS. But that would have been drowned out by people who were happy enough to read the text in Times Roman actually discussing its content.
I'm working at a startup right now, and I think this is pretty accurate.<p>The freedom is nice (no hours, nobody telling exactly what to do every day). However, I will NEVER be able to have the passion for the product as I would if it was my own startup, this is just work to me.
This is weird, I can't see the article, refreshed many times. <a href="http://imgur.com/n7rlMvc" rel="nofollow">http://imgur.com/n7rlMvc</a><p>Chrome on Windows 7.
Great article. This explains succinctly why you never should work at a start-up. Just don't. Let the 'founders' do the work, that's why they're founders.