Warning: there may be some geek speak in this post.
I’ve been in my new job for a little over two months now, and since this blog is about my life as much as it is about my hobbies, I thought it was time to give an update.
I started out enjoying the shorter hours and being able to leave my work at work and have evenings and weekends free. This is the first time I can do that since, well, ever. I feel like I have oodles of time. All the better to indulge said hobbies
In this new job I’m a software developer. This is a big change (and risk) for me as it signalled a move away from research and, as it turns out, science. Yes, I am developing software for scientists but it’s not the same as doing science myself. I must admit I miss the science at times, just not the lifestyle. And I can get my fix with seminars or papers if I choose. Plus there’s plenty of things at work that I understand and can “translate” for the other software developers because of my science background.
In case you’re wondering, this career change isn’t totally left field as I am trained in both. I have two bachelors degrees, one in computer science, the other in biochemistry and molecular biology. Then I pursued the science side all the way to the rabbit hole otherwise known as PhD, then (eventually) out the other side again to a post-doc position which was equally science based and computer (programming) based.
So, back to the new job. A few weeks ago, things at work hit a rocky patch. Rocky enough that I was seriously considering whether I wanted to stay. Which really freaked me out as having made this sideways step in my career, I can’t really step back. Hence the mention of risk, above. I felt like it was being assumed that every piece of code I wrote was wrong before they even looked. My line manager wanted to look at everything I’d done, then get me to change it all, though it was done to the specs he gave me. And the colleague whose project I was working on was rewriting all the code I’d written to do it his way (and breaking it!). What’s worse was I couldn’t see this ending any time soon as I knew the plan was to have me floating from project to project helping to speed up development where needed.
Fast forward a few weeks, and well, that colleague is still pulling that shit – rewriting code that he’d changed, that I’d fixed, back to something that doesn’t work properly – but except for the the odd urge to hit him over the head with something heavy, I’m trying to not let it bother me. My line manager now realises I can do my job and the scrutiny is off. He’s happy that I get things done quickly (tells me he wants something turned into a REST service and two days later he has it) and he’s indicated that I can be assertive in getting fellow developers to get things done. That latter being something I wasn’t sure about since I am, after all, only about two months into this job.
So I can say I’m enjoying my job again and am no longer thinking maybe I should leave. And I’m having good, productive days which make my little type A heart sing. And best of all, on evenings and weekends I can socialise or indulge in my hobbies, or both (like tonight at the local meet and make).
So ends this epic, no photo post. If you’ve made it to here, congrats!
Tomorrow we’ll be back to our scheduled program, with a special event: a finish!
Warning: there are all kinds of finishes, hopefully you won’t be too disappointed with mine