This is a story about a demanding job...

I can't divulge the details, but I've spent the last couple of days spread very thin, working for two teams at the organisation who I currently do consultancy for. One important deadline looms large, while a major issue caused me to get involved in something which I haven't touched for nearly two months - I was roped in because, as it turned out, not only do I know the most about a particular part of the system, but unfortunately it looks like I cocked something up during the exhausted time just after I moved house.

I'm not sure if everything is going to come together at the last minute. I certainly hadn't bargained on having to spend two full days wrestling with something which has come back to bite my ass, having lain dormant for the best part of two months. I was feeling in a pretty strong position to finish off a whole load of good work and get it delivered before the upcoming long weekend. Now, all my contingency time has been used up and things will be a lot more of a rush, but it shouldn't be a problem.

All the pieces of a very complicated system are connected together to create the product(s) which I'm responsible for helping the organisation I'm working with, to develop and support. I try to change things and make them better. I try to make things more simple, elegant, efficient and performant. I try to make things as simple and easy to understand as possible. Most of the time it works just how I wanted it to, but sometimes - when I have to hack at something somebody else produced - things go wrong. In this case, things have gone with very severe consequences.

I'm not sure whether I'm going to have damaged my reputation by being the origin of a major problem, or maintained my reputation because of my extensive involvement in resolving such a complex problem, but we'll have to wait and see.

I'm certainly not bored.

Tags: #career #computing #boredom