16 ms·
We are wasting up to 20% of our time on computer problems, says study
- kunalgupta 3y agoI track this! < 5% but still a lot
- Solvency 3y agoI wasted 80% of my time on this article page dodging lazy loaded ads, dismissing cookie banners, and subscribe now overlay modals.
- HWR_14 3y agoThat can be automated. Install an ad blocker
- mindvirus 3y agoThose are rookie numbers. With a little Kubernetes, we can get them way up. So much of the incentive structure in software companies is to ship new features. Maintaining existing ones or fixing bugs is a career dead end for software engineers and managers. No wonder so much stuff is broken and slow. Call me cynical, but from a dollars point of view this seems to be what customers want.
- hifromLA 3y agoI do agree when we see broken outcomes (e.g. us healthcare, us public transit, etc) it’s good to go back to incentives to understand why things haven’t gotten better. When perf time comes around, everybody knows the deal. Shipping a new feature is a much easier sell than a bug fix and looking like a hero for fixing a bug instead of preventing one is easier anyways.
- IshKebab 3y agoI agree. I have to really fight people when I try to write robust software. "Why are you writing a proper parser when a hacky regex that I thought about for 2 seconds worked the one time I tested it? You're wasting time." They don't understand that I'm not wasting time, I'm just choosing to spend a little bit of time earlier, because I don't like spending a lot of time later when debugging why everything broke.
- datavirtue 3y agoSame here. I stopped suggesting robustness because no one cares.
- ilyt 3y agoI just include writing robust code in my estimates and don't tell anyone. Shoddy code only happens in "the production is on actual fire, not manager-imagined fire" fixes and not for long.
- sempron64 3y agoThe problem with a careful but non-methodical approach is that it requires the programmer to correctly determine the stability value of their design. We often overestimate the importance of architecture on stability, or worse, architect something that is harder to maintain than the naive solution. With buggy ship-it-now software you have a known bounded risk - bugs will occur in some cases but the software will ship and the bugs can be fixed because it’s simple. With prematurely architected software the risk is unbounded - the project may get bogged down indefinitely in its own complexity without shipping. The inverse extreme can also be a problem, of course A project that is maintained for a long time on the naive implementation will also become unmaintainable. However, this will be due to _known_ architecture problems encountered during maintenance. These problems can be addressed in a relatively bounded amount of time. They are also quantifiable and thus explainable to management.
- im_down_w_otp 3y agoThe specific case of building a proper parser doesn't take that much longer if you know what you're doing, and it also enables lots of wonderful quality of life features for end users through additional opportunities for automation and contextualization that can be surfaced. Though, given the constant incentive to never learn how to write a proper parser does mean that practically nobody knows how to do it, and so it will always look & feel like an unbounded science project, and thus rarely done. Infinitely recursive MVP'ing is a race to the bottom.
- sublinear 3y ago> So much of the incentive structure in software companies is to ship new features. Maintaining existing ones or fixing bugs is a career dead end Highly dependent on where you work and what you consider a "dead end". You can't possibly be talking about becoming unemployable in the industry nor even a pay cut. The situation for senior devs is the opposite, actually. Maintenance is the long tail of every project. If you're not doing that, you're not really working in software.
- javajosh 3y agoThere is something like a paradox of automation at play, too. Both business and programmers are aligned on not wanting drudgery, but this means that a) we undervalue first-order work, and b) our automation reach often exceeds our grasp (k8s being an excellent example). Perhaps my thinking is colored by my recent read of Patrick O'Brian's excellent "Master and Commander" series of historical novels, about early 18th century English sailing ships, but the lack of automation is part of the romance - just to get from "here" to "there" required enormous effort. And who knows? Maybe if we take that approach we can press people into the software service by force, just like in the good old days!
- ElectricalUnion 3y ago> about early 18th century English sailing ships, but the lack of automation is part of the romance The highly hierarchical and structured command structure of a ship means that autonomous and intelligent human beings each make autonomous and intelligent decisions on the best course of action in a way that doesn't require constant and immediate upper layer attention all the time. The more limited amount of human beings required to upkeep a ship those days are mainly because of manpower shortage and cost reasons, not because the removed humans were "worse" at doing such operations. Those automation flows are in my opinion the same thing, they're replacing things because of manpower shortages or high costs of the previous thing, not because they're better.
- javajosh 3y agoCorrection: late 18th and early 19th century sailing ships.
- wredue 3y agoDude on HN was describing the other day how they’re moving to use an AI to generate a list of cars with specific features in their inventory and how this was a great part of the AI future. But as we see frequently even on the most sophisticated AIs, they get shit wrong… a lot. So this company decided to replace an actually working, guaranteed to produce proper results filtering system with a guaranteed to not produce proper results an unknown amount of the time, and the feeling was that this was good business direction. People want buzzwords, not working software.
- nerdponx 3y agoPeople don't want buzzwords, people want promotions, bonuses, and recognition. It turns out that producing working software is not the optimal way to obtain those things at a lot of companies.
- A4ET8a8uTh0 3y agoAnd how do you get said promotions, bonuses and recognition? By introducing change. And what change is easiest? One that relies on established ground of buzzwords.
- WinLychee 3y agoNot just new features, but making everything way more complicated too!
- q845712 3y agoI'm not sure it's exactly "what customers want" so much as it is the sweet-spot or intersection of the two curves: "what customers want" with "how much cost and risk owners and managers are willing to put in up front"
- sixstringtheory 3y agoMy thoughts too. With VC-funded freemium models, I think it’s hard to make a clear case for who the paying customer is and what they want.
- ravenstine 3y agoAdd on top of that the perception that users need "wow" factor for everything. We can't ever have a full page refresh, even for something as simple as a blog or a storefront, despite most users being oblivious to when those take place. Everything's got to be flashy and overly designed. If it doesn't look like The Google designed it, then no one will use it!!! /s
- MattGaiser 3y ago> but from a dollars point of view this seems to be what customers want. What percentage of software (in dollars) is purchased by people who are not going to be the ones using it? I suspect the answer is the overwhelming majority. It is how software monstrosities like Concur can exist and be ubiquitous.
- npsimons 3y ago> Call me cynical, but from a dollars point of view this seems to be what customers want. I'm right there with you, except I don't give "customers" that much credit. Most people left to their own devices (ie, not brainwashed by marketing) will just stick with "good enough." But it's less fun (and less profitable) to fix and maintain old code, so companies induce "demand" by marketing. And if you're a company who decides to do the adult thing and not play that game, you'll be creamed by the ones that do.
- coderintherye 3y ago>Maintaining existing ones or fixing bugs is a career dead end for software engineers and managers Strong disagree. This may be the case at certain "tech" companies, but I grew my career into CTO through maintaining existing systems and fixing bugs (and through doing the things no one else wanted to do). Amongst my fellow members of the particular CTO club I'm in, I'd say about 1/4 to 1/3rd followed a similar path. There is a related way you can limit your career though, by becoming an expert on a non-critical system and limiting your focus solely to it. Many engineers take that path because it feels safe and offers job security, but it will limit upward mobility options.
- wouldbecouldbe 3y agoHaha yeah. Kubernetes on Azure for bonus points. Not only do you waste more time, you also pay more and are recommended to get an expensive certificate.
- jonhohle 3y agoMaybe that’s a good business idea: solely focus on bug fixes for clients so their “rockstars” can architect their way into more bugs that need fixing. Since the business’s employees I are only focused on bugs, and not features, they’re not leaving tech debt in their wake.
- febusravenga 3y agoit's my strategy since I become bored with tech. I don't have passion or urge to create new useless software. There are many young or naive or plainly stupid which do. But I still have skills and insight to cover their asses when they corner themselves and are too busy with next fad and there are bugs to be fixed in yesterday's crapware... and I'm only 40..
- Tade0 3y ago> Those are rookie numbers. With a little Kubernetes, we can get them way up. I used to be a frontend developer, but now my problems include `Error: mkdir /bitnami/postgresql/data: permission denied`. All I wanted was to have a Persistent Volume Claim on my Postgres container that is part of a new dev environment I'm setting up. The other one worked, and still works fine.
- mattpallissard 3y ago> Those are rookie numbers. I make a living dealing with computer problems.
- happymellon 3y agoFucking hell, I've just blown another day because I'm dealing with over engineered crap. We are on AWS, and a Postgres database that is primarily in one region, and read only in a second? That should be Aurora, and 15 lines of CloudFormation/CDK/whatever. But that's too easy and reliable, who would need an SRE and an architect then? Instead we have multiple RDS instances, and a regularly failing PG Logical installation which requires an engineer constantly checking in on it because it silently fails and you only find out when storage starts burning out fast. There is no feedback loop to let leadership know that they are spending hundreds of thousands over the odds for an unreliable system, and architects who seem to fail to admit someone made a misjudged call a couple of years ago. I don't know what the solution is, but currently it's just some shitty old boys club. Yes, they also picked Kubernetes but decided to install their own instance on AWS. Why the hell are we in a managed eco system and trying to build it in the worst way possible? Everything crashes on a regular basis.
- bobthepanda 3y agoAt least over half the issues sound like issues with computer hardware/OS (the computer froze/the wheel keeps spinning) Many people have tried to have an OS and pretty much all except MS, Apple and Google have failed at the consumer level.
- ilyt 3y agoJust today we had a call with devs that wanted to run k8s (managed by us) on client's stuff (when we generally got few VMs and cranky security guys any time we needed some traffic passed thru). To run app that's like 3 containers with services, a queue, and a database. Took a second to explain that overhead, added management, and sheer paperwork to run it on client's infrastructure is absolutely not worth saving them like... a day or two making a bit more complex deploy script.
- yodelshady 3y agoI've spent the last two days working with (not-Kubernetes) virtualisation software that has serious, workflow-breaking bugs from... uploading and removing regular files, of a format it expects. In some random-aaS frontend I could expect that, but this is systems stuff. :(.
- nick-of-time 3y ago> Call me cynical, but from a dollars point of view this seems to be what customers want. Since when have the wants of customers been the driving factor behind business decisions? There is a downstream effect, sure, as long as there is competition, but businesses are controlled by petty little weirdos with short attention spans like Elon Musk. Does this make me more or less cynical than you?
- bhaney 3y agoUp to?
- justinclift 3y ago[flagged]
- karmakaze 3y agoThe only bit of info/detail: > The problems most often experienced by the participants included: "the system was slow," "the system froze temporarily," "the system crashed," "it is difficult to find things." The participants had backgrounds such as student, accountant, consultant, but several of them actually worked in the IT industry.
- boblob-law 3y agoThis seems like a load of crap.
- globalreset 3y agoIsn't that expected and natural? As performance of a system is being optimized, the relative size of un-optimizable parts goes up. Sure, your banking app crashes sometimes and annoys you. How about you delete it and instead take a bus to a postal office to pay your bills this way - no annoying apps involved, it will just take 1h instead of 1m.
- deleted 3y ago[deleted]
- tivert 3y ago> Sure, your banking app crashes sometimes and annoys you. How about you delete it and instead take a bus to a postal office to pay your bills this way - no annoying apps involved, it will just take 1h instead of 1m. Huh? Have ever actually paid a bill without using a computer? It doesn't work like you describe at all (unless you live in a really rural area or you're deliberately trying to make it difficult for yourself). Here's how it works: 1. Get a bill in the mail. 2. Open it, and write a check for the amount. 3. Put the check in the envelope, stick a stamp on that, and then put it all in your home's mailbox. 4. The mailman comes and picks it up, and it goes where it needs to go. No buses, no trips to the post office required.
- crazygringo 3y agoIt depends on which country you're in. In some countries bills need to be paid at any bank or at the post office, you can't mail a check. The bill basically has a bar code that that the bank scans, and you pay in cash. (Or you can scan it at your bank's ATM and deduct it from your account).
- frakt0x90 3y agoI live in the suburbs of a large city in the US and I have to physically go to the post office whenever I mail something. My neighborhood has a weird matrix of mailboxes with no way to indicate to the postman that he needs to take something. So I have to drive to a post office every time I want to send mail. We even tried leaving a note in the box and that did not work. It doesn't take an hour but probably 20 minutes round trip.
- samsquire 3y agoFinally, a chance to say what I really think about computers! I feel that the majority of time working with computers is not actually computing numbers (addition, subtraction, multiplication) but LOGISTICS. Logging into systems, Moving data around in memory and between servers, into registers for a function call, to and from a REST API, installing packages, finding dependencies, chaining together library functions.
- pipo234 3y ago+1. So often we conceptualize in terms of tasks, phases, states, processes. And then ultimately you discover it is all about data flow, an rarely about the algorithm.
- laxd 3y ago> I feel that the majority of time working with computers is not actually computing numbers (addition, subtraction, multiplication) but LOGISTICS. I think this was figured out in the 50's, when IBM started making mainframes for businesses - made for data processing and management rather than crunching numbers which was the focus of machines made at universities. Also, in norwegian and I guess other european languages. We call them, directly translated, "data machines" rather than computers.
- yurishimo 3y agoIn Dutch the word is "computer" also, but English is the bastard child between Dutch and French while Dutch is already a bit of a bastard child from German. ¯\_(ツ)_/¯
- laxd 3y agoI was confident that at least the germans would back me here, after all they got words like taschenrechner. But according to my dictionary they call it computer. Danish seems like 30% english nowadays, so I can't count on them. At least swedes call it "dator" which I guess is in the right spirit.
- balaga01 3y agoAnd this is why I do not fear unemployment or AI. There will always be work for someone who can be asked to build over complicated software and debug it.
- jt2190 3y agoAd-free link: Department of Computer Science, University of Copenhagen “We are wasting up to 20 percent of our time on computer problems” https://di.ku.dk/english/news/2023/even-though-our-computers-are-now-better-than-15-years-ago-they-still-malfunction-between-11-and-20-percent-of-the-time-a-ne_/ https://di.ku.dk/english/news/2023/even-though-our-computers... Original study published here: “Frustration: Still a Common User Experience” https://dl.acm.org/doi/10.1145/3582432 https://dl.acm.org/doi/10.1145/3582432
- jnsaff2 3y agoThen again how much time do computers save? Washing machines and fridges freed up a ton of time for people. Maybe computers as well, then again maybe they just entertain. My personal anecdata, I was recently investigating some page load timeouts for my client and this lead me down a rabbit hole which in the end meant moving a WHERE clause from outer query to an inner one and sped up the query 100k times. Based on slow query log stats it eliminated 25h of human waiting per day.
- hospitalJail 3y agoI see this too. We now have dedicated programmers to maintain a program that was supposed to save time. Well that program(and a few others) made it so instead of having 120 (real) engineers, we have 7 engineers. The cost saving is real, it allows greater complexity, and the maintainer can add upgrades and work on other things as the program matures.
- robertlagrant 3y ago> Then again how much time do computers save? Unbelievable amounts, both in speed of processing and communication, and in lack of error.
- itsboring 3y agoSeems like AI is becoming pretty effective at undoing the “lack of error” part…
- robertlagrant 3y agoAI is barely involved in any digitisation of things yet.
- sempron64 3y agoI’d be very upset if my dishwasher broke every 5th time I used it. And in that scenario I’d much rather wash the dishes by hand. Probably the same for my clothes vs. the washer. If it takes 10 minutes to boot my computer, log into 10 SSOs with two factor, and install 57 updates, at what point do I start keeping graph paper and a desktop calculator to track my sales instead of using excel?
- smy20011 3y agoOnly 20%? I think the numbers are close to 80%.
- Cupprum 3y ago80%? How did you get that number? Van you elaborate a bit?
- nhumrich 3y ago20% of our time is wasted, but we are 2-3x more effective overall because of computers. Sounds like a reasonable tradeoff
- lolinder 3y agoLink to the author version of the paper (the link in the article is paywalled): http://mortenhertzum.dk/publ/TOCHI2023.pdf http://mortenhertzum.dk/publ/TOCHI2023.pdf
- jamil7 3y agoProbably true. However, I interact with a bunch of broken systems all around me, in the real world, all the time. I'd also wager that I waste far more than 20% of my time on some of them.
- datavirtue 3y agoDevelopment teams, that include users, know about the issues. In the face of deadlines and budgets the team keeps opting to let little niggles slip in because they aren't a big enough deal to justify schedule disruptions or using developer time. All these little quirks add up to a shit UX. The users filed the bug and the devs recorded the story, but management shot it down. Incentives.
- ElectricalUnion 3y ago> All these little quirks add up to a shit UX. Not only that, after a while those UX warts are now embedded as part of someone's workflow and can't be changed. as usual, elevant XKCD: https://xkcd.com/1172/ https://xkcd.com/1172/
- yurishimo 3y ago> All these little quirks add up to a shit UX. This is killing me about my current job. I want to fix so many things, but the culture here is don't rock the boat (nationwide, not just this company). Just today a colleague was reviewing a PR. I left a comment saying that I deleted a few template files that were no longer in use but I noticed them while working through the ticket. The PR had 6 different comments on it asking "Why was this deleted" for every single file that I deleted. I hope it's a language barrier thing with this one particular person, but I don't know. We have retrospectives and talk a lot about making time to refactor as a part of sprint tickets and doing better within the system we have and then this crap comes up. So now I need to go write another ticket, bypass all of the refinement rituals (which nobody likes when I do that) and add the ticket to the sprint, just to delete these few unused files that git says haven't been touched in 7 years? Wtf guys. The hard part of software is, always has been, and always will be, people, not code.
- hospitalJail 3y agoMy Nest Thermostat was an example where I lost time. Sure I didn't have to walk down the stairs to change the temperature a few times, but as the Thermostat started to bug out, I spent hours trying to fix it. I lost more time than I ever saved.
- tivert 3y ago> Sure I didn't have to walk down the stairs to change the temperature a few times, but as the Thermostat started to bug out, I spent hours trying to fix it. I lost more time than I ever saved. I've got an Ecobee, and I've never had a problem. The main reason was (unlike the Nest, at least at the time) it's fully functional in offline mode (schedules and everything). I've since learned that HVAC people typically dislike Nests, though I don't remember the reasons (and they are fine with Ecobees). I'm not sure exactly what your problem with your Nest was, but they just didn't seem very reliable to me when I looked at them. Too much silicon valley in them: not prioritizing robustness, weird features that sound cool but just lead to an inscrutable device with a mind of its own, an over-reliance on the internet, etc.
- hospitalJail 3y agoAfter much research, my conclusion is that my HVAC system didn't have one of the wires connected, Common, C. This was not a problem until some update that caused the rest of the wires to be insufficient to recharge completely. Over the next year or so, the battery was killed. Who knows though. It was fine for the first few years, aside from when my power company overrode my settings on hot days and my kid had a life threatening fever.
- tivert 3y ago> After much research, my conclusion is that my HVAC system didn't have one of the wires connected, Common, C. This was not a problem until some update that caused the rest of the wires to be insufficient to recharge completely. My Ecobee doesn't have a battery at all, so that's something I had to deal with immediately upon installation. Luckily, I had an unused wire going to my own thermostat that I could repurpose. I believe it also came with a kit that would allow it to use a nonstandard signaling protocol so it could get needed power even if I didn't have an extra wire. I'm kind of puzzled why a Nest would even have a battery. Just a kludge to allow unreliable installation in places that don't have the proper wiring? One of the things I hate about modern software/product engineering is the over-reliance on updates and the mindset that aggressively obsoleting "old" versions. It creates a huge amount of unreliability and wasted time. IMHO, updates break things as much as they fix them. > Who knows though. It was fine for the first few years, aside from when my power company overrode my settings on hot days and my kid had a life threatening fever. Could they do that through the Nest, or did they have a separate cutout on the AC? My home has a remote operated cutout, which I'd assumed wad inactive until I randomly read by bill very carefully and realized it was active even though I never signed up for it (apparently the previous homeowner had it active, and that carried forward to my account).
- hkt 3y agoAs a devops engineer, 100% of my time is wasted on computer problems. I increase my efficiency further by following instructions to the letter: this allows me to also waste multiple 10s of %s of other people's time too. The 10x programmer is real.
- PartiallyTyped 3y agoAs a mathematician turned software engineer, dev ops and build systems are the bane of my existence. Every time I need to do that work, I want to quit. The fact that I “can’t just X” but need to use some convoluted build system with details hidden somewhere as if it was arcane magic is beyond me.
- hkt 3y agoAlas, lots of devops feel like they're cleverer than they are. I certainly did when I was younger. The sign of seniority in a devops engineer is removing code, breaking down complexity, and being able to design simple, standalone services at a useful level of granularity. Sorry to hear you've not been around those people enough. For what it is worth, even senior devops end up building convoluted crap too, but often this is because the organisation demands it. People don't recognise the hidden costs of complexity, in build or operation. Cleverness is often complexity, and promoting those kinds of solutions means creating the environment for "10x" engineers. People come to rely upon them because investing too deeply in learning about other people's complex legacies is almosy never worth it.
- PartiallyTyped 3y agoAt AWS we are expected to do our own dev-ops, even if you are at a larger project with with some dev-ops engineer, you still need to do your own dev ops for many things. CDK with TypeScript is actually pretty nice to work with, I like the compiler errors, having some type system, and managing my infra via code. My issue is with other systems. In all honesty, our customers have better build tools than we do.
- kstrauser 3y agoThere’s no way I’m 80% efficient.
- PartiallyTyped 3y agoTechnically even a perfect engine can not be 100% efficient, so is all good!
- kstrauser 3y agoI'm putting that in my next performance review.
- tester756 3y ago20%? This industry is built on lack of effectiveness. We've built a few complex, production ready OSes, with bilion programming language and compilers, with a few web browsers, with X drivers for everything (graphics, network, sound). Basically everything a few times Just to display funny cats in web browser
- narag 3y agoBasically everything a few times That's a very good idea. Really. In tirannies there's only one thing of each. When that thing breaks, you're sorely out of luck. People associate diversity with justice. But diversity is in fact your plan B, or C...
- tester756 3y agoI'm not saying that this is bad, just not so efficient.
- febusravenga 3y agodiversity and redundancy are inefficient by their own nature
- narag 3y agoOn the contrary, it is much more efficient. One size doesn't fit all. The bad systems die when that's possible. When there is only one, a problem becomes a bottleneck.
- swayvil 3y agoThe machine promises to make our dreams come true and the computer is the best machine. I call it a worthy expense. /s
- 1970-01-01 3y agoWe can fix that with software
- dustedcodes 3y ago> We are wasting up to 20% of our time on computer problems, says study Cough, they mean Microsoft Teams, SharePoint, Azure AD, Internet Explorer Edge and Windows 10/11 problems because the rest works fine, no?
- deleted 3y ago[deleted]
- mikewarot 3y agoWhen I started as an IT manager at a small events firm in 1997, I had 40 hours of work every week, just keeping things alive. By the end in 2013, things just ran smoothly, and I waited for something to break. Windows got reliable between Windows 97 and Windows 7, servers got reliable, networks got reliable... everything stopped breaking. There's no way 20% of peoples time is wasted on borked computers, that's a whole day every work week.
- deathanatos 3y agoMy MBP is currently running at ~800 MHz; it will be until about October or November, when I feel the coming chill of winter upon my skin. macOS thermally throttles the chip down, even if the chip is not actually that hot: the CPU is only ~65℃. But the surface temp on the keyboard is 109℉. All I can guess is that even though there's plenty of thermal headroom at the chip, you'd roast the user's hands if you attempted to use it. The fans cannot move the heat away from the CPU and out the back sufficiently fast, and too much ends up bleeding out the keyboard. But now you have a 2.4GHz i9 limited to 800 MHz. During a meeting, it can't really do anything else, VC eats the available compute. This is pathetic. Perhaps IT is different where you are, but my IT is out to lunch. IT is "hand new hire a new MBP" and … that's it? Unless a literal hole ended up in it¹, they're not going to replace it, ever. Spolsky wrote that one of the "rules" for SWE firms was "Do you use the best tools money can buy?" — he wrote that that was table stakes, and if you're not doing it, you're nuts. He wrote that in 2000, nearly twenty-three years ago. But tech cos love the MBP; IT teams only want to support one model of machine, regardless of how much of a lie that is (there are multiple models of a MBP deployed over time in a company) or how ill-suited a MBP is for the task at hand. Absolutely I'm losing at least 20% if not more waiting multiple seconds for keyboard input to show up. Being unable to look things up during meetings, meaning mistakes get made, begetting more meetings. ¹Hmm. HMM. Then there's the keyboard. The display cable connection. It goes on and on…
- jeroenhd 3y agoMacbooks had absolutely atrocious performance once the CPU heated up, masked by turboing extremely quickly to make short bursts of performance feel responsive. This was made worse by Apple's absolutely terrible cooling design. Their user-hostile form-over-function designs are also typically Apple. They made great devices for quick demos, but terrible professional workstations. I actually suspect Apple sabotaged their own Intel-based products when M1 was on the horizon to make performance look better in comparison. Their attempt to basically passively cool an i3 that had a thermal output that clearly couldn't be cooled in such a way can only be described as either intentional or incompetence somewhere in the chain. With the new ARM chips, things have changed for Apple. Their cooling solution is still worse than the competition, but their excellent CPUs don't need nearly as much cooling. The GPU sucks, but that doesn't matter for most productive use by using hardware acceleration (in select applications, for select formats). You're not going to be doing CAD work on a Macbook Air anyway. The sad truth is that Apple's competitors are doing worse these days. AMD is doing relatively well, beating Apple in most benchmarks, but with lower performance per watt in the end. Intel is still trying to compensate for their inferior CPU designs by squeezing more power into their silicon, leading to impressive numbers for anyone hooking their computer up to the wall, but terrible battery life if you try to use that performance in a laptop. I expect AMD to eventually get competitive based on the direction their mobile CPUs and GPUs are taking, but they still lack the production capacity to make a dent in the laptop space. What I don't understand is why even people working in the office all day every day end up with laptops hooked up to docks and dongles. Even the excellent Macbooks get beaten hands down for cheap by normal desktop components that are available prebuilt with excellent warranty and on-site service for very similar prices. Just use a desktop! You don't have to pick between top-of-the-line laptops and bargain bin desktops!
- gumby 3y agoWe also los 4-9%% of meeting time with people trying to get their Zoom connection to work (camera, audio, can't connect etc). The impact on GDP must be pretty significant.
- djyaz1200 3y agoThank goodness I can enjoy these same frustrations when I sit down to watch to TV thanks to all the bugs with the various streaming services.
- smashface 3y agoSkimmed article mostly. Could things be better? Sure. But saying we're "wasting" all this time seems a little disingenuous. How much time do people spend maintaining tractor equipment to grow crops? Or really any tools of any trade? The equipment and tools we use let us be more productive overall with certain tradeoffs.
- JoeAltmaier 3y agoI like to say, I spend one month a year writing code and 11 months testing, debugging, packaging, documenting, shipping, supporting.
- shswkna 3y agoI believe that most people that make decisions that impact a large number of people the world over, simply have a too narrow experience of the world, and of other people’s situations. They know their own reality and think that this is how others experience life as well. This is the root cause of many problems in the world.
- figassis 3y agoI know this will get some downvotes, but I'm the IT person in my close family. Used to get calls all the time to fix slow laptops, CD drives not working, keyboard not working, system not booting, popups everywhere, apps crashing, you name it. Each would take insane amounts of time to troubleshoot. And then sometimes their machines just needed to be upgraded because they were running the new office, and the new skype and the new chrome, antivirus, etc, and the 3yo system could barely keep up, but they just wanted a quick fix, not spend $$$. I even installed teamviewer and some support tools to save the untold amounts of time. Then I bought macs for everyone, installed iWork, 1Password and taught them how to use them. haven't heard a peep. One of the best purchases of my life.
- aloknnikhil 3y ago100% agree on Macs. Personally I have never had to play IT support when my parents had a Mac. Now with Windows, it’s basically whack-a-mole. Some days the camera stops working and some days WhatsApp doesn’t startup. And they are not power users by any means. So they don’t muck around with their setup either.
- wccrawford 3y agoWe've had to do tech support for family using Macs, but I'll admit it's been less than my Windows-using family. I have 1 family member in mind in particular that I think would have been better off with a Mac. And I probably would have been better off, too, because I could tell them I don't know much about them and send them to the store with a clear conscience. ;)
- willio58 3y agoDid this with my dad and it’s been years since the last IT call.
- jeroenhd 3y ago> they just wanted a quick fix, not spend $$$. > Then I bought macs for everyone I bet you would've gotten similar results if you spent the same amount of money on Windows computers. For example, my dad is using an 8 year old Windows computer that he got second hand. It works absolutely fine because it wasn't underspecced at the time it was produced. People underestimate the difference investing in good hardware makes. They see $300 computers and expect them to work just as well as a $1200 top of the line machine, and then get frustrated at how slow their Celeron machine gets after getting their expectations crushed. Getting mad at a "broken" computer is easier than admitting you messed up and made a terrible investment.
- aidenn0 3y agoThis is way better than I thought. The most common computer applications boost productivity by way more than 25%, so computers are an easy net win.
- GTP 3y ago> The computer could easily solve the problems without displaying this, while it provided a back-up version of the system for us, so that we could continue to work with our tasks undisturbed" How could this work? Teorically, the OS could detect that an application crashed and start it again. But to restore the state the application was in before it crashed, it would need to scan the application's memory and derive the state from it, hopefully without also recreating the conditions that lead to the crash. While this could maybe be done, it would require the OS to know the application's internals extremely well, so it isn't feasible to apply this at scale. Or am I missing a simpler way to do this? Maybe the OS could save snapshots of the application's status. This way it wouldn't need to know the application's internals, but there would still be the problem of how to know which is the last good status that will not cause a crash a few moments afterward.
- jesprenj 3y agoPerhaps you are describing Erlang? https://en.wikipedia.org/wiki/Erlang_(programming_language)#:~:text=%22Let%20it%20crash%22%20coding%20style https://en.wikipedia.org/wiki/Erlang_(programming_language)#...
- GTP 3y agoWikipedia says: "When a process crashes, it neatly exits and sends a message to the controlling process which can then take action, such as starting a new process that takes over the old process's task" But this seems only a small piece of what would be needed. And if the idea is to have a main process spawning a tread (or process) for each "thing" it has to do so that the thread can be neatly re-spawed in case of failure, how is this much better done in Erlang than in any other programming language? Can you please elaborate?
- wizofaus 3y agoFurther, if you restore an application's state to exactly what it was before it crashes, computers being the annoyingly deterministic machines they are, there's really only one possible outcome...(*) State isn't what you want to restore, it's "valuable user-created information". And I don't know of any platforms where you can clearly mark data as belonging to that category. (*) accepted, some crashes will occur due to things outside the application's control, and may conceivably succeed on retrial - but even that relies on being able to restore application state to some "last known good" state.
- zapdrive 3y agoAs someone hosting my own smart home (Home Assistant), NVR for cctv (frigate), cloud (NextCloud), file syncing (Syncthing), plus various others things like pihole, etc. and giving tech support to all my family members who are using all these services, I think it's more than 20% of my time! But it's totally worth it.
- ilyt 3y agoI haven't touched my NAS for months. Just Debian dist-upgrade once every 2 years
- abramN 3y agothis is where we need to start putting a premium on the customer's time. If a company sell you a product, and you spend 4 hours on the phone with support for an issue that turns out to be their fault, you should get reimbursed or credited for that. If a customer has to spend time repeatedly "turning it off and on again" - the customer should get a credit for that. Yes, this will require companies to use all of their telemetry and logging for tracking lost customer time due to their errors.
- desireco42 3y agoChromebooks to the rescue... for majority of people, even a lot of devs and designers, those work just fine.
- Cupprum 3y agoThe normal person working with a computer is not a developer. Most of the jobs would be heavily influenced by the microsoft suite. Microsoft in denmark is very popular, thanks to their amazing marketing team targeting corporates. Therefore this research just shows that closed source microsoft products do not work 20% of time.
- hackeredje 3y agoIt would be interesting to see what the numbers are for IT 4 IT systems , scripts, batches, integrations, countless programs in countless languages including programs where nobody who knows anything about the system or language is available and no help or documentation or vendor is present anymore.
- throwawaaarrgh 3y ago20% on failures, 60% on work that wouldn't be necessary if we didn't have to work around all the inefficiencies, incompatibilities, limitations, poor practices, bad design, etc Just one example: all the time you spend building and maintaining a configuration management system to "fix" system state. Versus an immutable system, that when its state is wrong, you just delete it and make a new copy from the old immutable state. 90% toil becomes 10% toil. That's what good design gets you.
- jeroenhd 3y agoTerrible software, especially terrible business software, is such a terrible waste of time. This is why Excel still reigns supreme; it takes months of production bug reports for flashy web dashboards to gain the same reliability and functionality of that VBA hell file someone in accounting dropped on the network share five years ago. On the other hand, there's a terrible lack of training in many areas. "Oh, I'm not good at computers" is still used as some kind of endearing excuse. I don't expect people to upgrade their own RAM, but looking through the browser history or finding a file in any file explorer should be requisite skills for any office worker. I get it. "I'm not good at computers" worked for the first twenty years they had to use computers, so there was no incentive to learn. But at some point we have to stop allowing this lazy excuse and start adjusting our requirements. Most people use computers in some fashion, I doubt you'd allow an electrician to get away "oh sorry, I'm not good at using screwdrivers". It's spreading to younger generations as well. The smartphone generation is growing up with an equally terrible understanding of computers as the older workers, because of the appification of everything and the absolute lackluster computer skills of many (already underpaid) educators. It used to be that most of the tech support calls I received were about cheap computers bogged down with adware. SSDs fixed most of that. Now, the tech support calls are all things I was taught in high school.
- ant6n 3y agoI spent a couple days getting SketchUp to work under Wine (thanks elemtary OS for not allowing updates making me stuck on old version of Wine, plaOnLinux bundles some newer versions tho). After working with Sketchup for a week, realized that some features didnt work under wine, so went to fix the windows dual boot that was destroyed when I had previously resized the partition using gparted. Fiddling with win recovery didnt work, so I needed a win boot disk. It turns out that the win10 image includes a 4.5G file, but EFI needs the boot image to be fat32, so no files larger than 4G. That must be one of the dumbest microsoft choices, to not split up that file. Somebody online suggests to use gparted to create two partitions on the usb stick, one fat32 and one ntfs, for the boot and the install files - and the installer will automatically recognize that. Anyway, that also took a couple of hours to set up, also the fresh win10 install and setup. Head->table. …Yes, we can waste a lot of time on computer problems.
- rootedbox 3y agoIt's not waste.. it's cost.
- deleted 3y ago[deleted]
- smallerdemon 3y agoI make my living within this 20% of non-functionality.
- smallerdemon 3y agoAs dumb as it always comes across, telling people to reboot their systems after nearly 25 years in IT support is something we're still doing to this day. And we're still doing it because it works more often than not when someone is calling about performance problems. Why? It's not unusual to see uptime numbers in the 300s or longer for some people. We all have that story. One was someone I work with telling my his laptop was interminably slow and unusable and wondering what he could do to fix it. First question: "How often do you restart it?" Him: "What do you mean?" Me: "You know, turn it off and back on, or just select restart." Him: "Oh, I've never done that ?" Me: "Hm. How long have you had it?" Him: "Four years." Four years without a reboot. The next week when I saw him and asked him if restarting it helped: "Yes! It's running like new again!" My analogy for this is simple: Do you clean your house? Yes. Do you do it intentionally? Like, you know, set out to do it? Or does it just 'happen' passively without you doing anything at all? (Paying someone else to do it not withstanding.) Most people actively, intentionally clean. But you know what they don't do? Actively, intentionally get it dirty. Getting dirty is a passive action of living; of just existing and functioning. It's the same for your computer. Using it causes clutter that a reboot will clean up. But you have to do the reboot intentionally.
- hiq 3y ago> It's not unusual to see uptime numbers in the 300s or longer for some people. Do you mean 300 days? Which consumer OS allows you to skip any reboot for that long? In practice IIRC macOS and Windows basically force you to do it regularly, with users frequently complaining about this (although they got better at saving and restoring state I think?). Some Linux distributions also ask you to reboot into an updated kernel once it's available, for security reasons. So I'm a bit surprised that a user would end up with such a long uptime without doing it on purpose.
- xboxnolifes 3y agoMore recently with Windows 10? Far fewer. But just back with Windows 7 it was easy to let your computer run close to forever. I would host game servers on my personal computer and it would run for weeks to months without a reboot. I would usually only reboot because I would install new software that required one.
- yupitstruenow 3y agoI would double that if you realize how much mud you have to walk through in JavaScript's currently fashionable landscape just to play with html tags.
- kmoser 3y ago> "Part of the solution may be to shield us from knowing that the computer is working to solve a problem. In reality, there is no reason why we need to look at an incomprehensible box with commands or a frozen computer. The computer could easily solve the problems without displaying this, while it provided a back-up version of the system for us, so that we could continue to work with our tasks undisturbed," says Kasper Hornbæk Says the researcher who has no practical experience in development. While it's true that some OSes (I'm looking at you, Windows) and applications have less than stellar UIs, getting the entire stack (including hardware) to cooperate on a consistent basis is exceedingly difficult without NASA-level engineering. Given how many parts of a computer (again, both hardware and software) are churned out with an eye more towards profit than reliability, it's a miracle things work as well as they do.
- rmah 3y ago"It's incredible that the figure is so high"... lol, 20% seems incredibly low to me. The "study"'s authors must have a really low quality bar for what a malfunction or delay is.
- mlinksva 3y agoThe actual study, full text https://dl.acm.org/doi/10.1145/3582432 https://dl.acm.org/doi/10.1145/3582432 I only skimmed, but two things struck me: (1) previous studies conducted 2003-2006 found 44-50% time lost to frustration, this one found 11-20%. That's a huge improvement! As bad as computers are today, they were far worse 20 years ago. Progress! (2) Performance (top 3 frustrations are the computer is slow/froze/crashed) is the top frustration.
- EVa5I7bHFq9mnYK 3y agoAdd FB and Twitter to the list of "computer problems", and we are wasting 80% of our time.
- drngdds 3y agoI'm a programmer so I waste 100% of my time on computer problems
- jrm4 3y agoSure, and let's not kid ourselves: Hacker News is a perfect breeding ground to create, much more than solve those problems. Making "startups" and "companies" the default way to "do software" is sometimes necessary, but very often not a good idea. It's absolutely fine to use software, and companies, to solve problems -- but when "software by company" is the focus, a whole lot of crap happens.
- rodgerd 3y agoYeah, it's interesting because the commentariat are overwhelmingly angry that they can't sideload on iOS, that people buy iPhones because they have better things to do that sysadmin phones and lightbulb (as an example). The weight of HN opinion is relentlessly hostile to people who think their devices should be more like toasters and less like MIT labs circa 1984.
- raygelogic 3y ago20% seems like an underestimate, especially if you consider a lack of knowledge of how to use one's computer to highest efficiency. also, most platforms suffer from feature bloat without a cohesive user experience. probably because they are trying to capture the widest audience, without carefully planning alignment/integration across features.
- biggestriverman 3y agoI would've commented earlier but couldn't get the link to load
- sp332 3y agoIt's an average. So another way to look at this is: we are wasting 20% of our people on computer problems.
- jen729w 3y agoWorth noting that this study, which I just happened to read today, is small (n=234, with the number of useful responses even lower). And the ‘up to 20%’ refers to the fact that they had some odd responses which indicated that the time wasted was the entire hour of the study. If they corrected these down the figure becomes 11%. Oh and it’s self reported. From participants crowdsourced at Prolific, who were paid. It didn’t seem like the most rigorous study to me. And I’m invested in the result being bad, as the thing I do claims to solve some of these problems!
- polyterative 3y agoThe problem is that we think that developers make software to be useful, the truth is that developers make software because their companies need to make money. It was really hard to accept this as a developer when I started to do this as paid job