Nice article. AFAICT, "social" is a bit like TNT. If you don't know how to handle social/TNT and you're handling social/TNT, you're in deep shit. If you mention social/TNT, you better have a strong argument for why you are able to use it correctly. I've heard <i>very</i> well connected and regarded folks say "when we get to scale, we can monetize easily...". The question back is always "awesome! when can you come back with proof? Say 50k users and growing?" Carrying the analogy forward too far, there are some applications that are 100% dependent on explosives, but they're few and far between (see Fireworks), but I hear tons of people talking about social applications as though they're super-common and easy. More often than not TNT/social are added to existing applications to enhance the application: see Mining or Music; rarely are TNT/social used to build stand-alone applications (see Fireworks, Facebook, Twitter).<p>I'm definitely in favor of the article's advice to: build a tool you'll use, get others to use it, figure out how to add network effects, then figure out how to add social. Much less risky and, probably, much <i>more</i> satisfying.<p>From TFA:<p><pre><code> my latest venture is Buffer,
a new Twitter application.
</code></pre>
I appreciate the author's points on adding-social and I'd certainly be curious about his perspective on building an applications that is 100% dependent on a capricious social network.