4 ms·
-AOL. I work in automation&controls in the oil industry, and my customers are always puzzled when I start to whittle away at the features suggested, rather than
by lb1lf 6y ago
-AOL. I work in automation&controls in the oil industry, and my customers are always puzzled when I start to whittle away at the features suggested, rather than adding to them; my mantra being that 'If it isn't there, it cannot fail.'
My experience echoes yours - I keep my appliances as simple as possible, both at home and professionally.
Add complexity wherever you have to, not wherever you want to.
- jiggawatts 6y agoI work in the IT systems integration industry, and I have unironically used the phrase "fewer moving parts" when describing the benefits of my preferred architectures.
- tuatoru 6y agoThis could be interpreted either way in this context. So, in the context of microwaves, does this mean you prefer software-controlled ovens instead of simpler ones with mechanical timers (which have lots of moving parts), or the reverse?
- ethbr0 6y agoIf no one attempts to remove features, bad features make it into the product, adding complexity and sapping time from good features. If someone attempts to remove a good feature, someone on the team should be able to successfully argue for it in 3-5 sentences.
- toomanybeersies 6y agoNo code runs faster than no code. No code has fewer bugs than no code. No code uses less memory than no code. No code is easier to understand than no code.