• Postimo@lemmy.zip
    link
    fedilink
    arrow-up
    2
    ·
    edit-2
    2 minutes ago

    The idea that manuals in linux are a good way to learn and understand new software is peak linux neckbeard bs, and I will die on this hill. I congratulate OP on the exact type of autism that lets them feel this is an effective and useful method for learning new software, but if there is desire to have a greater adoption of linux maybe its bad to be snarky at folks for not instantly understand the terminal based documentation conventions of some dudes in the 70s. Maybe an alphabetical* list of all possible options is okay for referencing or searching, but is objectively insane way to learn or understand a problem.

  • BradleyUffner@lemmy.world
    link
    fedilink
    English
    arrow-up
    41
    arrow-down
    2
    ·
    edit-2
    2 hours ago

    For appliances at least, 95% of “the manual” today is useless CYA safety disclosures in 17 different languages. Manuals today rarely contain useful information.

    • onslaught545@lemmy.zip
      link
      fedilink
      arrow-up
      14
      ·
      1 hour ago

      The actual manual is usually hidden somewhere on it for repair techs to find. For my oven it was taped on the back.

    • evasive_chimpanzee@lemmy.world
      link
      fedilink
      arrow-up
      20
      ·
      2 hours ago

      Until you do like step one of taking an appliance apart, and realize that the real manual is marked “for technician use only”, and it’s hidden inside of the appliance.

      My washer and dryer both have good manuals complete with circuit diagrams under the top once i take a few screws out. My chest freezer has one taped up under the hatch where the compresser sits. My refrigerator has one hidden in the door hinge.

      • jj4211@lemmy.world
        link
        fedilink
        arrow-up
        4
        ·
        48 minutes ago

        Yeah, my parents were about to throw out an oven that would keep shutting off. I pull it away from the wall and boom, wiring diagram. Take out the ohm meter, figure out that the resistance across the temperature probe went to near zero when steam intruded through a gap in the crimp. 5 dollar part and it was good to go for years to come (the new part was crimped in a simpler, more robust way).

      • Mike D.@sh.itjust.works
        link
        fedilink
        arrow-up
        1
        ·
        53 minutes ago

        Dishwasher had the service manual taped to the kick plate. It gave me codes to troubleshoot, finding the heating element died.

      • Montagge@lemmy.zip
        link
        fedilink
        arrow-up
        2
        ·
        1 hour ago

        Yup, just got done wiring up an old washer to turn it into a feather plucker using the technician only manual!

    • rumba@lemmy.zip
      link
      fedilink
      English
      arrow-up
      4
      ·
      60 minutes ago

      Appliance repair in the 20’s? WTFY (Watch the fucking Youtube)

      query:samsung Ice maker stoped working

      Hi, I’m jimmy from shadyApplianceParts.com Did your samsung ice box stop making ice? That’s a common problem. What you need to…

    • NeatNit@discuss.tchncs.de
      link
      fedilink
      arrow-up
      3
      ·
      1 hour ago

      Honestly I have to disagree. All my recently purchased appliances: microwave, washing machine, dishwasher and induction cooktop, had detailed instruction manuals that were genuinely useful, especially where the finer details aren’t obvious from the device itself.

      Heck, even my wireless earbuds had a little bit of useful info, like how to force them into pairing mode.

      Of course, all those manuals contained those nonsense safety warnings too (and I read every word of course! :P) but that’s neither here nor there.

    • pHr34kY@lemmy.world
      link
      fedilink
      arrow-up
      2
      ·
      1 hour ago

      The troubleshooting section of the manual is almost always useless because it only ever covers user error.

      My washer threw a drainage error and the manual suggested I blocked the outlet or had done something daft. I looked up the error code online and 90% of the time it was a failed water pump.

      I had to replace the water pump. It was an easy job that required less documentation than a lego set for a 5 year old. You just had to know which screws to loosen to get to the pump. Was it documented? Of course not.

  • buddascrayon@lemmy.world
    link
    fedilink
    arrow-up
    8
    ·
    1 hour ago

    Meanwhile I’m sitting here with my ADHD brain that is unable to read the first two sentences of a manual without losing focus and thinking about 15 other things and marveling at those can actually get through something like that and have it stick in their brain longer than 5 minutes.

    • Zink@programming.dev
      link
      fedilink
      arrow-up
      2
      ·
      1 hour ago

      The trick with my ADHD brain is to refer to documentation when I’m hyperfocused on how the thing works for some reason. It doesn’t have to be because it’s broken, but it could be, lol.

  • zxqwas@lemmy.world
    link
    fedilink
    arrow-up
    8
    ·
    2 hours ago

    I’ll read the manual after it stops working. There are 10 pages of “warning: don’t microwave your cat” and 10 pages of what obvious buttons do and if I’m lucky 3 pages of fault codes that in the worst case scenario I’ll see one of them the next 10 years.

    Sometimes customers pay me to troubleshoot what other vendors sold them, I find the manual for their model number and basically flick through it until I find something.

  • Ŝan@piefed.zip
    link
    fedilink
    English
    arrow-up
    5
    arrow-down
    1
    ·
    2 hours ago

    Oh, so you’re þe guy I need to ask when I have any small problem and I’m too lazy to… RTFM.

  • TempermentalAnomaly@lemmy.world
    link
    fedilink
    arrow-up
    60
    arrow-down
    3
    ·
    4 hours ago

    RTFM is an obnoxious retort for people, arguably in community, not to engage with a member of the community. I don’t mind reading the manual, but perhaps you can point me to where in the manual I could get further insight.

    Reading a manual is also a skill. Being able to compartmentalize manual info into buckets of “obvious and I don’t need to read on”, “could be helpful”, “interesting, but it gets there I ain’t touching it” takes either training or just getting lucky after a certain number of reps.

    • buttnugget@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      8 minutes ago

      This is the only comment I’ve seen in here that I’ve seen address this. The whole concept of RTFM is reactionary and ridiculous. That kind of thinking and behavior kept me at arm’s length from the Linux/tech community for many years. Still kinda does.

    • UnderpantsWeevil@lemmy.world
      link
      fedilink
      English
      arrow-up
      5
      arrow-down
      1
      ·
      2 hours ago

      RTFM is an obnoxious retort for people, arguably in community, not to engage with a member of the community.

      I think there’s a low level of “How do I figure this out?” [generic] in which its good advice to ask “Does it say anything about this in the manual?” before you try and tear into a system as a third party giving advice.

      I also think “I read the manual on my refrigerator” is some “I dare you to prove me wrong” horseshit. On the one hand, people don’t do this for a reason. Refrigerators simply aren’t that complicated to use. And the manual is rarely a smooth read, even for professionals. So its good advice, but not practical advice, better than half the time.

      Reading a manual is also a skill. Being able to compartmentalize manual info into buckets of “obvious and I don’t need to read on”, “could be helpful”, “interesting, but it gets there I ain’t touching it” takes either training or just getting lucky after a certain number of reps.

      Also, just a matter of free time and mental calories to burn. And hey, maybe if you’re a hobbyist who is hip deep in your Linux kernel because you eat this shit up, its the place you should have started. But also, Jesus Christ, maybe I just want a Mint instance to run a Jellyfin server. I’m not trying to get my master’s degree in this shit.

    • humanspiral@lemmy.ca
      link
      fedilink
      arrow-up
      7
      arrow-down
      1
      ·
      4 hours ago

      public transit, ftw… unless “I wish I died pecefully like my grandfather… the driver who was RTFMing, instead of his screaming passengers”

      • FauxLiving@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        2 hours ago

        Last time I could buy a game with an instruction manual I was lucky that I could ride in a car without a car seat.

  • yermaw@sh.itjust.works
    link
    fedilink
    arrow-up
    20
    arrow-down
    2
    ·
    4 hours ago

    I don’t bother with manuals any more. I never manage to retain much information unless I need it right now. Way easier to just fumble along and find what I need when I need it and cobble together a half-baked “understanding”.

    Should go get some ADHD meds one day.

  • NotASharkInAManSuit@lemmy.world
    link
    fedilink
    arrow-up
    25
    ·
    4 hours ago

    I work in maintenance, people act like I’m doing magic, but 90% of the time all I’ve done is read the fucking manual, the other 10% is just basic awareness.

  • ExLisper@lemmy.curiana.net
    link
    fedilink
    arrow-up
    7
    ·
    3 hours ago

    Yeah, this sure resonates with me. When I started with Linux to set up anything you had to RTFM. I remember constantly reading some “Linux printing How-To” or “Linux Wi-Fi How-To”. It definitely stayed with me. If I buy something and it has a manual I’m reading it. Just in case.

  • reboot6675@sopuli.xyz
    link
    fedilink
    arrow-up
    41
    ·
    5 hours ago

    I once read the first 3 chapters of the Git book and my coworkers think I’m some kind of Git wizard

    • zalgotext@sh.itjust.works
      link
      fedilink
      arrow-up
      20
      ·
      5 hours ago

      One of the first things I did at my first full time job (while my very under prepared boss was looking for “junior-dev-friendly” tasks for me to work) was go to git-scm.com and just read through all the man pages I could. I spent a few days doing that, then my boss asked me to create a PowerPoint and present what I learned to the team. It was instantly apparent that I was the only one who knew anything beyond git commit -a on the team at that point, and I was promptly appointed the “title” of “source control SME”. I’ve been heading up version control best practices for every team I’ve been on since (which is scary because the git cli has changed quite a bit since I read all those man pages but I haven’t had a chance to go back and refresh my knowledge).

  • cm0002@piefed.world
    link
    fedilink
    English
    arrow-up
    17
    ·
    5 hours ago

    My folks bought a new EV recently and my dad was unable to figure anything out for days. I hopped in and was doing everything he wanted in minutes.

    “How the hell did you do all that‽”

    “I RTFM Dad”

    • croizat@lemmy.ml
      link
      fedilink
      arrow-up
      4
      ·
      1 hour ago

      And because people don’t read error messages, many applications/sites/etc don’t even put them, or if they do they either don’t have any public facing documentation to actually figure out what that code means, or they do and it might as well be nothing

    • hansolo@lemmy.today
      link
      fedilink
      arrow-up
      10
      ·
      3 hours ago

      They don’t.

      Undoing self-owns like ignoring available information is the basis for 40% of the economy.

    • rtxn@lemmy.worldM
      link
      fedilink
      arrow-up
      86
      ·
      7 hours ago

      Most people were conditioned by more “user-friendly” systems to ignore the content of error messages because only an expert can make sense of “Error: 0x8000000F Unknown Error”. So they don’t even try, and that’s how they put themselves in a Yes, do as I say! situation.

    • alecsargent@lemmy.zip
      link
      fedilink
      arrow-up
      22
      ·
      6 hours ago

      People who don’t read error messages or do not take the time to see what is going on and just come to the technician/mechanic/doctor saying “it doesn’t work” or some half-assed hypothesis piss me off so bad.

      I know that at some point we all do a little of this in our lifes, but some people don’t seem to be able to read one goddamn paragraph ever.

      • rtxn@lemmy.worldM
        link
        fedilink
        arrow-up
        5
        ·
        2 hours ago

        At this point, if a student brings in a laptop, explains what doesn’t work, and leaves me to diagnose and fix it, I consider it a good report because it means that the student didn’t get any overconfident ideas. If a student also explains what they were doing when a thing failed, I’m giving them preferential treatment.

        Then there are comp-sci students who attempted something. I had one who disassembled their laptop and tore a ribbon cable. I had one who plugged in a random mis-matched RAM stick that turned out to be busted and wondered why Windows kept crashing. I had one who completely fucked up the registry. I had one who wanted to install Ubuntu for dual booting and accidentally wiped the entire SSD.

        I would rather spend an hour babysitting their computers than an entire afternoon un-fucking something they thought they could handle. If it were up to me, I would restrict the crap out of their user accounts, but the faculty leaders insist, against empirical evidence, that they’re smart enough.

        • alecsargent@lemmy.zip
          link
          fedilink
          arrow-up
          1
          ·
          51 minutes ago

          Are these laptops provided by the faculty?

          In any case I do not mind so much the “I should try to fix this on my own first”. If it’s your own device and accept the risks/consequences. But if it is a work/university provided laptop then it makes no sense to attempt to fix it on one’s own.

          I can feel your pain trying to fix/repair something you have to figure out what kind of stupid stuff was done to the device.

      • Elvith Ma'for@feddit.org
        link
        fedilink
        arrow-up
        9
        ·
        4 hours ago

        but some people don’t seem to be able to read one goddamn paragraph ever.

        I had a problem with my car. It felt strange while driving. Made some unusual noise. Then a bit later the motor warning light came on.

        I went to the garage, told them about the warning light and what I noticed the time before, what I suspected and such. A short while after the mechanic came to me and asked for a few details, as my description “wasn’t helpful” and the repair would be much faster with more details that told them where to look etc. Turns out the guy who checked in my car only noted “a warning light is on” and nothing else of my ramblings.

        So sometimes it’s also paying attention to what might be important and relaying information.

      • faythofdragons@slrpnk.net
        link
        fedilink
        English
        arrow-up
        11
        ·
        edit-2
        4 hours ago

        To be fair, techs don’t usually talk to the people who can read, so they’re only ever going to see idiots. There are competent people in the world, they’ll just never need your help, so you don’t see them.

        Last time I called tech support, it was for a Dell, and I interrupted their speech to tell them I already looked up the diagnostic. They asked which numbers were lit on the error panel to confirm I had the right diagnostic, and passed me directly to who I needed to talk to. I only called tech support because the cpu socket died and I was putting in a warranty claim, otherwise they would have never even heard from me because I could just install a new motherboard myself.

        edit: speeling