All of these apply to software development as well, but especially that first point. I'm on a project right now that has a bunch of things that can be simplifie

All of these apply to software development as well, but especially that first point. I'm on a project right now that has a bunch of things that can be simplified. Some duplicated state, multiple code paths for computing the same thing, etc. When problems arise it's very tricky to debug and it's almost always caused by that complexity. The temptation is to just add another layer of checks or validation on top of it or make a slight tweak. But of course the best path is to just roll up your sleeves and work to remove as many moving parts as you can. Most of our bug fixes have actually resulted in substantially fewer lines of code. Anyway, the point is to always try and keep things simple, and even better to make sure that principle is followed in the initial stages of design.