[laserbeam]

Honestly, that should be the mindset of IT experts in general. Any reset/reset should fix everything and bring the system to a known functional state before doing any work.

Obviously you don't want to have to restart to fix issues, but having that as a fallback (especially for issues you didn't predict during development) is great UX.

[hnbear]

Isn’t this the fundamental point of the push for impotency in configuration management tools?

You just need the state set to “good”, regardless of which bits need to change and current state. Hit the button and it makes it “good”.

[chimeracoder]

> Isn’t this the fundamental point of the push for impotency in configuration management tools?

FYI, The word you're looking for is idempotence (EYE-dem-poh-tense).

[smelendez]

Thank you. I thought this was some reference to giving people config options that don’t actually do anything.

[hnbear]

No, just phone autocorrect, and too late to edit it.

Typing too fast and not paying attention.

Although I do like your interpretation. Maybe I’ll call poorly implemented or useless functions impotent from now on.

[hnbear]

Yes, autocorrect.

[macintux]

Hence Erlang. When in doubt, restart the part of your application with bad data.

[fifteen1506]

I refuse.

I stand my ground on using quotes.

"Reset" "Internet".