Eschew Obfuscation

My wife has started blogging recently (actually, before I did) and has been spending quite a bit of time on making her blog nice.

Tonight, she asked me if I would like to blog on her blog as well as this one.

One caveat though:

“You have to blog in English.”

As an explanation, she went on to speak of my lack of speaking in English when I’m talking about what I do.

Interestingly enough, I’m struggling to come up with what I think is valuable content for this blog. I can only imagine the drivel that would arrive on my wife’s lovely new space if I have to provide non-technical content.

Wish me luck!

written by halfdime

Tonight I was approached at the end of the day by two folks I’ve been working with quite a bit lately.

They had a fairly urgent request and wanted to make sure that it was handled tonight.

Nothing unusual, right. Our users are constantly in need of some unplanned, “my crotch is on fire” item.

To me, the notable item in the exchange was that the two of them felt it was important enough to get this done that they would come down to our offices to make the request and address any concerns.

I think it’s very important for sysadmins to be approachable. Yes, we say no often, but how we do it can be as important as that we do it. Specifically, in this instance, the two were ready for no but knew that asking would give them an honest assessment at worst and a yes at best.

They were very pleased to get their yes. The fact that they felt that they could talk to me (and my group) is, to me, the major win here.

You see, whether my users like me personally or not, I want them to trust me. I want them to seek my counsel even when they know it may not be what they want to hear.

written by halfdime \\ tags: j

It’s really weird the things I think about while in the shower. This is the result.

Very often when people ask me what I do for a living, they’re confused by the term system administrator. They ask what that means. My responses vary wildly but often I just tell them, “I say no. A lot.”

I wonder if Gene Roddenberry had been a sysadmin if we would have the following:

Sysadmin, the pedantic career.
These are the rantings of your IT Professional.
His continuing mission: To deny your requests.
To seek out new insults and voodoo incantations.
To boldly say no to every request you have.

Don’t get me wrong, a healthy dose of skepticism and the ability to see flaws in logic is really important. I think we sysadmins often take this too far. We ravenously seek opportunities to show our abilities by correcting even the smallest mistakes. We thrive on telling someone that they’re wrong. This makes us seem a pretty negative lot.

Why is that? Don’t we have things to be happy about? How much energy do we waste daily in the pursuit of being right?

Increasingly, we’re told to be customer focussed.

Saying “no” is bad. Instead of, “I’m sorry Dave. I can’t do that.” We’re supposed to say something like, “I’m sorry Dave. I think we can synergize better if we coalesce our asset stream in a more holistic manner.”

There’s not a single pairing of ‘n’ followed by ‘o’ in that sentence. It must be better, right?

I worry about the impact that the negativity has on us as a community and in our personal relationships. We focus on what’s wrong or what could possibly go wrong in any situation. That’s constructive to a point but only if followed up by healthy changes. Perpetually saying, “That’s really broken but I’m not going to fix it” is dysfunction 101.

Going with the, fix me first, principle, I think I’m going to try to be more positive in my daily interactions.

I think I smile more than just about anyone else I know already. Perhaps I am a fool. Easily amused by the simple things in life. Regardless, I hope that smile can lift someone else from the dumps for a second at least.

Maybe I can say no in a non-threatening way that doesn’t involve a 5:1 ratio of buzz words to other words and makes me feel like a car salesman.

Maybe I’ll let it slide when someone makes a mistake and not be aggressively pedantic.

Maybe someone else will too.

written by halfdime \\ tags: j

Dealing daily in the world of IT has its hazards.

One of the most oft visited in my opinion is that of someone taking offense (umbrage, pique) at something communicated. Be it a stanza in an email, a snippet of an overheard conversation or an outright slight directed at someone else, our words can create a minefield for us that often affects our relationships.

If you know me, you know that I’m the last person to be preaching about the need for political correctness. I will leave adjusting your behavior to someone more qualified for correction. I will deal with the thing that’s easiest to change. Your personal perception.

Note the phrase used above was “take offense.” There’s no victim in that sentence. The person “offended” has decided that the intent of the author/speaker was to offend.

We, as the taker of offense, take upon ourselves the indignation and robe of the victim without ever talking to the alleged offender.

This frequently results in making us look the fool.

I don’t know about you, but I’d rather someone call me a flaming prat then to make myself look the fool.

At times, it can be difficult to discern. Especially in a day laden with email and text messages. There’s no body language in an email. Ten people could read the same email and come away with different opinions about what it actually meant, much less whether or not they were actively being offended.

I guess the long and short of this post is this; for the most part, we’re not important enough for people to actively try to offend us. The people who are really going to try are most likely going to be those closest to us and will want to be in your face when they offend you.

Don’t fret. They are out to get you, but you’re likely to see them coming.

written by halfdime \\ tags: people sysadmin