>>"...every minute spent on infrastructure is a minute less spent shipping features." Completely true. This does not mean that we should spend zero minutes on

>>"...every minute spent on infrastructure is a minute less spent shipping features." Completely true. This does not mean that we should spend zero minutes on infrastructure This does mean that we should ensure that every minute & dollar spent on infrastructure is well-spent - will actually produce, for the customers, the developers, and/or the company overall, a return of sufficient value. I used to be all about planning for scale early. But I've actually found it's better to plan to build one or two throw-away versions, built well as we can while being fast and with only minimal scaling features, THEN take the lessons learned (about real features, usage patterns, & loads that will need to be supported) and apply these to building out the more scaleable versions. The initial cheap, cheerful, & disposable versions provide initial traction, a lot of knowledge, and a known & limited technical & financial debt, but the 'killer feature' is zero technical lock-in when you go to design & build the scalable version. YMMV