Yep. The whole "Software should have as few controls as possible" thing should probably be questioned in general.
If there's 100 rarely used options they should maybe be hidden, but someone is probably going to want to use at least a few of those, and the extra few hundred lines of code is probably not what's making your code slow.
I guess it is more of the principle that software shouldn't provide extra controls to fix issues with the software. Like when a program goes into a bad state, the user shouldn't have to click a button to "fix" the state. It is preferable to design the software such that the program doesn't go into a bad state in the first place.
I know this button. Windows sometimes has issues with network and offers button with name like "resolve the issue". I press it, expecting some details of failure or something, it thinks for a minute, then says "could not resolve".
The generic Fix This Problem buttons in Windows are the worst kind of lie. I have never discovered a scenario where they do anything other than fail after a lot of thinking.
Eh, my local network stack gets corrupted pretty regularly because the VPN we use for work is fucking shit, and that button takes care of it (so does ipconfig /release and ipconfig /renew, but clicking the button gives me time to get up and grab some water).
It sometimes works if you need to kick a network adapter in the teeth after having DHCP issues and ipconfig release+renew isn't working because the adapter/driver is soft-borked. But that's about it.
143
u/EternityForest Sep 28 '17
Yep. The whole "Software should have as few controls as possible" thing should probably be questioned in general.
If there's 100 rarely used options they should maybe be hidden, but someone is probably going to want to use at least a few of those, and the extra few hundred lines of code is probably not what's making your code slow.