Shared publicly  - 
 
Nice post from re: v1 vs v2 of software products.

It's exciting to be back in the v1 stage of things, but even within Google, I tried to advocate for a fast v1 and then a slower v2 iterations of features. I'd like to think of it as a fast pass, then a slow pass. However, and this is a big however, this requires the commitment of engineers to WANT to take a slower pass through the code later. Commitment + Follow-Through! Otherwise, technical debt starts to accumulate.

It's a hedge that the accumulated waste of unnecessary scaling is less than the efforts to put out a scaling fire - which I'd be totally fortunate to have - Good problems. 1% problems.
1