Slashdot Mirror

← Back to Stories (view on slashdot.org)

Top 10 System Administrator Truths

Posted by CmdrTaco on from the my-users-never-lie dept.

Vo0k writes "What are your top ten system administrator truths? We all know them already, but it's still fun re-telling them. Stuff like "90% of all hardware-related problems come from loose connectors", even though you already know it's true, may save you from replacing the "faulty" motherboard if you recall it at the right time."

62 of 561 comments (clear)

  1. 95% of all problems.... by seramar · · Score: 5, Funny

    ... are operator errors. But you can't tell the operator that.

    --
    australian project gutenberg is better than the original.
    1. Re:95% of all problems.... by Rei · · Score: 4, Interesting

      It's interesting that everybody seems to know these things, and yet they still get us. A couple months back, I went through three power supplies before I discovered the fact that I actually had a power cable that was going bad. You don't even think of things like how power cables can go bad, but they do.

      --
      Very well; let this abomination unto the Lord begin!
    2. Re:95% of all problems.... by Anonymous Coward · · Score: 5, Funny

      "99% of all problems don't occur when the computer is off. That's why I always keep a pair of well-insulated pliers around."
      -- BOFH

    3. Re:95% of all problems.... by Anonymous Coward · · Score: 5, Funny

      When troubleshooting SCSI devices, always remember to light the black candles at midnight, and run the silver knife up the goats abdomen.

    4. Re:95% of all problems.... by mrn121 · · Score: 5, Insightful

      I know this was said as a joke, but I see this a lot amongst the geek community, the attitude that users just don't know what they are doing, and that is why they can't make anything work.

      Doing some GUI consultant work and writing a few users manuals for some pretty complex software has taught me one thing: Most user error is the fault of crappy software. A good setup (hardware or software) should be easy to use given the users.

      Now, obviously it is all about knowing the audience. If you are writing an application for use by other software engineers versus people living in an assisted living home, well, that makes a difference, and you certainly can't cater to all people (for example the guy who writes code for a living but can't setup his own email at home).

      The bottom line is, as much as it displeases us, not everyone is a geek. Not everyone cares about the latest firmware for their router, the latest patch for Call of Duty 2, or how to make a projection TV from an old overhead projector and a laptop from eBay. Our job, as geeks, is not to show everyone why they SHOULD care, but rather to make it easy for those who don't care to still do what they need to do.

      Just a few minutes ago I got an email forwarded to me from a "stupid" user who couldn't figure out how to perform what to me seems like a simple task in some software my team wrote. We emailed him the directions, even though they were very clearly stated in the manual that I wrote, but I took it one step further. I submitted a feature request in our bug-tracking database to put a message near where what he was trying to do to explain why that option is grayed out.

      Anyone can write software or setup hardware that has tons of geek features that we all like, but it takes a lot more effort to make the setup actually usable to the target users.

    5. Re:95% of all problems.... by seramar · · Score: 5, Insightful

      I did not say this as a joke, I was surprised it got modded so high. I work at a small service and repair shop, and you'd be surprised how many computers come back within a week or two after leaving the shop because the client did not listen to my suggestions and recommendations. I always tell them, we'd be happier to fix an issue that is caused because you followed our instructions than fixing one because you didn't. Still, they go on, installing file sharing software I did not recommend, ignoring their windows updates, and clicking "yes" or "no" on those bogus system-error messages, as opposed to the red x. And beyond that, we extend the invitation to any client to call us, free of charge, if they're not sure what to do. We're not bastards in here like people at a lot of computer shops, and we're willing to help, for free, if it's not time consuming and we can do it over the phone... but they hardly ever call while they're unsure, but only after they've broken something. I understand that they're not as savvy as us geeks, however, there are a few simple steps that they should follow based on our recommendations. The mechanic tells me to get my oil changed every 2,000 to 3,000 miles, so I listen. The guy at the salt water aquarium store tells me putting an anemonae in a tank is a bad idea, because when it dies (which it will in your little tank) it's going to kill all of your fish, unless you're really lucky... so I avoid the anemonaes. I'm not an expert, so I listen to those who are more knowledgable. Anyway I've talked too much.

      --
      australian project gutenberg is better than the original.
    6. Re:95% of all problems.... by bhadreshl · · Score: 5, Insightful

      The OSI model works in almost all aspects of computing and not just strictly networking.
      Application > Presentation > Session > Transport > Network > Data Link > Physical. This order is actually from layer 7 to 1.
      If you had followed the OSI model, you would've found out that the *first* thing to do would be to check the physical connection (aka power cord) and found your problem right away.

    7. Re:95% of all problems.... by grub · · Score: 4, Funny


      Indeed. Most of the problems here are "Layer 8" (the user)...

      --
      Trolling is a art,
    8. Re:95% of all problems.... by Brigadier · · Score: 4, Funny



      dude this maybe funny to you, but me and a dell technician spent 38 hours trouble shooting a poweredge scsi assemble. and I swear if voodoo was an option I would have tried it.

    9. Re:95% of all problems.... by SatanicPuppy · · Score: 4, Funny

      Effing Dell technicians. I had one power down a system to switch a hotswap SCSI drive, and wipe out the whole RAID. I was ready do do some serious voodoo right there in the server room, and I'm not talking about sacrificing a goat here.

      --
      ad logicam Claiming a proposition is false because it was presented as the conclusion of a fallacious argument.
    10. Re:95% of all problems.... by NateTech · · Score: 5, Funny

      Layer 8 - Religion ("We're a Microsoft shop.")
      Layer 9 - Politics ("The boss wants it, even if it's stupid.)

      Both of which are more important than the other 7 layers. ;-)

      --
      +++OK ATH
    11. Re:95% of all problems.... by gstoddart · · Score: 5, Funny
      When troubleshooting SCSI devices, always remember to light the black candles at midnight, and run the silver knife up the goats abdomen.

      I've found for SCSI-2, you want to move the knife in a downwards manner.

      And by the time you're working on low-voltage differential SCSI-3, you want to make a left-to-right transverse cut. The second yellow candle is crucial in this case.
      --
      Lost at C:>. Found at C.
  2. In no particular order.... by FalconZero · · Score: 5, Informative
    Fixing Problems
    ---------------
    • Rebooting Solves 90% of Windows problems.
    • Users are the cause of the problem 90% of the time.
    • The weakest link(s) in your security is/are human.

    Getting Help
    ------------
    • Good manuals should be read before you do anything.
    • Bad manuals should not be read UNDER ANY CIRUMSTANCES.
    • Google is your best freind. ever. period.

    Other People
    ------------
    • Good managers ask for something in 5 days, but need it in 6.
    • Good developers/suppliers promise something in 5 days, but deliver it in 4.
    • "I don't know, but I'll find out" is always better than "I know" (when you don't).
    • Technical support hotlines will invariably tell you what you already know.
    --
    Windows in 6 Bytes (IA-32) : 90 90 90 90 CD 19
    1. Re:In no particular order.... by Hektor_Troy · · Score: 5, Funny
      Good manuals should be read before you do anything.
      Bad manuals should not be read UNDER ANY CIRUMSTANCES.
      Fortunately all manuals come with stickers like "Super manual A+++++" or "Horrible manual, stole my wife, raped my dog F--------".
      --
      We do not live in the 21st century. We live in the 20 second century.
    2. Re:In no particular order.... by jellomizer · · Score: 4, Insightful

      "Rebooting Causes 90% of Unix problems."

      Well that is usually a half truth. Usually when you reboot a Unix system you do it for the following reasons.

      1. You screwed up and have no alternative Interface to get in.

      2. Your system has been on so long that you want to reboot it to see what whent down without it telling you.

      3. You need to had hardware and it isn't hot swapable.

      4. The disadvantage of downtime out waighs the time it will take to fix it without rebooting.

      5. You lost power for an extended period of time.

      6. Management tells you so.

      7. Upgrading the OS to a level all services need to be restated.

      8. There are many unknown processes and you want to be sure you are not stopping an important job.

      9. Other...

      But normally because the drives have been spinning for years. Having it Stop and then start again. Put strain on them and causes them to die. Or if the system has enough memory the drive may have died years ago but all the data is paged.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    3. Re:In no particular order.... by hotdiggitydawg · · Score: 5, Interesting

      I was thinking they were talking about "truths about system administrators", not "truths about system administration".

      Anyway, for the benefit of those who haven't seen this (very old and long, but somewhat entertaining) email that was doing the rounds a while ago... disclaimer: someone else wrote it, and I don't know who.

      KNOW YOUR UNIX SYSTEM ADMINISTRATOR - A FIELD GUIDE

      There are four major species of Unix sysad:

      1) The TECHNICAL THUG. Usually a systems programmer who has been forced into system administration; writes scripts in a polyglot of the Bourne shell, sed, C, awk, perl, and APL.

      2) The ADMINISTRATIVE FASCIST. Usually a retentive drone (or rarely, a harridan ex-secretary) who has been forced into system administration.

      3) The MANIAC. Usually an aging cracker who discovered that neither the Mossad nor Cuba are willing to pay a living wage for computer espionage. Fell into system administration; occasionally approaches major competitors with indesp schemes.

      4) The IDIOT. Usually a cretin, morpohodite, or old COBOL programmer selected to be the system administrator by a committee of cretins, morphodites, and old COBOL programmers.

      HOW TO IDENTIFY YOUR SYSTEM ADMINISTRATOR:

      -- SITUATION: Low disk space. --

      TECHNICAL THUG: Writes a suite of scripts to monitor disk usage, maintain a database of historic disk usage, predict future disk usage via least squares regression analysis, identify users who are more than a standard deviation over the mean, and send mail to the offending parties. Places script in cron. Disk usage does not change, since disk-hogs, by nature, either ignore script-generated mail, or file it away in triplicate.

      ADMINISTRATIVE FASCIST: Puts disk usage policy in motd. Uses disk quotas. Allows no exceptions, thus crippling development work. Locks accounts that go over quota.

      MANIAC:
      # cd /home
      # rm -rf `du -s * | sort -rn | head -1 | awk '{print $2}'`;

      IDIOT:
      # cd /home
      # cat `du -s * | sort -rn | head -1 | awk '{ printf "%s/*\n", $2}'` | compress

      -- SITUATION: Excessive CPU usage. --

      TECHNICAL THUG: Writes a suite of scripts to monitor processes, maintain a database of CPU usage, identify processes more than a standard deviation over the norm, and renice offending processes. Places script in cron. Ends up renicing the production database into oblivion, bringing operations to a grinding halt, much to the delight of the xtrek freaks.

      ADMINISTRATIVE FASCIST: Puts CPU usage policy in motd. Uses CPU quotas. Locks accounts that go over quota. Allows no exceptions, thus crippling development work, much to the delight of the xtrek freaks.

      MANIAC:
      # kill -9 `ps -augxww | sort -rn +8 -9 | head -1 | awk '{print $2}'`

      IDIOT:
      # compress -f `ps -augxww | sort -rn +8 -9 | head -1 | awk '{print $2}'`

      -- SITUATION: New account creation. --

      TECHNICAL THUG: Writes perl script that creates home directory, copies in incomprehensible default environment, and places entries in /etc/passwd, /etc/shadow, and /etc/group. (By hand, NOT with passmgmt.) Slaps on setuid bit; tells a nearby secretary to handle new accounts. Usually, said secretary is still dithering over the difference between 'enter' and 'return'; and so, no new accounts are ever created.

      ADMINISTRATIVE FASCIST: Puts new account policy in motd. Since people without accounts cannot read the motd, nobody ever fulfills the bureaucratic requirements; and so, no new accounts are ever created.

      MANIAC: "If you're too stupid to break in and create your own account, I don't want you on the system. We've got too many goddamn sh*t-for-brains a**holes on this box anyway."

      IDIOT:
      # cd /home; mkdir "Bob's home directory"
      # echo "Bob Simon:gandalf:0:0::/dev/tty:compress -f" > /etc/passwd

      -- SITUATION: Root disk fails. --

      TECHNICAL THUG: Rep

    4. Re:In no particular order.... by notthepainter · · Score: 4, Funny
      6. Management tells you so.

      Back in the mid 80s a co-worker of mine had told his boss at a previous job that the unix machines needed to rebooted when the PIDs got too high! Great bit of fun at the PHB expense. (This is also the guy who submitted an purchase request for some close parenthesis... got it signed also!)

    5. Re:In no particular order.... by Gorbag · · Score: 4, Insightful
      • Good manuals should be read before you do anything.
      • Bad manuals should not be read UNDER ANY CIRUMSTANCES.
      Collary: there are no good manuals.
      --
      -- I speak only for myself
    6. Re:In no particular order.... by Stargoat · · Score: 5, Interesting
      Ten Truths:

      1. Adobe products and antivirus cause the most software problems, but you cannot live without either.
      2. Most computer hardware problems are the result of sticky rolls, janitors cleaning, computers being accidently kicked, or power failures. In that order.
      3. When calling HP or Dell about anything other than servers, you will get bad tech support.
      4. Three year warranties on individual PCs do not matter. On a system with dozens of computers, they pay for themselves.
      5. There will always be a lower price. Get over it.
      6. Phones cannot fail. Five nines of reliability is not good enough.
      7. Documented organization of the network and supplies will save you more time than the knowledge a thousand certifications brings (which isn't that much anyways).
      8. Researching and backing up information before beginning a project is the sign of a professional. So is spelling.
      9. Soft operating expenses are always more expensive than hard operating expenses.
      10. When working on a project, document everything. It is almost never needed, but if your coworkers know you have it, they will not try to screw you.

      --
      Hoist Number One and Number Six.
    7. Re:In no particular order.... by bitslinger_42 · · Score: 4, Insightful

      "Rebooting Solves 90% of Windows problems"

      Nope. Rebooting only clears 90% of symptoms, it doesn't necessarily make the problems go away. For example, if you have a webserver that's got a memory leak and that leak takes 72 hours to fill RAM to the point that the system becomes unusable, rebooting clears the symptom (unusable system) but doesn't resolve the problem (bug in the webserver). Too many people think that the reboot fixes the problem, so they don't ever bother finding out what the real problem is.

  3. Never.... by citizenklaw · · Score: 5, Funny

    Never post stupid top ten administrator lists on Slashdot, lest I have to spend my time restoring a web server from backup.

    --
    the future is but past forgotten
  4. Truth... by gowen · · Score: 5, Interesting

    ... even though it's better than it used to be, registry corruption is still the number one cause of boot failures in Windows XP. And the contents ntbtlog.txt and the Recovery Console are still horribly inadequate tools for fixing it...

    --
    Athletic Scholarships to universities make as much sense as academic scholarships to sports teams.
  5. Simple by mysqlrocks · · Score: 5, Informative

    The solution to the problem is almost always simpler than you think. You can often cause more problems trying to fix a problem then the original problem itself. When you try one thing and it doesn't work, reverse the changes before trying the next thing and document each change.

    --
    Bradley Holt
  6. #10 Reboot should be #1 by digitaldc · · Score: 4, Funny

    When all else fails, reboot. If it still fails, blame the user.

    --
    He who knows best knows how little he knows. - Thomas Jefferson
    1. Re:#10 Reboot should be #1 by j-cloth · · Score: 5, Funny

      The other benefit of a reboot is that, in the case of weird problems, even if it doesn't work it gives you two minutes to think about other possible causes without having the user nagging you.

  7. #6.5: by Dirtside · · Score: 5, Funny

    IT'S NOT A CUPHOLDER!!

    --
    "Destroy science and religion. Science would re-emerge exactly the same; but not religion." - Penn Jillette, paraphrased
  8. All I got to say is... by mike77 · · Score: 5, Insightful

    PEBKAC

    --

    --Keeping the flame wars alive, one post at a time

    1. Re:All I got to say is... by donnyspi · · Score: 4, Funny
      PICNIC

      Problem In Chair, Not In Computer :-)

  9. Top 3 by saphena · · Score: 5, Interesting

    1) Never believe anything anyone tells you: always test for yourself.
    2) Always ask the dumb questions: is it switched on?
    3) Reboot cures most things EXCEPT rm -r * when logged in as root

    After that, things could get tricky.

  10. PEBKAC by Billosaur · · Score: 4, Funny

    Most users should not being allowed to operate computers, let alone drive cars. Sysadmins need to learn who these people are and minimize the damage they cause. I suggest randomly changing their password every day until they quit in frustration.

    --
    GetOuttaMySpace - The Anti-Social Network
  11. My own list by vaceituno · · Score: 5, Interesting

    -You shall be very pessimistic
    -Make sure you can leave exactly like it was before you touched it.
    -Dont fix what aint broken.
    -Start from a known state of the system (switch off - switch on).
    -Even you are genius level techie, follow the manual, RTFM.
    -Dont reinvent the wheel. Compare with something thats working.
    -Cables are not perfect. If something doesnt connect, check lower levels first.
    -If its there, ther must be a reason. Never ever delete anything. Rename instead.
    -You memory is not infinite. Write what you do.

  12. From the user's side... by Otter · · Score: 4, Funny
    Top System Administrator Truths
    • The best way to improve security is to give users more, longer, more complex, more frequently changed passwords. Eleven characters, including uppercase, lowercase, numbers and Unicode, changed every 30 days -- it's easy! The users should just keep making up new, easy to remember mnemonic phrases that, uh, include words begining with numbers and punctuation.
    • If users modify their system in any way, anything that happens is their fault. Smoke coming out of the power supply? It's because you added new applications to the Start toolbar!
    • If I've never heard of it, you obviously don't need it.
    --
    What I'm listening to now on Pandora...
  13. Power cables don't really "go" bad. by hackwrench · · Score: 5, Insightful

    from bending them around and whatnot, they develop breaks that can get pushed back together. This is what causes the problem to be intermittent. The cable 'is' bad, not going bad. People need to be more careful in wrapping their cords up. There should be a little bit of slack in the loops or else the slightest bit of pressure will cause them to develop a break.

  14. We have the three rules. by LWATCDR · · Score: 5, Insightful

    Rule 1. They lie. End users often tell you what they think you want to hear. When asking a question you should use terms like. What does it say? vs Does it say this?
    Rule 2. They don't know they are lying.
    Rule 3. Sometimes they are telling the truth. Yes sometimes what you think is impossible really is happening or looks like it is happening.

    --
    See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
  15. Never make system config changes on Friday by winkydink · · Score: 5, Funny

    Unless you lack plans for the weekend.

    --

    "I'd rather be a lightning rod than a seismometer." -Ken Kesey

  16. My 2p by benbean · · Score: 5, Insightful

    Never put the screws back in the case until you've tested your new hardware is working.

    --
    It's a Unix system - I know this.
  17. Another one by missing000 · · Score: 4, Informative
    90% of all quotes on slashdot are made up :)

    Seriously, the "90% of all hardware-related problems come from loose connectors" bit is found nowhere in the article or on google for that matter...

  18. Top Ten Sysadmin Truths by Golias · · Score: 5, Funny

    Number One: You will die alone.

    --

    Information wants to be anthropomorphized.

  19. Work smatah. by wheezl · · Score: 5, Funny

    If your job requires you to wear a name tag, carry a gun, or administer a Windows system, you have made a serious vocational error.

    --
    -- oh.... so..... sleeeeeepy.
    1. Re:Work smatah. by dosquatch · · Score: 5, Funny
      If your job requires you to wear a name tag, carry a gun, or administer a Windows system, you have made a serious vocational error.

      My job requires me to wear a nametag while administering a Windows network.

      They won't let me carry a gun. Even though I asked really, really nicely.

      Bastards.

      --
      "Hey, the third matrix movie would have been good except for the plot,story, and acting." --AC
  20. 4 Rules by semifamous · · Score: 5, Interesting

    In my Tech Support experience, I have found only three basic rules.

    Rule number 1. People are stupid. This one is true of all people. Tech support, highways, shopping, whatever. This rule has been extended to cover just about any stupid thing that anyone does.
    "Why did that guy just..."
    "Rule number 1."

    "Did she think she could get away with that?"
    "Rule number 1."

    Rule number 2. People lie.
    Me: "Has the computer been restarted since the problem started?"
    Them: "Yes..."
    Me: "OK. Let's try restarting the computer now and see what happens."
    Them: "What do you mean by restart?"

    And when you add 1 and 2 together, you get 3. Sometimes, people are so stupid, they don't know that they're lying. You know these people. They're the ones who have "Windows 2000 XP" or "2000 ME." They're the people for whom "Nothing happens when I try to check my email. Nothing! Just this error message..." Not realizing that the error message is *exactly* what I was looking for. An error message is *not* nothing. Grr.

    There is a fourth rule that also shows up from time to time:
    Rule number 4. No good deed goes unpunished.
    In the famous words of the leader of the Uruk Hai from his battle call at Helm's Deep in The Two Towers: "Grr."

    1. Re:4 Rules by arkanes · · Score: 4, Insightful
      Not realizing that the error message is *exactly* what I was looking for. An error message is *not* nothing

      God, yes.

      "Nothing happens when I check my email."
      "Do you get an error message when you try it?"
      "There was some dialog on the screen, yeah."
      "Grr. What did it say?"
      "Oh, I didn't read it"
      Aaaarrgggh.

  21. My rule by ptomblin · · Score: 4, Funny

    It doesn't matter whether I'm giving or requesting tech support, the number one rule is that the person on the other end of the telephone is an idiot.

    --
    The next Cmdr Taco duplicate will be ready soon, but subscribers can beat the rush and see it early!
    1. Re:My rule by BushCheney08 · · Score: 4, Funny

      Something to remember: the converse is true, too : p

      --
      Be a real patriot: Question authority. Think for yourself. Formulate your own conclusions.
  22. First System Administration Truth by Master+of+Transhuman · · Score: 4, Funny


    Don't get linked to by Slashdot!

    None of the other nine truths will save your server!

    --
    Richard Steven Hack - This sig is TOO GODDAMN SHORT TO DO ANYTHING USEFUL WITH! MORONS!
  23. Acronyms by d_54321 · · Score: 4, Funny

    If the acronym contains an F, don't ask what it stands for.

    --
    Support the FairTax
  24. Re:Gunking up the works? by oneiros27 · · Score: 5, Funny
    what can a computer full of dust do to make it not work?

    Spontaneously combust

    Trust me -- you do not want to get that call:

    Caller: You know that machine in (room) that has a sign that says 'do not turn me off'? You: Yes ... what about it? Caller: There's smoke pouring out of it.
    --
    Build it, and they will come^Hplain.
  25. Re:Not too bad by Spy+der+Mann · · Score: 4, Funny

    No One Ever Got Fired For Buying Microsoft.

    Microsoft has been BOUGHT!?!?

    *Runs to Check the stock market*

  26. Type twice, hit enter once by bcattwoo · · Score: 4, Funny
    Read what you typed before hitting enter.

    Now let me just kill that last background process with the old 'kill %1'

    [$researchgroupserver]: kill 1 enter

    Crap!

  27. Treat users with respect by fantomas · · Score: 5, Insightful

    Treat users with respect even if they are clearly in the wrong. Don't patronise somebody if they haven't got the first idea about computers: educate, don't insult. I'm not a buddhist but the old karma idea of "what goes around, comes around" seems to play out in the long term. Being patient with somebody who's royally screwed up their computer pays off in six months time when you need them to put your expenses claim through accounts at 5pm on a Friday evening/ notice you standing in the rain by your broken down car/..../

  28. You don't know everything by cprincipe · · Score: 5, Insightful

    Even if you've been doing this for 20 years. If you are working with another technician, have the grace to treat them like an intelligent human being.

    --

    bun-fhuinneog agam!

  29. Just to PO the "Don't post your list here" folks.. by mnemotronic · · Score: 5, Insightful
    Ok, so it's more than 10.

    1. 90% of Windows problems can be solved with a different OS, oops, I mean a reboot.
    2. 5% of the users really know their stuff, and could do your job better than you, but choose not to, because the pay sucks.
    3. Most users, including engineering types who are very intelligent in their own field, know a specific sequence to run the program or programs they normally use. They don't know how to set environment variables, fire up (much less use) a DOS command line, or organize their data in a hierarchical fashion. And, they sure has h*ll don't know how to edit the registry. Don't expect 'em to.
    4. If you don't provide and enforce a directory structure and naming convention on shared/networked drives, users will place every single file and directory at the root.
    5. "MSTSC /console". Don't leave home without it. 50% of the time you can stay home & work in your undies because of it.
    6. Backup servers every night. This'll save your *ss more than once.
    7. When someone is requesting new services or features, learn to ask "What do you really want?". Ask this question a lot. Keep repeating until the requestor finally discovers what he or she reallywants. It won't be obvious to them.
    8. WiFi in the local coffee shop is kewl. That plus VPN is even kewler. But WiFi in the office makes be very nervous.
    9. You never have time to read the magazines you've subscribed to.
    10. The office coffee sucks. Buy a french press & your own coffee. I recommend Ethiopean Yirga Cheff.
    11. You can never have too many bookshelves.
    12. Users will end up going to p0rn web sites. 95% of this is unintentional. The rest you ignore until the user starts whacking off in the office, then you threaten to report them to "human resources" (i.e. the Dept of Political Correctness).
    --
    The Russians have won. They have made the world a cesspool of distrust, greed, fear and hate.
  30. GeekSquad Top Ten? by dada21 · · Score: 5, Insightful

    I have a friend living the GeekSquad life. I'd never hire him as he believes in their process to fix lockups:

    1. It must be this unsupported software: remove Firefox or any F/OSS.

    2. It is a virus, your AV is no good, purchase Norton CoverYourAss v9.6 for $49.95.

    3. The AV doesn't perform a deep clean by itself, we can run one for $24.95.

    4. You need a bigger hard drive, w recommend Norton Ghost to copy it. $199.95 + $49.95.

    5. We should install the drive. $24.95 + $8.95 wrist strap.

    6. We should run ghost for you, $19.95.

    7. You need USB 2.0 ports for your mouse to run faster, $49.95 plus $24.95 installation.

    8. Your hard drive cables are old belt style, you needbthe snappy round cables, $29.95 plus $9.95 installation.

    9. Your video board is old, the ATI MegaWow XL is only $199.95.

    10. You should probably buy one of our Compaq BusinessPro by HP combinations, you burned your TCP/IP converter with static.

    I pop open the discarded PC, replace the processor fan and blow out the case. All is fine - $30.

  31. Schmooze the users by lildogie · · Score: 4, Insightful

    On a 24x7x365 job, I learned the value of walking through the user's work area every weekday morning, first thing.

    They started waiting for me to stroll in instead of paging me at night, just to be nice to me.

    But the best part was, they thought of me as the guy who keeps the system running, because most of the time that I showed up, the system was running.

    My colleagues who only showed up when their systems broke had the reputation "Here comes trouble!"

    Taking credit for things going well is essential!

  32. The Truths of Skippy by EvilTwinSkippy · · Score: 5, Insightful
    1. Fast, Cheap, Right. Pick 2
    2. One must honor the Random Number God with a token offering every morning
    3. Never underestimate the power of imagination, stupidity, or bad luck.
    4. Network equipment's attention span is about as long as it's power cord
    5. Scripting works about as well as the broom from the Sorceror's apprentice: don't let it run unattended.
    6. Your network can be down more often than it's up. If you keep your users in the loop, they will be happy.
    7. Your network can run without fail for months on end, but if a problem happens and they don't hear from you first, you are incompetant.
    8. A User fills out your performance review.
    9. A database is a high performance cache between your backup medium and your application.
    10. Any device that is sufficiently ignored will fail to gain your attention.
    --
    "Learning is not compulsory... neither is survival."
    --Dr.W.Edwards Deming
  33. Diabetic Shock in 3, 2, 1... by 2names · · Score: 4, Funny
    "It gives me the feeling that, if this is what everyone in support puts up with, I can do it too."

    Great. Glad you feel that way. Now, before we all hug, skip, and fling daisies, you need to remember ONE thing:

    THERE ARE NO FEELINGS IN IT. EVER.

    Feelings are reserved for secretaries named Gladys who come crying to you when they accidently delete all the pictures of their grand kids.

    "This article is very comforting."

    You better sack the hell up if you are going to make it in the IT world.

    --
    "I'm just here to regulate funkiness."
    1. Re:Diabetic Shock in 3, 2, 1... by SatanicPuppy · · Score: 4, Interesting

      Cynical but true.

      Do not befriend the users. Do not tell them what is actually going wrong. Never accept blame. Do not rush to complete requests.

      Here are the reasons why:

      If you befriend them, they will cease to be able to do the simplest thing without your help. This is fine if they're hot, but not if they're not.

      If you tell them what is actually wrong, they will get it more wrong when they report it up the line, and you will be blamed for something. Instead tell the users something hugely general that will fit into that comfortable place in their minds.

      If you accept blame, users will view this as a sign of weakness, and assign blame the next time, without waiting for you to volunteer.

      If you rush to complete non-critical, non-it projects, users will use this as a performace benchmark, and you'll be forced to complete all of their projects first to avoid the appearance of slacking off, in the course of this you will have to ignore critical maintenance that can get you in real trouble later.

      --
      ad logicam Claiming a proposition is false because it was presented as the conclusion of a fallacious argument.
  34. 95% of bad GUI design.. by C10H14N2 · · Score: 5, Insightful

    ...is the result of trying to implement 100% of user requests. Sometimes, telling the user "no, you simply can't have that" is the best way to ensure an application isn't horribly poisoned by thousands of totally irrational, non-intuitive crap "features" each piece of which makes sense only to the person who requested it. Worse, such design-by-committee applications are invariably written interface-first, back-end last with no regard to how to actually make the goddamned thing WORK, much less work efficiently.

    I agree, good software should be intuitive, but far better to be proactively engineered to be more intuitive, rather than reactively veneered to feel less unintuitive.

  35. Re:Not too bad by EvilTwinSkippy · · Score: 4, Funny
    No One Ever Got Fired For Buying Microsoft.

    Actually not true. I know the guy, and I fired him myself.

    (We are a Linux/OS X shop today.)

    --
    "Learning is not compulsory... neither is survival."
    --Dr.W.Edwards Deming
  36. Geek aura by CustomDesigned · · Score: 5, Interesting
    Very often, people asking me for technical help have problems that refuse to manifest themselves when I am present. My wife calls this my "aura". It is not just computers. The DVD player doesn't work? As soon as I say, "Let me take a look", those circuits start quaking in their solder boots, and by the time I walk over they have shaped up and start working perfectly - and will keep working for another 6 months at least. But I clean the lens to keep it in a good mood. Refrigerator on the blink? A few comments about it getting old and time for a replacement, and the thing shapes up in a hurry. Of course, cleaning out the blocked air intake helps keep up its morale.

    Seriously, anthropomorphizing machines is a powerful technique. It gives you an approximate but effective mental model of a complex system. "Primitive" cultures are not dumb when they attribute personalities to objects. Our brains are wired to use personality to predict complex behaviour.

    My Mother had no technical skills or knowlege - but she treated the automobile like a pet. She was alert to the tiniest change in sound or vibration of the machine, and very often alerted my Dad to problems long before he was aware of anything. One time, driving across country, my Mom said the right front wheel "didn't sound right". We were cruising along at 70, and everything seemed fine. But she insisted, so my Dad pulled over and checked all the tires. No sign of a problem. He pulled the hub cap off the right front wheel - and noticed that the cotter pin had broken! A few more miles and the wheel would have come off. My Dad panicked, since we didn't have any cotter pins in his repair kit. But my Mom dug in her purse and offered a bobby pin. My Dad didn't want to use it, because it was the wrong kind of metal and would break easily. My Mom said she had more, so he put it in. That bobby pin took us another 5000 miles.

    My Dad does all his own work on his cars - at least he did until he ruined the valves on his Honda Accord a few years ago. Now he lets a mechanic do some stuff for him. I learned to be in tune with machines from my Mom, and learned to fix them from my Dad. When designing file system software back in the '70s, the rhythmic sounds of the disk access mechanism was my best feedback on its efficiency. Those were the days of 14" disk platters.

    1. Re:Geek aura by jimicus · · Score: 4, Funny

      Very often, people asking me for technical help have problems that refuse to manifest themselves when I am present.

      Lots of people in IT find this. Generally, it's because most vaguely complicated electronics is sufficiently sentient to know when it's in the presence of a Higher Power, and that it Must Obey.

      Fortunately, they're not that sentient. I have found an extremely good way to maintain system reliability is to place a photo of myself in the server room.

  37. Have a Knoppix (or other) LiveCD nearby by ishmalius · · Score: 4, Insightful

    I can't stress enough how valuable one of these, or some other good LiveCD, can be. If the box is Windows, Linux, whatever, keep one handy. One of these things can be priceless if the thing refuses to boot properly, someone deleted NTLDR, X locks up on runlevel 5, your driver interrupts conflict, a recursive script uses all of the PIDs, or any number of problems. Keep a printout of the boot options for the disk, too, to boot the unbootable.