I’ve heard many people talk about dropping MongoDB in to their web application as a replacement for MySQL or PostgreSQL. There are no circumstances under which that is a good idea. Schema flexibility sounds like a great idea, but the only time it’s actually useful is when the structure of your data has no value. If you have an implicit schema — meaning, if there are things you are expecting in that JSON — then MongoDB is the wrong choice. I suggest taking a look at PostgreSQL’s hstore (now apparently faster than MongoDB anyway), and learning how to make schema changes. They really aren’t that hard, even in large tables.
Social software" is about making it easy for people to do other things that make them happy: meeting, communicating, and hooking up.
This of course means every numbnuts and his dog are currently crawling out of the woodwork and regaling us with their carefully considered twaffle about what Twitter is doing, what it should do, and how much money we’re all going to make buying and selling Twitter’s IPO shares when and if they ever come to market. A particularly amusing sub-genre of said twaffle consists of various pundits of varying credibility and credulousness pontificating on what Twitter is actually worth, as if that is a concrete piece of information embedded in the wave function of quantum mechanics or the cosmic background radiation, rather than a market consensus which does not exist yet because, well, there is no public market for Twitter’s shares.2
We’re going to cut straight to the chase. Modern browsers can animate four things really cheaply: position, scale, rotation and opacity. If you animate anything else, it’s at your own risk, and the chances are you’re not going to hit a silky smooth 60fps.
If you’ve got Markov problems, I feel bad for you son. I’ve got 99 problems, I feel bad for you son. I’ve got Markov problems, I feel bad— Chad Etzel (@jazzychad) November 6, 2013
The problem with hyper product-oriented entrepreneurs is that they often have one tool in their pocket: Making a great product. That’s both admirable, and dangerous. Once the initial product is working, the team has to quickly transition into marketing and user growth, which requires a different set of skills. It has to be more about metrics rather than product design: running experiments, optimizing signup flows, arbitraging LTVs and CACs, etc. It’s best when this is built on the firm foundation of user engagement that’s already been set up. In contrast, an entrepreneur that’s too product oriented will just continue polishing features or possibly introducing “big new ideas” that ultimately screw the product up. Or keep doing the same thing unaware of the milestone cliff in front of them. Scary.
Also, there’s the fact that both “NSA Files Decoded” and “Snowfall” so clearly take the form of what I like to call “The Editor’s Prerogative.” What is The Editor’s Prerogative? It’s when you take a piece of journalism and make it huge in scale and elaborate in delivery so that it is more in line with how important an editor thinks the story is than how new audiences actually want to consume it.
Too big for Excel is not “Big Data”.