mainframes and sex
Sep. 24th, 2010 11:17 pmMaybe it is insanity.
I mean, I am the only person in our team who has any mainframe-based skills and what did I suggest to my manager today? I proposed converting our last remaining mainframe-based process into a unix one like everything else our team owns. Basically I am making one of my skills obsolete. On the other hand, it’s not as if they keep me onboard because of that unique knowledge. The last time I had to do maintenance to that process – which I created 15 years ago – was in June 2007. That thing never breaks – as is usually the case with my work – and I seldom use those skills except twice a year, when all mainframe-based processes must prove that, should something happen to the Big Machine, they could switch to a backup. Like sex, those exercises involve a lot of preparation then “Boom!” it’s quickly over, but without the fun that usually ends the Other Activity. This process will be shut down some time in 2012, possibly after the End of the World. Why then bother? Why not leave things as they are for the next 2 years?
I’m bored.
I look back upon 2010 and most of what I did was to provide support to the contractors working on our merger, or keeping the system alive, or transferring most of our unix-based processes to new servers in another data center. I am quite good at working in the engine room.
In other words, I have done very little creative work.
And there will be a lot of that here. The conversion doesn't mean keeping the existing logic as is while translating one computer language into another. I will instead translate the logic itself to take advantage of a different technology.
I mean, I am the only person in our team who has any mainframe-based skills and what did I suggest to my manager today? I proposed converting our last remaining mainframe-based process into a unix one like everything else our team owns. Basically I am making one of my skills obsolete. On the other hand, it’s not as if they keep me onboard because of that unique knowledge. The last time I had to do maintenance to that process – which I created 15 years ago – was in June 2007. That thing never breaks – as is usually the case with my work – and I seldom use those skills except twice a year, when all mainframe-based processes must prove that, should something happen to the Big Machine, they could switch to a backup. Like sex, those exercises involve a lot of preparation then “Boom!” it’s quickly over, but without the fun that usually ends the Other Activity. This process will be shut down some time in 2012, possibly after the End of the World. Why then bother? Why not leave things as they are for the next 2 years?
I’m bored.
I look back upon 2010 and most of what I did was to provide support to the contractors working on our merger, or keeping the system alive, or transferring most of our unix-based processes to new servers in another data center. I am quite good at working in the engine room.
In other words, I have done very little creative work.
And there will be a lot of that here. The conversion doesn't mean keeping the existing logic as is while translating one computer language into another. I will instead translate the logic itself to take advantage of a different technology.
no subject
Date: Sep. 25th, 2010 06:43 am (UTC)No? Oh, good... ;-)
no subject
Date: Sep. 25th, 2010 09:36 am (UTC)no subject
Date: Sep. 25th, 2010 12:40 pm (UTC)no subject
Date: Sep. 25th, 2010 08:32 pm (UTC)no subject
Date: Sep. 25th, 2010 12:41 pm (UTC)no subject
Date: Sep. 25th, 2010 06:56 am (UTC)So, are you any good at cryptic crosswords?
no subject
Date: Sep. 25th, 2010 01:22 pm (UTC)no subject
Date: Sep. 25th, 2010 08:33 pm (UTC)And we all know how you feel about the creation of awful puns.
no subject
Date: Sep. 25th, 2010 10:18 pm (UTC)no subject
Date: Sep. 27th, 2010 02:50 pm (UTC)no subject
Date: Sep. 25th, 2010 08:14 am (UTC)I mean, I suppose it keeps people like me in business, but ow.
no subject
Date: Sep. 25th, 2010 01:19 pm (UTC)One year ago, my boss's boss passed on to my boss that we should not have processes across different platforms. His concern was that there was one piece of what we do involved technology that only one person knew how to handle, and should that person be hit by a bus, they would be in trouble. That's not what he actually said, but... I pointed out to my boss that the mainframe platform was very stable, but stability was not their prime concern. Again, that's not what he said, but... I could see that there was no point in arguing. We had two mainframe-based things remaining and one of them was originally going to be shut down a few months from now instead of late in 2012 so we left it alone. I converted the other process. It was kind of neat to do actually, especially in the middle of all the non-creative work I was doing. That conversion turned out to be a good thing because, when the merger hit, it made some of the necesssary changes very easy. The mainframe is very stable, but defines things very rigidly. Of course, the unix version is very stable too because, well, that's what I do (says he humbly).
no subject
Date: Sep. 25th, 2010 01:41 pm (UTC)no subject
Date: Sep. 25th, 2010 10:21 pm (UTC)no subject
Date: Sep. 25th, 2010 10:39 pm (UTC)no subject
Date: Sep. 25th, 2010 10:50 pm (UTC)People come to you anyway because You Know Stuff. And because you won't treat them like idiots. And because - dare I say it - you're too reliable.