This is why you should apply the Dumb&Fast approach for a first ~MVP version, plan to throw it away, then apply the smart & careful approach for the more durabl

This is why you should apply the Dumb&Fast approach for a first ~MVP version, plan to throw it away, then apply the smart & careful approach for the more durable versions. The first version should get out there quickly and validate, adjust, and/or destroy your assumptions about your customers, systems, usage & load patterns, etc., then that deeper knowledge and more careful approach goes into the next 'real' version. Prevents premature scaling & optimization, and you never have to pay the tech debt from the 1st version. Source: been there, done that, works great.