January 16th, 2007Sitting Idle
Shortly after becoming involved with computers, I started wondering why people would let such wonderful data processing machines sit idle for most of the day. There is always so much work being recruited by distributed computing projects, and considering the amount of raw power that goes to waste every day, I’m surprised that large vendors such as Microsoft and some Linux variants don’t include some built-in software that makes use of the extra clock cycles. Just think of how far SETI@Home or Folding@Home would be if the userbase was increased by a factor or two!
I mention this because, like the idle computers that are online 24 hours a day with very little to occupy themselves, I have nothing to seriously occupy myself with at work. Since the middle of 2006, it seems as though I’ve been cut lose to accomplish very simple tasks, but not be a part of any enjoyable solutions.
I am a solutions provider by nature. When somebody has a technical or process problem, I think of ways to solve the problem. If I can use technology, then I’m in my element. If it’s a very complex problem that needs technology, then I am really in my element. Not being able to flex these mental muscles leaves me very unfulfilled and this seems to follow me home….
The last major project that I had at work was finished in the early fall of last year. Since that time, I have tried to occupy myself with side projects and minor maintenance issues reported by users. The maintenance I can understand. This is a regular part of dealing with software. Things break or processes change, so software needs to be updated from time to time. The side projects that I do at work are typically done to both keep myself happy, and to provide value to my co-workers. Unfortunately, these are usually cancelled long before they even get off the ground.
Since last summer I have felt as though my efforts are largely ignored. I know that I was a bit pre-mature telling my employer that I would be leaving an entire year in advance, but given the complexity of the proprietary enterprise software, I would have figured that a new programmer would need at least six months to get the ropes before I would leave. So far there have been no mention of a possible new employee, and any new work that needs to be done goes to the my already-over-worked teammate. Unless I’m the only person in the office during an emergency, I barely seem to exist.
I wonder if I could work on an as-needed basis. They could call me a day or two in advance, and I would show up for given days. Because I would already know the data and software inside and out, there would be no waiting time for me to provide a solution (unless it’s a nice, big project). This would give me the opportunity to find other work during the day and perhaps move towards an alternate career path.
Or perhaps I should just cut my losses and move on.














































