Nikhilesh Rao

I have been involved in innumerable discussions with Engineering group from the start of my career about the "quick and dirty" approach way of doing things. My default position (not always correct!) has always been, lets get the feature out there, see if it has any traction, study user behavior and then scale/refactor it from there. Obviously, the engineering team's default position (once again, not always correct!), has been that we will spend more time doing a feature "properly" then the quick and dirty approach.

Once again, Eric Ries of the customer development fame, has written a great post on finding a balance between the "quick and dirty" approach and repaying technical debt. More here