• DJKJuicy@sh.itjust.works
    0·
    3 days ago

    A “tech support guy” frustrated that users don’t know how to reboot their device (which is just a band-aid for poorly written software) for laughs?

  • shads@leminal.space
    0·
    3 days ago

    Before I went to a laptop with somewhat shakey suspend power consumption my desktop PC was going on 18 months uptime. The reason it was only 18 months was that we had a power outage. Unfortunately Debian became a bit boring so now I use Arch BTW. So many of the problems I deal with are caused by the insistence we use Windows “because it just works”. Worst part is 95% of my workflow is browser based. Its only bloody stinking Outlook that means I couldn’t use Linux to do everything.

  • mycodesucks@lemmy.world
    0·
    3 days ago

    Seriously though… it’s 2026. It’s fair to demand operating systems and software that are capable of cleaning up after their damned selves.

    • NaibofTabr@infosec.pubEnglish
      0·
      3 days ago

      Sorry, best I can do is 1 million more lines of LLM-generated sloppy spaghetti code that will be reviewed by no one, but implemented immediately to meet management’s target metrics for AI use.

  • TabbsTheBat (they/them)@pawb.socialEnglish
    0·
    3 days ago

    2 days ago, I went on my PC only to notice the audio was really crackly, after trying to move the headphone cable to see if I had broken it, and also disconnecting and reconnecting the headphones, both of which did nothing, I rebooted my PC which instantly fixed the problem :3 10/10 would turn off and on my PC again

  • wopalopa@lemmy.world
    0·
    3 days ago

    how hard is it to make autonomous reboot when needed? feels like that will solve a lot of headache

  • Destide@feddit.ukEnglish
    0·
    3 days ago

    Or learn the basics of the tool you use every day for work. Scary amount of office workers are like carpenters who don’t know what a hammer and chisel is.

    • wheezy@lemmy.mlEnglish
      0·
      3 days ago

      I like analogies so I’ll ad my own. Its like a leatherworker not knowing anything about how a hide is tanned. Or a tailor not knowing how fabric is woven.

      It’s really really important to the trade to understand the process in which their base materials are created. They don’t need to know the exact skills of creating those materials to the degree of someone at a Tannery or a Mill. But it’s important to the work of both of those trades to understand the basic process. And really I don’t think a leatherworker or tailor could be considered to hold either of those titles if they didn’t understand the basics.

      We don’t have that with modern tech. The materials and tools that modern workers use appear as complete black boxes to them. Like magical black boxes. And it’s honestly, a fundamental incompatibility with the incentive structures of existing economic systems that were forced upon a technology that should have made them obsolete in the 90s. But I digress.

    • The_Hideous_Orgalorg@sh.itjust.works
      0·
      3 days ago

      Not just office workers. Working in production factories has shown me that most people can’t, or won’t, think beyond “I pressed the button and it didn’t do the thing”.

      • NaibofTabr@infosec.pubEnglish
        0·
        3 days ago

        OK, but… if a device presents a UI of some kind, with a control that is presented to the user to perform some action, and the device fails to perform that action when the control is operated, then the problem is NOT with the user. There is either a system failure, or a design failure.

        Bluntly, if the situation is “I pressed the button and it didn’t do the thing”, that is the correct time to involve tech support. It should do the thing when the button is pressed, that’s what the button is for.

        • The_Hideous_Orgalorg@sh.itjust.works
          0·
          3 days ago

          Sure, but when you are repeatedly called to go over there and move their stuff out of the light curtain or other similar easy to notice issues, it gets annoying.