Re:Go Slow to Go Fast
by scottschulthess on Friday December 30, 2011 @07:32PM
(#3409689)
How is that relevant to the OP?
Re:Go Slow to Go Fast
by InclinedPlane on Saturday December 31, 2011 @03:38AM
(#3410491)
The OP extols the virtues of releasing code "when it's ready" due to the hazards of rushing code out the door in an "unready" state. Unready means bad.
Re:Go Slow to Go Fast
by scottschulthess on Monday January 02, 2012 @11:49AM
(#3416437)
ah yes I agree
The biggest mistake most companies make is not rushing bad code out the door too quickly, that's hard to prevent entirely, but rather failing to take the time to fix or replace bad code quickly once it's obvious the functionality isn't throwaway.