We are inching closer

Commiting to deadlines is a bad thing. atleast in public. Once you commit to a deadline you have two options,

a. Ship your product no matter how sucky it is.

b. Add x days and proclaim new deadline. repeat n times. (Vista release schedule perfected this technique)

At CampusChai we are working on some really cool stuff. So we are not going to commit to any deadlines, it will be ready when its ready.

What do you folks think is the best code release technique?

a. Users love broken code and sites that don’t work.

b. Code it and throw it out there and let your users figure it out.

c. Make incremental improvements. Make sure it works 80%.

d. Develop an n-tier architecture and put it through a unit, functional,UAT, pre-alpha,pre-beta… testing.

btw, Here is a sneak preview of what’s coming your way.