
Seriously though… it’s 2026. It’s fair to demand operating systems and software that are capable of cleaning up after their damned selves.
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.
Linux sure when to shit didn’t it.
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?

It is 2026
Go fuck yourself, thief.
Fuck reddit.
And actually.
Random YouTube channel. But no idea how to give a show that old a credible link.
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.
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”.
To be fair, factory work doesn’t always reward people who start pushing new and interesting buttons. You got an error with the turbo encabulator and then decided to bypass it?
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.
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.
Yes. And the last two comments actually touch on a fundamental problem with modern modes of production. It’s why you’re both correct. More specifically, the relationship of laborers to the actual outcome of their labor.
Yes, it’s a lack basic problem solving skills. Or really, any interest in solving the problem. But, humans are fundamentally animals. And like any other animal, we look to conserve energy if we can obtain the same outcome.
The “issue” is seen as an opportunity for a break. The workers are so alienated from their labor that a minor problem has no incentive to be solved or thought about in order to continue the labor. It’s the “not my problem” thinking that wage labor relationships create.
The worker is not getting paid less or more when the widget maker breaks at the widget factory. The widget maker broke. They don’t get paid extra to fix the minor problem with the widget maker. They actually now have a perfectly acceptable excuse to reduce their labor output and still receive the same wage. Which is the goal and relationship with any wage labor job. From the software engineer to the janitor. To get the most amount of pay for the least amount of work.
“Laziness” is what people call it. But, it’s changed since the days of hunter gathering. The relationship of ones labor is not connected to a social group. They won’t be given less berries or a less favorable cut of meat for being lazy. They get a wage. Their relationship that builds incentives is not with what is being produced, who is consuming that production, or even the workers they produce it alongside. The relationship at the end of the day; is with a wage.
“Laziness” in modern work structures is actually a worker being smart and optimizing for individual gain based on the environment they are forced to live within. As long as they can maintain their wage and expell less of their energy in mental or physical labor; they are doing what is best for them.
And they don’t even need to understand any of this. It comes naturally. It’s why so many modern day companies spend so much time trying to reinforce the idea of “we’re a family”. It’s why we all think “why the fuck are we doing this “team outing” that probably costs more than I make in a month?”
It’s literally all there to try to get your monkey brain to think the relationship at the company is “with the people” and not with your wage.
It’s with your wage. Take a break when the widget makers breaks. Take your time if your job is to fix the widget maker. Take as much time as you can while still remaining hired.
Do the least amount of work for the most amount of pay you can get away with. Oh, and unionize. You’ll see the widget maker will break down less often and get simple fixes as soon as their is solidarity among workers and not the illusion of competition. Though, unfortunately many unions are corporate captured. So you may already be working under that.
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.
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
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.
how hard is it to make autonomous reboot when needed? feels like that will solve a lot of headache
“Oh no! My unsaved files!”
Easy, we’ll just power cycle the entire building. All current problems will go away.
Jeder Boot
tut gut!
Every boot
does good








