Chad Perrin: SOB

24 August 2006

Signs You’re Doing Something Wrong (Part Two)

Filed under: Cognition,Geek — apotheon @ 04:23

About three months ago, I composed Signs You’re Doing Something Wrong (Part One). I promised more. I did not know how long it would take to get there, but I certainly expected it to be sooner than three months.

Here it is, three months (and change) later.

There are, as I pointed out in the previous installment, many programmers out there who simply don’t know they suck. These are some indicators they (we?) can use to help categorize themselves (ourselves?). You may notice that these signs you’re doing something wrong are attitude-oriented, rather than methodology oriented, but the indicators of suck are no more or less transferrable across activity domains. Arbitrary rules are also a sign that you’re doing something wrong when passing laws in the House of Representatives. Superficial productivity metrics are also a sign you’re doing something wrong when firing someone for procrastination. The inability to describe the benefits of your work without euphemising its failings is also a sign you’re doing something wrong if you’re cooking the books to make your multi-thousand-dollar product package look cheap compared to its one-good-dinner-price competitor. By the same token, the following points apply to many realms of endeavor, though I present them in the language of programming.

  1. Bandaging: When you find a bug or a vulnerability, don’t just slap a band-aid on it. I don’t care how busy you are, don’t create a behavioral patch for your software (or legislation, or revolutionary new vacuum cleaner design) and attach it to the standard distribution. Temporary solutions last the longest, when they’re applied directly to the problem. When shipped separately, however, there’s a little bit of breathing room. Take the opportunity to find the source of the problem and fix that instead for general distribution. Slapping a bandage on a nice deep cut may prevent you from bleeding to death, but you really need to get to a hospital and get that looked at by a professional. If you never hunt out the root causes of the problems you encounter, you’ll never be an expert, and if you never fix the root causes of your problems, you’ll only be replacing one problem now with four or five more problems later. The better you get at hunting down root causes and fixing them, the better you’ll be at avoiding problems in the first place later. If you’re using a magic number to solve an arithmetic bug in your program, you’re in for trouble later.
  2. Optimism: You should always, when you’re programming, be asking yourself “What can possibly go wrong?” You should be asking yourself this because you should be planning for every eventuality. This is cynicism, which is not the same as pessimism: as I’m known to say from time to time, a real cynic is an idealist who learns from life experience. Be cynical. Expect the worst but, unlike a pessimist, do not take that as a foregone conclusion of defeat. Instead, take it as foreknowledge of the sort of thing for which you should be planning. Bad, unplanned outcomes are common, and you can best recover from them or even avoid them entirely in many cases by imagining unplanned outcomes and preparing for them. When you’re always “looking at the bright side” and trying to comfort yourself with silver linings, you’re overlooking the potential for things to get worse. Sometimes, they do get worse, and if you’ve overlooked that potential, it will take you by surprise. When that happens, you’re screwed. This is particularly valuable when driving a car in heavy traffic: if you always assume that any random one of the dimwits around you might cut you off without leaving enough room for you to slow down and avoid rear-ending him, you’ll always be able to prepare to the point where you will always be able to avoid rear-ending him. Funny how that works.
  3. Spelling: No, you don’t have to be an excellent speller. On the other hand, you do have to be able to hide your atrocious spelling from others — more specifically, from excellent spellers. Hint: the spell-checker that comes with MS Word will not suffice (for instance, it doesn’t recognize when the wrong homonym is used, only when you add an extra T to the word TTwo). If you don’t care enough to double-check your spelling, you’ll write bad documentation, suffer from a lack of attention to detail, and fail utterly to appear professional to a great many people. More to the point, you’ll betray your contempt for correctness. The worse your spelling is, the more important it is to get it right: expert spellers can tell the difference between an expert speller who overlooked a typo and an atrocious speller who just doesn’t care enough to double-check. That’s the difference that matters — was it an overlooked typo, or are you both ignorant and irresponsible? One might legitimately ask how much attention you’ve paid to the correctness of your code if you never bothered to figure out whether the documentation should read “send an integer to method foo()” or “send an integer too method foo()”. Correctness matters.
  4. Tolerance: It has been very popular for many years to pretend that everyone has something to offer and everyone is valuable. It’s simply not true — at least, not for your purposes, whoever you are, and whatever your purposes might be. Incompetence should not be tolerated. I don’t mean that you should march into your project manager’s office and tell him what kind of useless, washed-up piece of crap he is. What I mean is that when your project manager sucks rocks, you should be polishing up your resume. You should be looking for someone who measures productivity by what your code does, and how well it does it, rather than by how many lines of it you’ve written this week, and when you find that person you should get him or her to hire you immediately. When you’re the project manager, don’t just accept corporate policy written by some idiot predecessor: work to change policy so that it makes sense. Tradition is not a justification for incompetence, and tolerance is not a justification for complacency. If you’re in a counterproductive environment, and you aren’t either looking for a better environment or trying to fix the environment in which you’re working, you are just dead weight. That means you’re doing something wrong.

I know some of this must seem downright heretical. Good. If I was telling you stuff that perfectly fits the “common wisdom”, you wouldn’t be learning anything new. Here’s a bonus sign you’re doing something wrong.

  1. Orthodoxy: If “nobody ever got fired for buying IBM” is the guiding principle of your professional life, you’ll never be anything but a mindless drone. While you may be able to come up with career-saving excuses all the time, you won’t be saving money and time. Nobody ever became great by pursuing a life of perfect averages.

4 Comments

  1. Great Article. Now if we can only get everyone to read it and recognize where they sit. There should be some kind of suck-o-meter that you can send your code through to see who you are.

    Thanks for championing good coding practices.

    Comment by BBSoftware — 24 August 2006 @ 12:46

  2. Thanks for the complimentary comment.

    Feel free to get everyone you know to read it, and help them recognize where they sit. Heh. I don’t mind the traffic and Google ranking, certainly. More to the point, it’s stuff that I tend to think should be disseminated widely, no matter who wrote it.

    Comment by apotheon — 24 August 2006 @ 01:10

  3. […] SOB: Scion Of Backronymics » Signs You’re Doing Something Wrong (Part Two) “a real cynic is an idealist who learns from life experience” “tolerance is not a justification for complacency” “Nobody ever became great by pursuing a life of perfect averages” (tags: programming) […]

    Pingback by links for 2006-08-25 -- Chip’s Quips — 24 August 2006 @ 07:18

  4. […] SOB: Scion Of Backronymics » Signs You’re Doing Something Wrong (Part Two) […]

    Pingback by Labnotes » links for 2006-08-27 — 26 August 2006 @ 10:28

RSS feed for comments on this post.

Sorry, the comment form is closed at this time.

All original content Copyright Chad Perrin: Distributed under the terms of the Open Works License