1686: Sunday Night

Back to work tomorrow, and after a rather gentle start last week I’m actually hoping I’ll be able to get stuck in and make myself useful a bit more this week. I have a full-day company induction on Tuesday, I believe, but all being well the remainder of the week will see me actually doing my job, which will be nice.

Yes, that’s right, I said “nice”. I know in modern life it’s fashionable to be cynical about your job and to merely tolerate it rather than enjoy it, but for the moment I’m actually relishing the prospect of having something to do each day — and that something being part of something bigger.

I’ve had this to a lesser extent when working on websites, of course, but when working remotely from a different timezone to the rest of your colleagues, it’s easy to feel somewhat justifiably isolated at times. The advantage of what is effectively working “solo” alongside a bunch of other people who are also working “solo” on the same thing is that you can turn things around pretty quickly — more often than not, I’d have an idea for a feature on a website and be able to research, write and publish it within a space of a day. (Obviously things that require longer to research — by playing a whole game through for a review or walkthrough, for example — take a bit longer, but these can be worked on alongside other things.)

The downside of this I’ve already mentioned: you feel like you’re kind of going it alone, even when the people you work with make an effort to get together online in some form or another and swap ideas.

Conversely, having switched work environments from working solo at home to part of a team in a big office, I’ve noticed two things related to the shift: firstly, things take a whole lot longer than if I was doing everything myself as in the past, and secondly, you’re a lot more reliant on other people.

These things are a mixed blessing at best; it can be frustrating to be waiting on an important piece of information from a specific person and they simply don’t get back to you for weeks at a time. On the other hand, it means that things are — theoretically, anyway — a whole lot less stressful, since the workload of getting something done is spread between several people, each of whom can concentrate on their own specialisms rather than having to dip their toes into unfamiliar waters on occasion. It also kind of means you can work on a lot more things at the same time — do your bit, pass it on to the relevant person or people, then get started on something else, only returning to the original thing if you have to go back and fix something.

None of this is news to any of you who have been happily chugging along in office jobs for years now, I’m sure, but this is still quite a new experience to me. Those who have known me a while will remember that my past lives have included being a teacher, a salesman, a software trainer and a video games journalist — all jobs that tend to involve you dealing with things by yourself, whether or not you’re part of an overall “team”. It’s actually kind of nice to know that now, for the first time, I can share out some of the responsibilities a bit more as well as helping other people out when I can. I foresee it being a much more pleasant way to work — let’s just hope I keep feeling that way after the initial “honeymoon period” is over!

Anyway. In line with my new responsibilities as a cog in the corporate machine, it is time for me to disappear in a bedwards direction. I hope you have a pleasant week.


Discover more from I'm Not Doctor Who

Subscribe to get the latest posts sent to your email.