Blogging Pubbitch

Sorry. This one's an epic post. What prompted it? Take a look at the last two paragraphs.

I've been in ThoughtWorks for well over a year now, and it looks as if I'm going to be here longer than anywhere else previously. This isn't hard because for a while, my jobs started having a half-life. The first one was a year, the second lasted six months and my third only 3 months before the company folded. In any case, rather than just going "yeah, I like it here" (and I do) it might be more fun to do this slightly differently. I present to you the Ugly, the Bad and the Good about working at ThoughtWorks.

Let's start with the ugly.

Let's face it, right now it's possible to make a stack of cash as an independent IT consultant. In fact, you can make so much money that there's no real way for a company the size of ThoughtWorks to compete. Of course, you trade earning power for security as part of a company, and from where I'm standing I think that ThoughtWorks manages to strike a reasonable balance between the two, but there's no getting away from it: you can earn more elsewhere.

What about travel? ThoughtWorks has offices scattered throughout the world and has a transfer programme in place, allowing people to move from office to office. That's not what I'm talking about. What I'm talking about is the fact that as a consultant the work isn't always where the home is. When you sign up, that's one of the things that is made clear to you, and sometimes the luck runs out. Right now, I'm bang out of luck. Before that? Not doing badly at all, thank you very much partly because my commute to work involved taking a ferry past the Sydney Opera House and the Harbour Bridge.

The other big ugly involves the work. Sometimes there's no getting away from the fact that the work that's available just isn't the most interesting there is. On the plus side, since I'm working as a consultant and being rotated periodically on to new projects there's always the chance that the next leap will be the leap home. Or to a more interesting project. You get the idea.

On to the bad. Or as I like to think of it "the bit that could end up being a career limiting move". Oh well.

ThoughtWorks hires some really bright people. When I was looking for a job, it was the people that were the biggest attraction about the company. After all, the chance to work with some of the best minds in the industry is not something to be sniffed at. Sadly, these are people who are in demand, and sometimes they wander (or are drawn) off to pastures new. Every time one of the people who I look up to leaves the company it makes me stop and think about what I'm doing here.

Currently, EU law allows companies to ask employees to opt-out of the 48 hour working week. One of the key tenants of XP is the concept of "sustainable pace". Originally this was referred to as the "40 hour week". It seems to me that if a company really believes in sustainable pace, even if it's the norm for the country (and in my experience that includes the UK) asking their employees to sign out of the legislation that's meant to protect them from burn-out is an unusual thing to do. Now, I understand that there will be times where I'm just going to have to buckle down and get some work done and I've got no problem voluntarily working more than 40 hours a week, but deliberately trying to skirt around this issue makes me uncomfortable (hey! If anyone from legal wants to explain this a little better to me, then please go ahead and I'll blog about it here)

Enough whining! On to the part of the post that I'm looking forward to; the good parts of being a ThoughtWorker.

As I mentioned before, having the chance to work with other ThoughtWorkers is a huge draw to joining and staying with the company. Some of the established luminaries are obviously interesting to work with, but even the so-called junior people are a pleasure to work with. Catch me in the pub after a few beers, and I'll wax lyrical about how great my current dev team is. All of them. I even like the non-devs for many of the same reasons that make the devs fun to work with: they're smart, vocal, listen when they need to and have an energy that I sometimes notice is missing elsewhere.

If you get a chance, work with a ThoughtWorker. They're great. It should be a slogan somewhere.

The company really is a reflection of its people, and its people seem to want to do the Right Thing, both by each other and by our clients. Whenever I express discontent in some way or other someone somewhere makes the time to listen to me and to try and make things better. There's a whole company of people like that, striving to make it a better place to work. What's not to like about that?

Let me give you an example. On my current project there's a lot of travel and a lot of time away from home. ThoughtWorks realises how little the team like this and have pulled out all the stops. They've fought for (and managed to arrange) a four day working week (long days, though, don't think we got off lightly!) While we're away, they've arranged flats for all of us rather than hotel rooms. The flats are pretty good, and are being equipped with everything a geek needs (aka: broadband)

Indeed, the travel opportunities are something else that's good about ThoughtWorks. We've got offices spread around the globe, in America, the UK, China, India and Australia. I joined the Sydney office originally because we were living out there at the time and thinking about making the move for far longer. In the end, we had to come home, and we decided to do it the long way by taking three months to travel to all the places we'd not seen on our way down. ThoughtWorks agreed to a sabbatical and then a transfer to the UK office.

If we wanted to go travelling again, then it's a simple matter to apply for a transfer to another office. When there's the space on a project somewhere cool and they need me, then ThoughtWorks would make sure that I had a chance to go. The nice thing is, it doesn't matter how long you've been with the company or how senior you think you are, they'll try and make it happen.

I remember a time when a bunch of us were in a pub in Sydney. There was talk of a Ruby project in one of the other offices, and someone had Roy's number on their phone. So, we called the CEO of the company and signed up. What's not to like about a company where the management are so accessible? And so understanding of a bunch of slightly tipsy devs calling them up?

An accessible leadership is only any good if you know what's going on. Fortunately, within ThoughtWorks there's about as high a level of visibility as it's possible to get. You want to know something? Ask. It may already have been posted to one of the internal notice-boards.

What prompted me to write this post? Well, part of it has been the fact that I've not written much about ThoughtWorks and part of it was that I was asked to blog about the fact that we're hiring. Here's the sales pitch: as a geek, I love it here. There are some of the best people that I've ever worked with, all in one place. There are some cool, cutting edge projects too. Stuff for you to sink your teeth into. It's not the perfect place to work, but then nowhere is. We're working hard to make it as close to perfect as possible though, and we'll always need another voice to get us there.

If you think that you'd like to join us, then please sign up either directly or through me. Mention my name in either case. I get a bonus for it, you see....