Saw an interesting blog post from someone in a new job unsure how to react to a developer's comments
. I'm curious to see how other people respond to the situation he presents. There are three comments so far, all with quite different approaches.
Perhaps because I've recently accepted a new job offer myself, I found myself focusing on the "new job" aspect of his post, more than the "defend your work to a developer" part. I'm thinking about how I'll deal with being the New Kid next month (and also the first tester on board), and thinking back to when I joined my current organisation.
My reply was that I'd go around for a chat with the developer. I'm going to end up working with this programmer during my time here. Time to introduce myself. What I didn't expand on in my comment, was that if I was new to the organisation, as well as meeting a new colleague, this is also a great opportunity to learn more about the company: how does this company work? How do people work together? Are there any longstanding difficulties between departments/individuals that I might want to be aware of, so that I understand why people seem to be reacting a little strangely to innocuous comments I make? How do you get things done? I'll be listening and watching very carefully for any clues to how the organisation tends to work in practice. I'd probably follow up by chatting to my boss, and colleagues.
It occurred to me though that this is very much a Big Company assumption - in a smaller company, or in one that was organised differently, I'd probably already have met the guy. Makes me wonder what other Big Company assumptions I might be making.
So - last time you joined a new company, how did you deal with being the New Kid? What do you look out for? Was it a big company, or a small company? When you say big/small, what does that mean to you?