"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.
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 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.
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.
I always loved this one from my fridge:
What the hell is that supposed to mean?
It means if the fridge makes those sounds there is nothing to worry about.
And it doesn't have to be printed out in different languages.
When you call costumer service, instead of going "it's making this sound SRRR! SRRR!" you can say it's making the fly noise
"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.
I wish this was more of a thing. Right to repair!
This is one of my favorites: https://scp-wiki.wikidot.com/scp-2521
I love that. So he only likes pictures? If you write text, he will still take you?
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
RIP SkaveRat
Hasn't gotten me yet. I should be fi
Oh, hello Fi!
RIP slaveRat's computer/phone
Ah so the guy in Scenario A actually writes a piece of text which the SCP consumes. If he drew an image, nothing would happen?
Yup
The Wii safety documentation
and here I was, wanting to go skydiving with a Wii...
I was hoping someone would post this one it’s a classic
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
I like the old amd ones.
I think datasheets for components are often pretty great. At least the old ones with good application information and all that.
Then again, for a modern MCU or something there's several books worth of information, so it won't be on one document any more.
Automotive SPICE ® v4
Process Reference Model
Process Assessment Model
https://vda-qmc.de/wp-content/uploads/2023/12/Automotive-SPICE-PAM-v40.pdf
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.
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.
I loved when games came with manuals. FI Sid Meiers Pirates
Is this loss?
Lmao, didn't notice that but I can actually see it
Ghost ride ya whip, a flowchart:
🌈 Now we know! 💯
The Voron 3D Printer assembly manual. It's like IKEA and OSI had a baby.
https://raw.githubusercontent.com/VoronDesign/Voron-0/Voron0.2r1/Manuals/VORON_V0.2r1_Assembly_Manual.pdf
I'm going to do a write-up on this in the future. It really is a wonderful experience.
My Voron made me want to pull out my hair going through the instruction manual. Absolutely hated building it.
Aviation procedures manuals.
You more remember documentation which sucks than a good examples.
Sometimes is better to just read a source code.