Everything New is Old So, just when I got a new baby, I also got a new job, though I haven't blogged about it yet because I've been kind of busy with Jaime. However, it's really an old job at Lazer, whom I worked for in 1998-1999. I've wanted to go back to working at Lazer for a long time because I've learned to hate big companies and working with too many other people with differing viewpoints. It's nice to be a good team player, but when you're not, then it sucks to try to pretend you are. Trying to work within the framework of what is acceptable/understandable/satisfying to others has been little else but a drag.On the other hand, I originally left Lazer to better learn the craft of programming, and nothing makes it clearer how successful I was at that than to come back here and work with my old code. Ugh! On the one hand, working with others was annoying, but on the other, I was right that I needed to do it to learn. It's a good thing I learned one other thing though, or else this return to Lazer would represent nothing but acceptance of stagnation.I learned how to learn. Most of what I learned I learned via open-source projects and by engaging in conversation with other programmers around the net. And so, coming back to Lazer, I'm armed with the connections and the habits of exposing myself to new ideas on a daily basis - via the internet. I not afraid I'll stagnate here at Lazer - in fact, without having to work under an organization that doesn't share my biases, I'm hopeful I'll progress more quickly. And best of all, I get to do it at a small company I actually enjoy working at. I'm feeling pretty fortunate about how all this has worked out.

So, just when I got a new baby, I also got a new job, though I haven't blogged about it yet because I've been kind of busy with Jaime. However, it's really an old job at Lazer, whom I worked for in 1998-1999. I've wanted to go back to working at Lazer for a long time because I've learned to hate big companies and working with too many other people with differing viewpoints. It's nice to be a good team player, but when you're not, then it sucks to try to pretend you are. Trying to work within the framework of what is acceptable/understandable/satisfying to others has been little else but a drag.

On the other hand, I originally left Lazer to better learn the craft of programming, and nothing makes it clearer how successful I was at that than to come back here and work with my old code. Ugh! On the one hand, working with others was annoying, but on the other, I was right that I needed to do it to learn. It's a good thing I learned one other thing though, or else this return to Lazer would represent nothing but acceptance of stagnation.

I learned how to learn. Most of what I learned I learned via open-source projects and by engaging in conversation with other programmers around the net. And so, coming back to Lazer, I'm armed with the connections and the habits of exposing myself to new ideas on a daily basis - via the internet. I not afraid I'll stagnate here at Lazer - in fact, without having to work under an organization that doesn't share my biases, I'm hopeful I'll progress more quickly. And best of all, I get to do it at a small company I actually enjoy working at.

I'm feeling pretty fortunate about how all this has worked out.