Everyone loves reading documentation, what are some of your favourites?
-
[email protected]replied to [email protected] last edited by
"Do not dangle the mouse by the cord or throw at co-workers."
"All parts of the computer should fit together easily and without force. By all means, do not use a hammer!"
But seriously, some old UNIX workstation and server manuals come to mind as there's no mention of Microsoft anywhere. Just a good description of how the computer is actually supposed to be used.
Also home computer manuals and some hifi and lab equipment manuals which came with full schematics and measurement and calibration procedures. They essentially gave all users the maintenance manual and not just the dumb user one.
-
[email protected]replied to [email protected] last edited by
Automotive SPICE v4
Process Reference Model
Process Assessment Modelhttps://vda-qmc.de/wp-content/uploads/2023/12/Automotive-SPICE-PAM-v40.pdf
-
[email protected]replied to [email protected] last edited by
Also home computer manuals and some hifi and lab equipment manuals which came with full schematics and measurement and calibration procedures. They essentially gave all users the maintenance manual and not just the dumb user one.
I wish this was more of a thing. Right to repair!
-
[email protected]replied to [email protected] last edited by
Aviation procedures manuals.
You more remember documentation which sucks than a good examples.
Sometimes is better to just read a source code. -
[email protected]replied to [email protected] last edited by
and here I was, wanting to go skydiving with a Wii...
-
[email protected]replied to [email protected] last edited by
Like the picture in the post, furniture assembly. I enjoy assembling simple furniture (couches, chairs, storage, etc.) and trying to figure out the documentation, especially if it's made in china with inaccurate instructions, missing or unlisted parts, and the entire thing not in english.
-
[email protected]replied to [email protected] last edited by
I like writing documentation for processes at work. I always aim it at the "I'm familiar with the tools but haven't done this before" person. I always include examples of the actual commands because it is one thing to describe a command but when you see it it makes FAR more sense.
-
[email protected]replied to [email protected] last edited by
I was hoping someone would post this one it’s a classic
-
[email protected]replied to [email protected] last edited by
Is this loss?
-
[email protected]replied to [email protected] last edited by
Any of the classic RFCs. I really like the way RFCs are written.
Also, they're extremely verbose, but the Intel x86 processor manuals are fascinating
-
[email protected]replied to [email protected] last edited by
I loved when games came with manuals. FI Sid Meiers Pirates
-
[email protected]replied to [email protected] last edited by
Lmao, didn't notice but I can actually see it
-
[email protected]replied to [email protected] last edited by
I always loved this one from my fridge:
-
[email protected]replied to [email protected] last edited by
What the hell is that supposed to mean?
-
[email protected]replied to [email protected] last edited by
It means if the fridge makes those sounds there is nothing to worry about.
-
[email protected]replied to [email protected] last edited by
When you call costumer service, instead of going "it's making this sound bzzz bzzz" you can say it's making the fly noise
-
[email protected]replied to [email protected] last edited by
I like the old amd ones.
-
[email protected]replied to [email protected] last edited by
This is one of my favorites: https://scp-wiki.wikidot.com/scp-2521
-
[email protected]replied to [email protected] last edited by
I love that. So he only likes pictures? If you write text, he will still take you?
-
[email protected]replied to [email protected] last edited by
Any written or spoken information about 2521 will cause it to grab it. Be it whatever is used to write it down, or whoever said it.
So it can only be described in images, photos or pictograms