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.
the variables were not defined properly and were named esoterically
I wonder why it was so hard and took so long to write
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
The help command is one of the first things I work on in any project. Even if I’m never gonna share it, my future self will appreciate it.
$ mysterytool $WHAT DID YOU DO?!
Knowing my luck, It probably deleted a rarely used system library and will lead to unpredictable crashes.
I just want to say this is a masterful use of the format.
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
Soy devs have invaded Linux.
But also
mysterytool --help
mysterytool: unrecognized option: '-'ok then…
mysterytool -h
mysterytool: unrecognized option: 'h'mysterytool --help ‘--help’ unrecognized option, -h for helpI will burn this motherfucker to the ground
Or the opposite:
mysterytool -h -h unrecognized option, --help for helpBoth need to burn.
Embedded *nix be like
Cries in busybox
That, at least, had an excuse to be terse. If you use busybox, you probably have a real machine with the ability to browse the online documentation, anyway.
If the program’s author hasn’t bothered to properly document its function, then it has no business being on my machine.
“tHe PrOgRaM iS sElF dOcUmEnTiNg”
I’d try
mysterytool -H-H for Hard drive to delete, -h is help
-his halt.
