[dankohn1]

Great piece. What this means for me is how important it is to have a low latency feedback cycle. Even a cryptic error message, if it's immediate, will let me quickly try enough things to find the correct approach.

One of the most frustrating weeks I've spent was modifying bash scripts to work around wonky functionality on AWS Elastic Beanstalk. Every time I tried something, I had to wait 30 minutes for it to deploy and then examine the error message to see what was wrong.

Of course, in the meantime I would get distracted by something else, so the cycle time was even longer.