Pragmatic IT

IT Infrastructure and Software Development from the Customer's Perspective

Finding More Women for IT

Martin Fowler recently published a great blog post on how to get more gender diversity in IT. You need to read his post to understand this one, but in a nutshell he makes an analogy to a bag of marbles. 80 % are blue and 20 % are pink. 10 % of each colour are sparkly. As long as you have 100 marbles, you can find 2 sparkly ones of either colour. You just have to look for them.

When I read his post, I thought, “what about the marbles outside the bag.” In the universe of marbles, 50 % are blue and 50 % are pink. 10 % of each colour are sparkly. So if you step outside the bag (e.g. the resumes you received for a job posting), the probability of finding a sparkly pink marble is actually greater than that of finding a blue one.

Using Plantronics M165 Marque 2 Bluetooth Headset with Linux

The Plantronics M165 Marque 2 Bluetooth headset paired very nicely with my Android phone. To pair it to my computer running Linux Mint 17 I:

IT Lottery

So today I had to participate in one of the many little rituals of an enterprise IT project manager: Get someone signed up to my project time charge code.

I submitted the usual paperwork like I’ve done a number of times before, but this time I was told that the role I selected wasn’t a role in the timesheet software, and neither was the individual’s official job title. The individual is an employee of the client’s company.

I felt somewhat smug that I was able to completely ignore the absurdity that an employee’s job title isn’t acceptable to the company’s timesheet software. But then I realized what I was being asked to do: I had been told two titles that weren’t acceptable to the timesheet system, but I had not been told what would be acceptable. I guess I’m supposed to randomly guess until I get the right answer.

Definitely a Dilbert moment. But then I asked myself, “Why would someone respond to me this way?” The person I was dealing with is a very nice, dedicated worker. They weren’t just trying to make my life difficult.

I think it’s because, in the enterprise IT world, there’s no upside to providing service. An IT manager has too many demands, and not enough people to meet the demands. In addition, the path to promotion for the manager is through more responsibility, and the way to get that is by having more staff and a bigger budget. If you provide good service for the same personnel level, you’re not meeting your boss’s needs.

Also, there’s no upside to taking responsibility. If you take responsibility, you can be blamed if, sometimes, you don’t achieve the desired result. Better to leave all decisions up to someone else, and don’t give them any help, in case they blame you if your help turns out not to be helpful.

This culture so permeates our business that it’s not absurd to just tell someone, “You got it wrong,” without giving so much as a hint as to what the right answer might be.

No wonder people have such low expectations of IT.

Relocating Another Data Centre

I recently took part in another data centre relocation project. I was one of a number of project managers moving some of the servers in a 1,300 server data centre. I moved about 200, and decommissioned another

  1. I was directly planning and executing moves, so my role was different from on my previous project. It was good to experience a move from another position.

The project was successful in the end. I have to say that there were a number of lessons learned, which goes to prove that no many how many times you do something, there’s always something more to learn.

Unlike my previous experiences, there were three major organizations working together on this relocation: the customer and two IT service providers to the customer. All organizations had good, dedicated, capable people, but we all had, at a minimum, a couple of reporting paths. That in itself was enough to add complication and effort to the project.

The senior project manager identified this right from the start and he made lots of good tries to compensate and mitigate for it. We did a number of sessions to get everyone on the same page with respect to methodology. Our core team acted as a cohesive team and we all adhered to the methodology. And in fact, across the project I think it’s safe to say that the front line people did as much as they could to push toward to project goals.

Despite our best efforts, we all, across the three organizations, had to devote significant efforts to satisfy our own organization’s needs. It’s worth noting that much of this is simply necessary – organizational governance is a big issue in the modern economy, and appearing to have management control is an business reality.

So if you’re planning a relocation, take a look at the organizational structures that will be involved, and take them into account when planning your data centre relocation project.

Time Zone in Rails

There’s pretty good info out there about using time zones in Rails, and Rails itself does a lot of the heavy lifting. The Railscast pretty much covers it. It’s only missing a discussion of using Javascript to figure out the client browser’s time zone.