Reflections on a new job

At the end of my third week in the new job, I’ve come to a couple realizations. Most recent is that I’m having to watch the clock closely so that I leave on time. I’m a contractor, so I’m hourly, not salaried. That means it’s all too easy for me to start putting in overtime at a job I enjoy, and this i just such a job. Problem is, the manager here isn’t allowed to give me overtime without the approval of his higher-ups, and unless something major goes bonkers that approval probably won’t be forthcoming. This sort of bugs me, because I’ve already found myself wanting to stay later and get something finished, but it’s ultimately not that big an issue, I just have to budget my time closely.

I’m also re-discovering why I went in to IT in general – and system administration in particular – in the first place. I’m having a large influence on how things are done already, making people’s lives easier and helping them sleep better at night. At least, I think I am, which is much the same thing as far as my enjoyment of the job is concerned. I’ve also already been given opportunities for input that my former boss would have never given me, and made decisions he would have never approved of simply because he didn’t understand the logic behind them (or was too caught up in having to appear in control of everything to actually let anyone else get any work done).

In future posts, I may detail some of the automation stuff I’m putting into place. It’s not really all that ground-breaking; honestly, it’s somewhat pedestrian and rote, simply because there are so many other places that have done similar things before. Still, it’s all my stuff, customized specifically for my new job, and I take a great deal of pride in the fact that not only did I put it into place, but that it’s been well-received by the admin team here and that it has (so far in it’s limited lifetime) worked quite well. Not flawlessly, but quite well.

I’ve still got a good bit of work to do to add functionality I want to add to what I’ve already put in place, but I’m going to launch by next big initiative next week, addressing a completely different topic than workflow automation. It’s something I see as sorely needed (again) for the future of the environment, but it’s significantly larger and more invasive than the simply installation automation I’ve done so far so I don’t know how well it’s going to fly. I have faith that the people here will see the need for it and the logic behind it, I just don’t know how easy it will be to actually make the necessary changes to put it into place. I’m hopeful.

Wow. That’s something I haven’t been able to say about my job for a long time. It feels really good to be able to say that.

Comments are closed.