• Mac
      link
      fedilink
      English
      22 hours ago

      My Voron made me want to pull out my hair going through the instruction manual. Absolutely hated building it.

        • SeekPie
          link
          fedilink
          116 hours ago

          And it doesn’t have to be printed out in different languages.

      • @[email protected]
        link
        fedilink
        16
        edit-2
        22 hours ago

        When you call costumer service, instead of going “it’s making this sound SRRR! SRRR!” you can say it’s making the fly noise

  • @[email protected]
    link
    fedilink
    291 day ago

    “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.

    • @Crazyslinkz
      link
      171 day ago

      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!

  • @zzx
    link
    924 hours ago

    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]
        link
        fedilink
        17 hours ago

        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.

  • @[email protected]
    link
    fedilink
    71 day ago

    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.

  • edric
    link
    fedilink
    English
    61 day ago

    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.

  • lnxtx (xe/xem/xyr)
    link
    fedilink
    English
    41 day ago

    Aviation procedures manuals.

    You more remember documentation which sucks than a good examples.
    Sometimes is better to just read a source code.