I don't think I agree with his feedback loop chart. He claims 5-15 seconds to validate that a local code change works is highly effective. But in practice, th

I don't think I agree with his feedback loop chart. He claims 5-15 seconds to validate that a local code change works is highly effective. But in practice, that amount of time makes for one of the most unfriendly environments to be in. For example having to wait 5-7 seconds for an AWS SAM (Serverless) Lambda function to be built and locally invoked is so much worse than making a code change in a Flask, Rails, Django, Laravel, Node, Phoenix, etc. app and seeing the change as fast as it takes you to focus your browser and reload, or running something in a REPL. When you do such a thing 100 times in a few hours those 5+ second pauses are deadly for motivation and productivity. It's a constant reminder at how crappy the development experience is and it's also not long enough to do something else while it completes so you're stuck wasting your life away on a tool. Is anyone really happy when they need to wait 10 seconds to see a change when developing a web app? I think the web context is important because you can relate to it from past experiences. In 2001 there was a near instant feedback loop with making a change to a PHP page and reloading the browser. Anything less than that 20 years later seems like a direct downgrade, especially considering computers are probably 1,000x faster today.