You suck
There’s a childish thing bloggers do. They get angry about something that pisses them off, and they vent. They know, deep in their hearts, that whining about stuff when they could be out there making positive change is not constructive. And they especially know that
lashing out in public is not constructive criticism, it’s just throwing a digital temper tantrum.
But the primitive, reptilian part of their brain—the one that was in charge when they were two years old—takes control of the keyboard and off they go. After a few paragraphs of pointing out how arrogant Apple has become, or how much Vista sucks
tbng qvpx, they calm down and realize how childish the post is.
But do they round file their post? No, in a fit of hubris they try to dress it up in serious clothing by inserting a few absolutely ridiculous suggestions like “
Use one field for entering a name,” or “
Apple should license PlaysForSure.”
That way, they can pass their rant off as some kind of wise observation from someone who “gets it.” Well, I’m a dad with a two-year old, and believe me, I get the point of these posts. It’s just plain people pissed providing a paucity of pertinent points. They’re mad as hell, but you and I both know that they
are going to take it some more.
None of this, of course, stops me from doing exactly the same thing. But a little self-awareness goes a long way: I’m not going to waste your time pretending to be a nice guy trying to help someone correct their mistakes, or suggest that I’m a smart guy who knows better, or even that I’m trying to share some knowledge with you so that you can be a better programmer.
Nope. This is just a rant. Unadulterated bile.
You suckYou suck. Yes, you, Mister Web Application Engineer or whatever puffery is printed on your business card in lieu of “Whipping Boy.” If I was in a good mood, I might say that you’re a fine human being, and it’s just your work that sucks. And that you can’t help it, there are deadlines and bad managers and clients who buy lemons and all sorts of excuse for the crap you ship. But I’m not in a good mood.
I’m not in a good mood because I should be in New York right now. Do you know why I’m not in New York right now? Because the company you work for—a travel agency—didn’t email me my e-ticket in time for me to get on my flight. Why not? Well, it seems I made the mistake of giving you a valid but unusual email address,
invective+travel@gmail.com
, and your software did something stupid.
Now, we both know that
it is very hard to validate email addresses properly. Had you thought it was invalid and not let me enter it on the web in the first place, you would still suck, but I would be telling you that you suck from NYC. But instead, you let me enter it. You even sent a confirmation email telling me that you were processing my order to that email address! But I guess you have different systems, with different logic, and the system that was supposed to actually send my e-ticket mangled things and emailed it to
invectivetravel@gmail.com
instead. No
+
. So nobody even knew anything was amiss! No error, nothing, just sending it to the wrong place. And it probably bounced, but you didn’t tell any of your customer service people, so nobody knew there was a problem until it was too late.
Well, my situation sucks, but at least I don’t suck. You do. This email mangling isn’t a bug. It’s a place where you thought you knew what a valid email was, and you added
extra code to block “invalid” characters. Had you simply schlepped strings around like they did in the days of COBOL, all would be well. But that wasn’t good enough for you, you had to actually burn your employer’s money making your software worse.
I’ve seen your work before. My legal surname for many years was “Braithwaite-Lee.” Note the hyphen. In your infinite wisdom, you have built many web systems that told me that “-” is an illegal character in a name field. You are an idiot, what makes you think you know anything at all about what kinds of characters people are going to want to put in their names?
A name is the most personal thing people are going to give you, and here you are “validating” it. I would point out the irony of a medium invented by
Tim Berners-Lee rejecting surnames with hyphens, but I know for a fact you just got the job because you aren’t qualified to do anything else, so you have no knowledge whatsoever of our industry’s history.
I find this “validation” especially irritating when ordering something online and trying to pay with my credit card. What excuse, other than the fact that you suck, can you give for telling me that the name “REGINALD BRAITHWAITE-LEE” was an invalid credit card name,
when that’s exactly what was printed on my credit card? I mean, besides the fact that you’re wrong, why were you trying to guess that someone else’s computer accepts or rejects? Just ask them, oaf. The bank will tell you if the name is invalid.
This is a basic tenet of your suckage. You are not lazy in any enlightened, useful way: you make work for yourself under the guise of making things easier or of strutting around your office bragging about the latest shiny enterprise bauble. Most of the problems you have to solve arose because you made choices that suck.
Your credit card name validation sucks. Why? because it tries to save a round trip to the bank when a customer mis-types what is written on their own credit card. Does it always do so? No, of course not, I can merrily put my name down as “STUPID OAF,” and you don’t care. Your little check just takes care of one corner case, gets it wrong, and encumbers your code with broken dreck, just like the email crapfest.
And that’s why you suck.