So, I'm strongly considering getting back into doing something software-related in my free time. I've done zero programming since I switched to apps engineer last year, and with the economy tanking, I think it might be a good idea to get something recent onto the resume.
There's a perfect opportunity to do a project for work, which relates to issuing and tracking licenses. My boss more than once has asked me to do something on that. The problem is that with my other responsibilities, and being part-time, the time just isn't there.
One thing I really want to do is modify the program to put a check on the MAC addresses. That's the only part I can't check against the product because it differs by PC. I had left a right quote out of the last one in a list the other day, and so the license didn't work and we had to resend it. And of course, my boss was quizzing me as to what happened and chided me over email that we had to stop making so many mistakes. Actually, there have only been 3 since Feb 11, all mac addresses, two by the offshore resource, and there's been a lot issued, but the perception is out there now.
You'd think he'd be happy that just this week I turned an image around in a few days that looked like it was going to be months (with a lot of pressure from a customer), found the solution to a remote access issue the device software was having (which is a critical issue for an image we want to sell to a customer), and just yesterday during an emergency conference call had them successfully installing, testing and activating an image I created last November *during the call*. Not to mention saying I had already completed another image they were asking about. Although that call was after the boss chided me on the "too many errors".
The whole license thing is way out of proportion, as problems are easily fixed and have nothing like the gravity of getting these images right. But it just happens because when there is a mistake, it goes out on a huge list and everyone sees it. Fortunately, they gave me access to an offshore resource to help out, and she is a literal godsend. Although she did screw up a couple of them recently, which is why the boss is saying there are "too many" errors, along with the one I made.
But that is another good reason to create a database to track licenses. So I can have numbers saying "so many licenses were issued, and this is the number of resends".
The problem is, I'm going to have to do it for free, because my part-time job is averaging over 30 hours and there is no way I'm going to get that amount of programming done without it being more than 40 hours.
But the benefits are
1) I will be getting recent experience
2) I will have a focus for my free time
3) I'll be able to cut down the errors on issuing the licenses
4) I'll be able to come back with some numbers when accused of having "too many errors".
I feel kind of resentful, but at one point there really were too many errors, so in a way, I brought it on myself. Also, l like working with software, so it's a kind of hobby anyway. We'll see.