I feel like you could drop "in household appliances" from that statement and still be telling the truth. I'd be willing to bet that anyone reading this could think of examples in software where those making product decisions seem to be operating off of these principles:
* Refine relentlessly (vs stop improving what doesn't need improvement)
* Be heavily state-dependent as a way to minimize presentation of options. But don't call attention to state.
* Minimize any affordances. Rely on implicit interaction patterns you assume the user has already learned.
* Minimize everything. Remove options. Hide what you can't remove. The less the software does, the less the user has to think, right?