Embed Notice

@skinnylatte Honestly this joke example is better than some of the technical documentation I've read, as a software developer / sysadmin, at least it lists the path you are expected to find some config file in, so many docs will just say "and go change the foobix setting in the config file" without ever saying _where_ the config file is located (or what you are supposed to change it to), so you have to strace the process to figure out where it loads configs from which is a ridiculous thing to have to do. Or something will say to "frobnicate this setting" but won't tell you what the setting actually _is_, is it "setting=Frobnicate" capitalized is it "setting='frobnicate'" in quotes is it "setting=3" (where 3 is defined as Frobnicate somewhere else), or is it "setting: { value='Frobnicate'; }" or some other format. Even better when there isn't a message about an invalid setting, so guessing wrong just doesn't work with no indication as to why. A simple example could clear up so much confusion from trying to describe things in words, badly, but is sometimes mission impossible.