Skip to main content

Not consulting any more. Or am I?

As I've hinted in some earlier blog-posts, I have now moved to Bonn, Germany, and as of last Monday, I'm working as a developer for IP Labs.

This means I won't be a consultant anymore, as I have been for the last 2,5 years. I am now a "fast ansatt", or steady employee. It's a bit interesting to ask myself:
  • Does this mean my rocketeer knowledge increasing career has come to an end?
  • Will I go to work with a much more relaxed attitude, getting used to stable work environments and fewer changes?
  • Will I spend less time overall doing stuff related to my profession?

I hope the answer is to all three question a ringing 'no!'. I really enjoyed being a consultant because it allowed me to do stuff I'm really good at. I'm not a super-programmer, in fact I know lots of programmers who are better than me (well, even more that are worse than me), but I hope I still will be able to contribute lots to the company by doing what I always do: pushing for more agility and sound practices.

So far in my career, I've worked closely with about 5 different teams, from 1 to 10 in size. My role in these projects have either been enforcing soft values (typical agile stuff, like planning, estimation and practices), enforcing hard values (code style, tool-use), or both. This effort has been spent mostly on the individual level, some on the organizational level, and then some on the community level (although not as much as I would've liked).

At IP Labs, I've found that the individual/hard values are already at quite a high level. They (or we, as I should say) are already well-endowed with pride, professionalism and quality, as well as excellent Java coding skills. There are some practices that can easily be introduced to make things a little better, but things are working, and the developers are delivering lots of functionality with steady velocity.

Also on the organizational level, they are focused on developer-satisfaction as well as customer-satisfaction. Already from day one, you feel that your developer needs are being taken care of, getting free choice of laptop and equipment (I'm now the proud owner of a MacBook, which I so far utterly despise, but hope I will learn to love in time). The infrastructure is very developer oriented, and Windows is frowned upon.

There is no crappy Exchange mail server here that forces everyone to use Outlook: It's simply IMAP - use the client you prefer. They don't use Messenger or SameTime with proprietary protocols, they use Jabber instead. Again - use the client you prefer. All in all, one kick-ass place to work :)

Well, back to the ranting. ..

The luxury of not being a consultant is that my voice can be a little louder. No more tip-toeing around, packaging plans into sweet little convincing ideas and planting them in other people, being sure not to make it sound like you're not selling anything, even if you're not selling anything but common sense.The idea is that if you're a steady employee, you can criticize, argue and be taken seriously without too much beating around the bush, subterfuge and convincing.

Or maybe it really isn't that different. As a consultant, you have to be careful not to be to rash, try not to insult anyone, be fair, objective, honest and overall being very very patient. Shouldn't the same rules apply to all software workers? Just a thought...

I think after all my job won't be that different. Maybe I'll get some more elbow-room, but all in all, consulting is perhaps nothing else than being an understanding, careful and humble colleague.
Labels:

Comments

  1. Anonymous12/1/09 04:15

    Hai!

    Whether you'll become a Mac or not, welcome on Father Rhine's most prestigious shores.

    We need to get together over a beer once I've shaken all my viruses, bacteria and assorted diseases.

    ReplyDelete
  2. Anonymous19/1/09 05:51

    This comment has been removed by a blog administrator.

    ReplyDelete

Post a Comment

Popular posts from this blog

Open source CMS evaluations

I have now seen three more or less serious open source CMS reviews. First guy to hit the field was Matt Raible ( 1 2 3 4 ), ending up with Drupal , Joomla , Magnolia , OpenCms and MeshCMS being runner-ups. Then there is OpenAdvantage that tries out a handful ( Drupal , Exponent CMS , Lenya , Mambo , and Silva ), including Plone which they use for their own site (funny/annoying that the entire site has no RSS-feeds, nor is it possible to comment on the articles), following Matt's approach by exluding many CMS that seem not to fit the criteria. It is somewhat strange that OpenAdvantage cuts away Magnolia because it "Requires J2EE server; difficult to install and configure; more of a framework than CMS", and proceed to include Apache Lenya in the full evaluation. Magnolia does not require a J2EE server. It runs on Tomcat just like Lenya does (maybe it's an idea to bundle Magnolia with Jetty to make it seem more lightweight). I'm still sure that OpenAdvant...
6 comments
Read more

Git tools for keeping patches on top of moving upstreams

At work, we maintain patches for some pretty large open source repositories that regularly release new versions, forcing us to update our patches to match. So far, we've been using basic Git operations to transplant our modifications from one major version of the upstream to the next. Every time we make such a transplant, we simply squash together the modifications we made in the previous version, and land it as one big commit into the next version. Those who are used to very stringent keeping of Git history may wrinkle their nose at this, but it is a pragmatic choice. Maintaining modifications on top of the rapidly changing upstream is a lot of work, and so far we haven't had the opportunity to figure out a more clever way to do it. Nor have we really suffered any consequences of not having an easy to read history of our modifications - it's a relatively small amount of patches, after all. With a recent boost in team size, we may have that opportunity. Also the need for be...
1 comment
Read more

The Git Users Mailing List

A year ago or so, I came across the Git-user mailing list (aka. "Git for human beings"). Over the year, I grew a little addicted to helping people out with their Git problems. When the new git-scm.com webpage launched , and the link to the mailing list had disappeared, I was quick to ask them to add it again . I think this mailing list fills an important hole in the Git community between: The Git developer mailing list git@vger.kernel.org  - which I find to be a bit too hard-core and scary for Git newbies. Besides, the Majordomo mailing list system is pretty archaic, and I personally can't stand browsing or searching in the Gmane archives. The IRC channel #git on Freenode, which is a bit out-of-reach for people who never experienced the glory days of IRC. Furthermore, when the channel is busy, it's a big pain to follow any discussion. StackOverflow questions tagged git , these come pretty close, but it's a bit hard to keep an overview of what questio...
Post a Comment
Read more

Git-SVN Mirror without the annoying update-ref

This post is part of  a series on Git and Subversion . To see all the related posts, screencasts and other resources, please  click here .  So no sooner than I had done my git-svn presentation at JavaZone , I got word of a slightly different Git-SVN mirror setup that makes it a bit easier to work with: In short, my old recipe includes an annoying git update-ref step to keep the git-svn remote reference up to date with the central bare git repo. This new recipe avoids this, so we can simply use git svn dcommit   directly. So, longer version, with the details. My original recipe is laid out in five steps: Clone a fresh Git repo from Subversion. This will be our  fetching repo. Set up a  bare repo. Configure pushing from the fetching repo to bare repo In the shoes of a developer, clone the repo Set up an SVN remote in the developer's repo In the new approach, we redefine those last two steps: (See the original post for how to do the fir...
17 comments
Read more

Git Stash Blooper (Could not restore untracked files from stash)

The other day I accidentally did a git stash -a , which means it stashes *everything*, including ignored output files (target, build, classes, etc). Ooooops.. What I meant to do was git stash -u , meaning stash modifications plus untracked new files. Anyhows, I ended up with a big fat stash I couldn't get back out. Each time I tried, I got something like this: .../target/temp/dozer.jar already exists, no checkout .../target/temp/core.jar already exists, no checkout .../target/temp/joda-time.jar already exists, no checkout .../target/foo.war already exists, no checkout Could not restore untracked files from stash No matter how I tried checking out different revisions (like the one where I actually made the stash), or using --force, I got the same error. Now these were one of those "keep cool for a second, there's a git way to fix this"situation. I figured: A stash is basically a commit. If we look at my recent commits using   git log --graph --...
12 comments
Read more