Then you pick up the manual:
To use, start using. If you get an error, try again
Reconfabulate the tridepodictaphone by nabulizing the fromgulan with kreevus. If stufingus brawes, then hyfangle the natriuminutaur.
Basic 17th year psycoders can do this.
The funniest thing to me is that any good manual would just say “DO NOT USE SOCKS AND FLIP FLOPS SIMULTANEOUSLY”
what if i want to embarrass my nieces and nephews
Finger-pulls and 'remember when…'s
What about tabi socks and setta?
I’m not sure there is a correct way to do this
That looks like an XY problem.
Finally, thanks I’ve been trying to remember the name of this for ages
Timtowtdi, doesn’t say there’s necessarily a correct one.
The documentation is usually dog shit.
The corporate culture does not allow appropriate time for the documentation as it is considered something that cost money without a quantifiable gain.
It permeates in the FOSS space as well since writing good documentation is a skill and it is not fostered in corporations. So devs start great projects with terrible documentation.
Does anyone know of any good resources on writing good documentation? It’s a thing I’m weirdly passionate about and absolutely want to get better at for my own sanity and for others as well if I can contribute.
But it seems like it’s a very under discussed subject…
Veronica Explains has a really good video talking about how much of a dead skill it is now from the standards it used to be.
WTF is going on in panel 2? Did they cut a hole in the sock?
deleted by creator
Step 1: cut a hole in the sock
Step 2: put your sandal in that sock
Joke’s on you, the docs don’t exist or are so outdated that they don’t even compile
Looking at you Microsoft.
that does look less painful than reading documentation
then documentation instructs it must be used for spanking
Man page me daddy.
Hold on… Is it
flipflop -throw -f=10 -t=bor is itflipflop -throw 10 -f -b? The docs show both work for setting the force to 10 and target to buttocks
That’s vibe coding.
Then you look back at your notes a couple years later and you’re like “I still don’t understand wtf I did it that way”.
It works, DON’T TOUCH IT.
It amazes me to see people do everything except 1) rtfm or 2) contact the support line that’s already paid for.
Edit: apparently my coworkers are in this thread.
As if the goddamn support knew their asses from their asserts.
The manual: poorly written; indecipherable
Support: reads the manual to you
“as viewed by the original dev who knows it inside and out”
I enjoy it more to figure out on my own. Kinda like disassembling stuff to see how it works and then put it back together. Reading the manual is like copying answers
Then the doc is so complicated that you spend hours reading stuff just to understand if the page is actually related or not. Then at some point you get bored try something randomly and it works.
The manual is probably outdated either way
Beat me to it.
What’s the meme for when the documentation is two years out of date?
Or when the documentation IS up to date… but the last 4 versions of the docs are still online and look exactly like the new version with no obvious sign of which version they are? (Looking at you, Microsoft)
I mean, thats how i learned to use a computer, was moms so the manual was gone by the time i used it anyway.
