Post History
So, I'm in the process on writing a hardening guide for Windows 10. Similar to http://hardenwindows10forsecurity.com/index.html, but different in scope and style. I wondered, if informing about "B...
Question
technical-writing
#3: Attribution notice added
Source: https://writers.stackexchange.com/q/32441 License name: CC BY-SA 3.0 License URL: https://creativecommons.org/licenses/by-sa/3.0/
#2: Initial revision
So, I'm in the process on writing a hardening guide for Windows 10. Similar to [http://hardenwindows10forsecurity.com/index.html](http://hardenwindows10forsecurity.com/index.html), but different in scope and style. I wondered, if informing about "Bad/Worst Practices" would be a thing that should be avoided? The thing is, I read several blogs in the past that told to avoid this. According to them to not give the user the knowledge that something like this exists. Honestly I feel this is quite a weak argument. If I try to explain to users why they should do something in a specific way, might it not be meaningful to tell them why **not** to do it in a different one? From a didactic viewpoint I would consider the following points regarding this: - Give only very general informations, not an actual How-To. This would mean they still have to look somewhere else - fine, if they want. - No URLs to external guides that show this "Bad Practice" in action. Similar to the first point. If they want to use it still, I can't prevent it. - Make it clear by a panel that this is considered as "Bad/Worst Practice" and should not be used for given reasons. I think this sounds reasonable, but as always: Open for additional/different thoughts.