35

It fucking infuriates me when the docs mention to create a certain config file "xyz.json" but completely leave it to your imagination where the hell this fucking file should be placed!
Come on, I'm not getting paid for detective work, fucking imbeciles.

Comments
  • 7
    I especially hate when you get the documentation that shows you where it should be placed but its multiple places and then they don't tell you how to point the program to it

    "The xyz.config file should be placed at either

    /usr/share
    /etc/programX
    /home/user/.config
    (Add a few more here but none will eventually apply when the program is run because fuck you)
  • 6
    Unfortunately, 90% of what we do is detective work. Ever get a requirement that’s more than 10% accurate?
  • 3
    Now that I think of it, maybe my obsession with being programmary detective is weird. Whatever you throw at me, except few cases, is gonna be scrutinized and postponed many times 😅 ... 😑
  • 2
    I'm glad someone ranted about this. We need more rants on shitty docs.

    My personal pet peeve is when they tell you about a massive object their function accepts as an argument but never bother to provide any details about any of the keys or what they do.

    Some just slap an interface name on it like it makes any difference whatsoever, like

    ```ts
    eatMyAss(config: IEatMyAssConfig)

    Arguments:

    config {IEatMyAssConfig} - Config to tell function what to do
    ```
Add Comment