Best of Times, Worst of Times

January 1st, 2010 — 2:01am

The past 10 years has had it’s ups and downs. Big ups and really bad kick you in the balls downs.

All three of my kids came in the last ten years.

I got three nephews.

One of my nephews has Down Syndrome.

One of my nephews is terminally ill.

My Dad passed.

When I think back to the memories of the last ten years I overwhelmingly have thoughts of joy. But I also have thoughts – small nipple tweaking thoughts – of regret. It seems as though the older I get the stronger and harder the experiences become. Sucks getting old.

The only thing powerful enough to prop me up and keep me going is the love of my wife and kids. I have 4 little ladies that love me and I’m damn fortunate for that.

I hope that the last 10 years has at least made me smarter. Smart enough to know to pay attention to the next 10. Time is fast. And no one has figured out how to slow it down.

It will always be the best of times. It will always be the worst of times.

Comment » | Life

Us vs. Them – A story of bad leadership

December 17th, 2009 — 3:47am

Today at work a situation occurred that had it happened to me, you might understand my current frustration. However it happened to a co-worker and it still has me miffed.

It all starts with an email. A poorly worded, extremely divisive and classless email.

There are projects that have all kinds of moving parts. Many different teams working together to make it all happen. There are technical project managers, engineers like me and others all delivering small components that get mashed together to deliver a solution.

An obvious and usually all-important feature of these projects is the timeline. When will it be done? At the beginning of a project you “roughly” outline the time you think it will take to develop, test and deploy the given project. Then everyone involved agrees to some form of that timeline. A second but often overlooked and underestimated feature of projects are the technology choices to fulfill the solution. These technology choices in a large way dictate the timeline.

So this is what happened.

We deployed a project to QA. This means that for the most part the development is done. We are now testing it to make sure it’s all good before it goes public. We (I say “we” because I feel we’re a team, and this is part of my point) then get emails from another team regarding technology choices made. Something to the effect of “I thought we were going to use something different?”

Now this kind of interaction is not atypical. In fact it happens all the time. Well in this case we reply with “well we finalized on this technology, however if you want something else we can discuss it and how it will affect the timeline”. This is the key. When you make changes post development, it costs time. The response we made was tactful and prudent. Simply put we can change whatever you want, but it’s going to take time and the original agreed upon timeline will change. Full Stop.

This is where the story turns and the Us vs. Them part comes in. The response we got from a manager of the other team was as I see it rude and frankly offensive. It went something to the affect of “don’t threaten us with timelines” and “be a team player and try to fix this”. If I were to describe the person who this email was addressed to I would use words like “team player” and “go-to guy”. This guy has single handedly managed all of the projects I have been a part of as well as everyone else around me. And he develops a little bit himself. And he manages all the outside administration. He does it all. And with a smile.

The managers email made me recoil. I stood up and said “where does he get the balls to talk to you like that?”. This person – the one who the email was addressed to – said nothing. He smiled at me and shrugged his shoulders.

I was fit to be tied. Who is this guy to imply that my guy wasn’t a team player? And where does he think we’re threatening him with timelines? It seemed to me a total over-reaction and a terrible, terrible way to respond to a otherwise innocuous email.

I hesitated to respond with my own smart ass remark such as “you stay classy”. Even worse I thought to storm down there and tell this guy how off base he was and ask him if had a fucking clue what he was talking about.

But I didn’t. I didn’t because my guy didn’t. It was his business to take care of so I kept my mouth shut.

Here is the big point I’m trying to make.

Leaders (managers like this one) need to realize that all of their communication, spoken or written, need to be worded in a way to avoid causing division. In this example there was an immediate schism. Now we have to work with this manager to deliver a solution and honestly I will always think he’s an ass because of this. Without ever having really met him my mind is made up that he is complete and utter douche. I’m a professional and will never ambush my team with some form of sabotage. But I will continue to hold this manager in a cross-hair.

Communication is hard. It’s especially hard when it’s in email. There’s no body language or inflection that would help you to understand the attitude the writer has when they wrote it. Maybe this manager was joking. Maybe he was giving my guy a sharp reminder. Regardless of his intentions, his words communicated offensive division. I tend to believe in Hanlon’s Razor: never attribute to malice that which can be adequately explained by stupidity.

I tend to respect authority (barely). But I go cold with animosity when authority is stupid.

Us vs. Them.

Comment » | Work

The future of my kind of work

November 20th, 2009 — 1:30am

Today Google announced its release of the source code for the Chrome OS. That is their version of a computer operating system that revolves around the web browser.

I have mixed feelings about this from a user perspective. From a technical perspective I’m totally buzzed about it.

For family and friends reading this (all 5 of you) this plays really well to explain what it is “I do for money”. See in the video when they are talking about the software you use (Gmail, YouTube, Searching etc), well that is the kind of software I build. Web based software. Presumptuously this would would mean that in a world where computers only run software from the internet – I have a lot of opportunity.

But I have a concern as a user. Frankly I like things the way they are. I want to store data on my machine. I want local (native) applications. But then again, I’m rather techy and maybe there’s context about all of that. When I think of my Mother using her computer, I don’t think of anything local. It’s email, browsing and that’s really it. So this kind of thing would be perfect for her.

So while I’m totally digging the idea and I’ll be paying really close attention, I have this underlying suspicion that it won’t be “applicable” for a while yet.

Maybe I’m wrong.

Comment » | Code, Work

Back to top