Thomas Ferris Nicolaisen's blog

So! As I blogged about previously , I've begun working at a new company right after New Year's. I figured I'd get some thoughts out on how the first month has been. Usually, when someone begins in a new job they're excited, nervous and above all very humble towards the existing practices that exist in the new workplace. Of course, I had these feelings, but being an agile fanatic, I was pretty sure that I would be able to find some improvement points. Here are some of the specific steps I took during my first weeks. Step 0: Start writing a diary I don't think an honest worker was ever harmed by being transparent in his work. A practice I've been doing ever since I started working is The Diary . Basically, just a personal wiki-page where you note down a few lines each day on what you're working on. Apart from being a good way to keep focus throughout the day and being a nice place to paste notes and code, it sends out a message: that you're interested in

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 agi