What software engineers can learn from the rapid collapse of Fast
I think the most applicable warning for engineers when it comes to the actual work, as opposed to whether one should join a particular startup, is this:<p>> Engineers calculated the load Fast had in needing to serve their traffic. The Fast button was rendered less than 500,000 times per day - rarely needed to ever serve more than a few requests per second.<p>> One of the few warning signs engineers noticed is how Fast spent far more on infrastructure than the scale of the operation would have called for. Engineers sometimes brought up suggestions to scale infra down, and save costs - given there was not much revenue generated.<p>Sounds like the whole thing could have run on a single cheap VM, perhaps with a second one for redundancy.