In his post on his Medium.com site Ted Blackman looks at something he calls "Lug-nut driven development" (or, shortened LuDDite). He breaks it down into a few different suggestions including "build the whole thing badly" out to "automate stop and start".

These are practices that I’ve applauded myself for doing at the beginning of some projects, and kicked myself for not doing early enough in other projects.

The full list suggests things like:

• Building a system that goes through the whole flow first (not perfect) then come back and refine
• Testing as you go instead of coming back at the end and retrofitting them
• Log everything you can then cut back and refine
• Plan out the error handling before hand to help make it consistent
• Be able to "stop" and "start" the system easily

While not all of these are specific to web applications there's some definite helpful advice in here, especially to those starting out on new projects.