Reminds me of a comment I once came across in a work application's code: "This function took forever to write correctly. It was hard work. I didn't document it. Figure it out."
Of course the variables were not defined properly and were named esoterically.
$ mysterytool
$
WHAT DID YOU DO?!
I don't understand how devs can be too lazy to write documentation but somehow they'd rather explain the same shit in discord over and over and over and over and over and over
I was recently trying trying to get help on a clipboard program someone had recommended me, clipq. What I found instead was a GitHub discussion where the dev said "I'm not sure what you mean by 'man' pages" in response to someone asking for them. I think I need to find an alternative
Haha, I made this :) Hereβs the blog post I created it for, if you want a bit of context:
But also
mysterytool --help
mysterytool: unrecognized option: '-'
ok then...
mysterytool -h
mysterytool: unrecognized option: 'h'
If the program's author hasn't bothered to properly document its function, then it has no business being on my machine.
Embedded *nix be like
Programmers generally detest to do documentation, so when the user help "UI" is all down to a programmer to define this is often what you get, especially if it's a small tool.
It's like people don't like surprises anymore.
Exclusively installed through some dodgy PPA you got from a blog.
strings `which mysterytool` | less
Give up your darn secrets before I start fumbling around with strace and get even more frustrated!
I just want to say this is a masterful use of the format.
I'd try mysterytool -H
python -V
What the actual fuck
top 50 comments