Slashdot Mirror


Workers Will Smash Their PCs To Get an Upgrade

An anonymous reader writes "One in four office workers reckon that the best way to get a new work computer is to smash up the one they have — either that or to take it down to the junk shop themselves. Some 40 per cent of office workers complain that their aging workplace PC hurts their productivity and many are tempted to resort to extreme measures to get an upgrade, including taking a hammer to the aging beast on the desktop. Some ten per cent of UK workers said they'd even resort to buying new parts for their work devices themselves to perform their own upgrade; particularly those who work in smaller organizations."

28 of 533 comments (clear)

  1. Never underestimate the power of liquids by grapeape · · Score: 4, Interesting

    I worked in a office where about once a year one of the employees would "spill" coffee on her laptop..usually a week or so after she noticed a deployment of new laptops in some other department. It worked until she moved to a floor with security camera's and was caught...after that her replacement was the one that recieved a shiny new one. The sad part was the machines she had were never out of date they simply became bogged down because of her browsing and installing habits, but rather than ask to have it cleaned up or god forbit learn to do it herself she would just have an "accident".

    1. Re:Never underestimate the power of liquids by Moryath · · Score: 4, Insightful

      Try working in most actual business environments.

      The argument always goes back and forth like this:

      IT Side - we have the following reasons that normal users shouldn't be installing programs themselves.
      - Security risk of adware/malware/bundleware
      - Number of incidents where machines have been compromised.
      - Number of incidents where complaints of "my machine is slow" turn out to be the result of user filling drive up with crap

      User side -
      - "But it takes more than 5 minutes for them to come down and install (program X that's actually work related) for me." Nevermind that these installs happen maybe once per year and if they would bother SCHEDULING with us...
      - "But I want to try out (program y) to see if we can use it in the business..."
      - User happens to be the PHB's son or is fucking the PHB on the side.

      Brain-dead PHB side-
      - "My employees are complaining that you IT guys are getting in the way of their work! Fix it so they can install things!"
      - One month later: "Megan's machine got infected again. Why the hell aren't you IT guys stopping this from happening? Do whatever it takes to stop this from happening again!"
      - One more month later: "Megan's complaining you took away her install rights! I need her to be working as best as possible, give them back to her! She can't possibly cause problems with that!"

      Now add in that you might be working in an EDUCATION environment - where every tenured faculty member is also a brain-dead PHB.

    2. Re:Never underestimate the power of liquids by MoonBuggy · · Score: 5, Insightful

      I don't doubt that what you say is accurate, but I'm amazed it's still socially acceptable for people to be unable to use the basic technology we interact with every day. A person who needs to drive a company vehicle as part of their job would be out pretty quickly if they kept crashing into trees - sure, the occasional genuine accident happens, and will be overlooked, but negligence/stupidity/repeated incompetence will (rightly) get you fired. There's absolutely no reason that the same shouldn't apply to people using company computers.

    3. Re:Never underestimate the power of liquids by Culture20 · · Score: 3, Insightful

      that's the real trick, if Windows had and enforced proper user/system separation then companies could lock down the systems that would limit that crap. Windows and it's applications assume you have full admin rights all the time. UAC while bad was a good step MSFT should have just pressed harder program developers to code properly, and forced all XP programs into a hard lock down mode.

      Are you from 1999? Software developers stopped assuming users have admin access a few years after XP hit the scene. It's only rare medical of scientific control software that's written that stupidly anymore. And guess what? There is specialty scientific software for Linux out there that assumes you're root.
      And windows is easy to segregate admin access on desktops either manually or via GPO. You can even list admin users additively or destructively(replacing the current list, preventing admins from adding someone else as an admin).

    4. Re:Never underestimate the power of liquids by drsmithy · · Score: 3, Insightful

      that's the real trick, if Windows had and enforced proper user/system separation [...]

      It has had for nearly twenty years. Fifteen if you only want to start counting from NT4. The problem isn't the lack of OS capability.

      breaking easy backward compatiblity in the name of security isn't a bad thing.

      Apparently it is. Just look at the negative commentary in Slashdot about UAC, from people who should know better.

  2. You mean monitors? by Toe,+The · · Score: 4, Insightful

    It's funny how many people point to their monitor and call it their computer. I can imagine a lot of people smash up their monitor expecting that it will result in their getting a new computer.

    What I'd really like to know is how many people do that; get a replacement monitor; and say, "Wow, this new computer is so much faster!"

  3. Obligatory by cashman73 · · Score: 3, Funny
  4. It's Not The Hardware... by benjamindees · · Score: 5, Insightful

    The reason most office workers are unproductive has nothing to do with their hardware.

    --
    "I assumed blithely that there were no elves out there in the darkness"
  5. SSDs to the rescue? by chemicaldave · · Score: 4, Interesting

    Obviously the 5 year old computers in TFA could use an upgrade, but I've found that for my aging workstations, a simple storage upgrade to an SSD would probably be more than enough to increase my productivity. Storage is the new bottleneck, not processing power.

  6. What a bunch of dummies by countertrolling · · Score: 5, Funny

    Slow computers means taking lots of breaks and going out for a snack. I don't want to be more 'productive'. I want to relax, and a slow machine helps me do just that.

    "What the hell is taking you so long?"

    I just shrug and point to the screen...

    --
    For justice, we must go to Don Corleone
    1. Re:What a bunch of dummies by bunratty · · Score: 3, Insightful

      Most unproductive workers are unproductive because they're lazy and dumb. They blame the computer because it's easier than admitting they're lazy and dumb. If programmers could write complex programs in the 50s and 60s using punched cards and waiting overnight for the output of their runs, a smart and diligent worker could figure out how to queue up work so they could be productive even with a "slow" computer. Their "slow" computer is thousands of times faster and is available to them nearly all day! Only a poor worker blames his tools. Now if the computer just plain didn't work, that would be a different story...

      --
      What a fool believes, he sees, no wise man has the power to reason away.
    2. Re:What a bunch of dummies by Jaysyn · · Score: 3, Insightful

      Their "slow" computer is thousands of times faster and is available to them nearly all day! Only a poor worker blames his tools. Now if the computer just plain didn't work, that would be a different story...

      Says the person who has never used a serious CAD or GIS application on non-cutting edge workstation.

      --
      There is a war going on for your mind.
  7. Easy cure by Chrisq · · Score: 5, Interesting

    Any smashed PC is replaced by the oldest in stock. new replacements for those which reach the budgeted life intact.

  8. Railroad workers did the same thing 100 years ago by AnalogDiehard · · Score: 4, Interesting

    Over 100 years ago, many railroads were tightwads and wouldn't issue new lanterns to conductors and brakemen to replace their aging ones. They finally would ditch their lanterns over a river bridge as they approached the yard limits, then report the lanterns as missing to the yardmaster who would issue them a new lantern.

    --
    Eternity: will that be smoking, or non-smoking? I Corinthians 6:9-10
  9. Re:Spend money to save money... by Austerity+Empowers · · Score: 4, Interesting

    That's about right. I think my company dropped $50M on a "new brand image" (that looked a lot like the old brand image), another $42M on a new "one size fits all" database that actually doesn't work for almost anything, tens of millions in golden parachutes.

    "Can I get a monitor with a display resolution larger than 1400x900?" "No." "But...but...I can't even see a page of schematics at a time, and the code I'm maintaining is a hundred thousand lines split in to dozens of files!" "The budget is tight, can't do it."

  10. Re:smash by ElectricTurtle · · Score: 4, Funny

    You apparently failed to notice the the phrase 'her replacement'.

    --
    I support the Slashcott and will not be reading or commenting from 2/10/14 to 2/17/14. Beta is steaming pile of dog shit
  11. Re:Maybe I should try this by grub · · Score: 4, Funny

    Yeah, we have some poor Vista users.

    --
    Trolling is a art,
  12. Re:bean counters hate computer upgrades? by Hatta · · Score: 4, Insightful

    we try to show business owners that 10 year old computers really are a problem, even when they still work.

    If they still perform the task for which they were intended 10 years ago, why are they a problem?

    The real problem isn't old computers, it's new software. New software comes out which doesn't really do anything better than your old software. But people you do business with upgraded, so now you have to upgrade your software to interoperate with them. But the new software runs more slowly, and now you need new hardware to do the same task you were doing just fine 6 months ago.

    For a stand-alone application, there's nothing wrong with 10 year old computers. Or 20 year old computers, for that matter. DOS still works as well as it ever did.

    --
    Give me Classic Slashdot or give me death!
  13. Re:Spend money to save money... by khr · · Score: 4, Insightful

    "Can I get a monitor with a display resolution larger than 1400x900?" "No." "But...but...I can't even see a page of schematics at a time, and the code I'm maintaining is a hundred thousand lines split in to dozens of files!" "The budget is tight, can't do it."

    You're asking for the wrong reasons... With a bigger monitor you can show the new brand image more clearly, you can use the extra space to display the image of the new mission statement... You'll always be on track that way, you'll know the schematic you can't see clearly on the screen is driving customer satisfaction and global leadership and all that...

  14. Just because they say it, doesn't mean they do it. by mr.nobody · · Score: 3, Insightful

    All IT people have heard the joke, "Well, if I take a hammer to it..." But that doesn't mean they do it. From the article, the headline reads as though users are causing deliberate damage to their computers in order to receive an upgrade. Read the actual text however, and while users are saying that, there isn't anything presented to show there are widespread acts of vandalism happening. The only real takeaway from this article is that some UK offices are using significantly outdated equipment. The headline is just sensationalism. I hate to say it, but I think /. fell for this one.

    --
    mr.nobody
    --Don't you wanna go where nobody knows your name?
  15. Re:Something to be learned from the spiller by clang_jangle · · Score: 5, Funny

    The only way is to issue destructive/"accident prone" people used or reconditioned machines. I always say, "take care of this solid, but old machine for 18 months and we'll see about letting you have a new one.". It works pretty well. That coffee spiller would have been quite deflated if she'd had to deal with me, heh -- "I'm so sorry you had an accident with your Pentium M laptop; here's a nice, reconditioned PIII for a replacement -- awwww and you were only 6 months from getting one of the new ones... Well, maybe(the last quarter of 2012!".

    --
    Caveat Utilitor
  16. Re:The Best Way by MyLongNickName · · Score: 5, Insightful

    Wow. What a horrible idea. Never, ever, donate money to your employer. And even if you take it with you when you quit, you have donated money to your employer.

    As a manager, it is MY job to give you the tools to make you more productive. If I am not making the right trade-offs, then I am not doing my job. And if I am not doing my job, you shouldn't make me look good by donating from your own pocket.

    --
    See my journal for slashdot ID's by year. Mine created in 2005. http://slashdot.org/journal/289875/slashdot-ids-by-year
  17. Re:Maybe I should try this by Zeek40 · · Score: 4, Interesting
    They still launch rockets with VAXes. I worked on the Space Lift Range System Contract for my Internship, and learned the terrifying fact that they're launching giant missiles into space 20 miles from my house with Computers older than me and ancient wire-wrapped TTL chips in perfboard, and basically no one knows what hardware does what anymore because everyone who built the stuff is retired or dead.

    We had a launch control board assembly fail shortly after I started my internship, and a rocket was supposed to go up the next week. No one had any idea where or how to get a replacement, then someone remembered that the old 'backup' system was moved to the Kennedy Space Center Museum. They made a call, grabbed an armed guard from the base, drove up to KSC, swapped the broken control board with the museum piece, and launched a rocket with it a week later. To the best of my knowledge, they are still launching rockets with a piece of hardware literally salvaged from a museum of history.

  18. Re:Same old bottleneck by b4dc0d3r · · Score: 3, Insightful

    I installed Nt 4 on a 75 mHz desktop, thinking I might go MSCE or something. If something was reading the hard disk, I could watch every control get painted. Erase, draw the outline, put the letters on, do a checkbox. Start task manager to see what is taking up the CPU, 20 minutes for that to load. Then I see CPU usage is only about 50%. Why? Windows 98 on the same machine did not have the same problem, so it wasn't the hardware.

    I wish I knew. I get the same thing on Vista with a dual-core 2.5 gHz processor. Outlook refuses to show me meeting info. It's not responding, then slowly responding, then paints the reminder window. Can't see the dial-in number, waiting for it to paint. Get 3 instant messages - are you joining? Yeah, paste me the number and i'll be right there.

    PC backup, antivirus, update scans, hard drive maintenance - any prolonged disk activity brings the computer to a halt. It's not just me - yesterday we had a chief architect say "Id bring that up but my backup just started" and everyone said "oh, yeah we know."

    Simple version: my notebook is slower than my previous XP one, and I just tolerate it until we get the OK to move to Windows 7, and hope it's slightly faster because the processor is faster. It won't be, because it will have a 4 million GB drive at 5400 RPM.

    With Windows NT, storage has always been the bottleneck. At least until you throw enough memory at it that it can hold all your apps plus an ample disk cache. Backup, antivirus, etc. tasks use a lot of non-cached data, and there goes your advantage.

  19. Verified in the real world. by PhreakOfTime · · Score: 4, Interesting

    I have done exactly this to one of the clients I had.

    It was a small business, with about 10PC's around the office for the agents to use as needed. One of the agents kept whining that this certain computer was 'old' and therefore to slow for him to work on. It was keeping him from getting as much done as he thought he could.... or that was what he kept saying.

    So, we talked with the owner of the company before rolling out our change; A brand new... case. Thats it, new case. Same guts, same hardware, same everything... but the case.

    Suddenly, this was the 'fastest' computer in the office(yes, all the computers were exactly the same hardware), and the complaining stopped(for awhile)

    As was expected, this did NOT increase this persons productivity. As was explained to the owner before the upgrade, this person was using every excuse in the book to get away with doing as little work as possible. It was always some external factor that was the problem. This happens a lot with people who do nothing more than what we lked to call 'play office'. They sit in the required space, show their face, but don't actually contribute anything meaningful but body heat in the winter time.

    By definition, stupid people are EASY to manipulate. Use them to your advantage, or suffer the fools forever.

  20. I hope you also realize though... by Moraelin · · Score: 3, Interesting

    I hope you also realize though, that the programs we do today are also much more complex than you could do on punched cards back then. Even small-ish programs can have a million lines of code or more. (Larger ones, more. Windows XP was some 35 million lines, Vista over 50 million, and that's not counting such stuff as C libraries and whatnot.)

    Even at 1 gram per card, and each card being a line of code, a 1 million line program would weigh literally a metric ton. Did you see many people carrying their program to the computer with a small truck?

    Even the kind of internal complexity that went into programs those days was actually a lot lower. E.g., you didn't need to optimize access to shared data for 1000 web sessions at the same time, when the program is run as a sequential batch. (Yes, concurrent stuff did come around too, but later, but not in the days of paper cards.)

    Most such batch programs I've seen actually are just doing some fairly simple calculation in a loop, that nowadays you wouldn't even write a program for. It's stuff that the PHB would do directly in Excel.

    In other words, yeah, I love reading such posts that tell me that someone is too fucking stupid to even understand the difference between programs these days and most programs that were done on punched cards. And probably the 50's-60's and punched cards were the last time they were competent. I really love that kinda PHB, who thinks that because he once did some piss-poor two-level loop on punch cards back then, it means he's qualified to judge modern programs and deadlines. No, really.

    --
    A polar bear is a cartesian bear after a coordinate transform.
  21. Fighting for PC user rights by hellfire · · Score: 5, Insightful

    Here let's flip that around a bit, just as another example.

    IT Side - we made up the following reasons that normal users shouldn't be installing programs themselves.
    - Microsoft gave us a document that says we should configure it like this so we did just that.
    - We are too lazy or overworked or underpaid to think too hard about our user's needs
    - We never bothered to ask what user's requirements were, we just assumed it.
    - IT person happens to be PHB's son or fucking PHB on the side.

    User side -
    - I have to be able to do work that my boss has required me to do which is core to the business making money!
    - I need to be able to test certain situations in order to come up with a new means to be more productive and save the company money!
    - Arbitrary restrictions are stifling users for the sake of making IT look good.

    Brain-dead PHB of IT side-
    - "We have a policy and we stick too it and we can't change it."
    - One month later: "We have a policy and we stick to it and we can't change it."
    - One more month later: PHB is out of the office playing golf with someone while you fume over missing yet another deadline.

    Now add in that you might be working in a software development environment, where every IT rep treats you like an office temp and tries to give you access to MS office and internet explorer and nothing else and does absolutely nothing to understand how your own company's software works nor tries to understand what it takes to create, test, and support said software when your own customers have admin rights to their own machine and, funny, you don't, so you can't possibly figure out what their problem is!

    This is just a counter example to your stereotype. People in general are idiots, sometimes they are in IT, sometimes they are in the user base, and sometimes it's both. You can't paint one side with a broad brush and completely blame things like this on them.

    --

    "All great wisdom is contained in .signature files"

  22. Re:Maybe I should try this by Kreigaffe · · Score: 3, Funny

    That is both the most awesome and awful thing I have ever heard

    --
    ... still waiting for this free-as-in-beer free beer I keep hearing about. :|