-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 It's nothing new, rather my rules about startup code:
[1] - Write code First step: if you have an idea, then you need to write some code to get along with it. The idea itself doesn't sell. [2] - Code Right Your code is an asset, so DoS, DDoS, XSS and scalability should be rule number one, before releasing any code. [3] - Relase Early Forget alpha modes, jump into beta relases and start evangelizing right from the start. [4] - Dont worry, be crappy If its beta, then you can be crappy, but you shouldn't be in that state very long. [5] - Release often 100% of the times, an airplane filght is not on the right track. Always in constant moves, it adjusts the flight to the flight plan, so you should do the same. Adjust your code with often releases. [6] - It's done when it's done Expectation management. You're in beta mode, your users start asking for more features, you release often, but you forget the other rules, in no time it's hell on earth for you. So, start managing user expectation with a bundle of features in a adequate release plan. [7] - Think Freemium Freemium is the mother of all beta modes and in production state the food for your evangelists. You must give something for free to start a contagion and lowering the adoption barriers for your code. - -- Vitor Domingos Paradigma.pt -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFGeprszLeQsaqPtNIRCuiBAJ4kF09sxfY7cG5qYtS61883DEx1vACfZuMN ckt8G3GBDAhr+9EgOoLIohg= =3ga8 -----END PGP SIGNATURE----- _______________________________________________ tce mailing list [email protected] http://lists.paradigma.pt/mailman/listinfo/tce
