Open your project's sources

Posted by scooletz on January 23, 2011 · 1 min read

In the Ryan King’s presentation you can find a plenty of good/best practices of Twitter teams. You can find tips how they use Cassandra, what kind of an awesome id generator they provide (and it is an open source: Snowflake). I do read about open s ourcing as a way of getting your apps better, but I do not know where are the boundaries of showing what you’ve got vs. giving everyone the omnipotent ‘How to steal my users and dethrone me’ book. Can everything may become public? What are the root secrets you should not reveal? Any thoughts?

BTW the whole presentation can empower you in using no-sql. It’s a must-see.


If so, the power of the indescribable almighty Business is great indeed;-) It seems that open-sourcing becomes more and more popular, and maybe, needed if you want to have a high quality solutions. Who would it test better than a group of nitpickers :P

by scooletz at 2011-01-24 21:35:16 +0000

I guess that even if they opensourced the whole twitter code (which they are not doing), nobody would detronize them thanks to using this source. There's a lot more to success than a good technical implementation. As an answer to your question I would say that the secret is all those little things, most of which living on the business side of the product.

by dro at 2011-01-24 08:56:46 +0000

My tools

[PL] Master of Aggregates
[PL] Master of Aggregates
[ENG] My free e-book
[ENG] My free e-book