It's My Soap Box
I swear I am surrounded by idiots! It seems that all the young kids with computer science degrees don't' have a clue! Don't get me wrong, they can develop new things but can't seem to fix them when they break. I believe that colleges these days either don't teach problem solving, or they don't have any application to the science of problem solving. If was to invent a class for problem solving, all it would be is actually solving problem, not just talking about the process.
Current case in point. One of the younger developers that I work with had a problem today and, rather than asking where they could find the source to the program in question, they dropped the problem on my desk to solve. Yes, I was the author of the program but, it seem that anyone with programming knowledge could look at the program to figure out what it does and why it was failing in this application. The same program works fine in my application. So I dropped what I was doing and looked through the process only to find that he didn't have the correct setup to support what he was trying to do.
The standard operating procedure around this place seems to be, if it's broken (no matter what it is), bring to me so it can be fixed. This is also true for things that I didn't originally develop.
If it continues I am going to blow a gasket.
I am also in the process of transferring my knowledge to a new team member. We just when through another re-organization and I now report to a different Application Supervisor. He it trying to get our team and his old team to be able to back each other up. The problem I have is that the person he has identified to help back me up doesn't have the skill set required. So not only am I transferring knowledge, I'm teaching the languages also.
Okay, that's enough. On the lighter side of things.
I'm still hoping to have the cabinet ready for finishing by next week. The doors should be done by the weekend (if I can breath in the shop). Then all that's left is the hardware and finishing.
Current case in point. One of the younger developers that I work with had a problem today and, rather than asking where they could find the source to the program in question, they dropped the problem on my desk to solve. Yes, I was the author of the program but, it seem that anyone with programming knowledge could look at the program to figure out what it does and why it was failing in this application. The same program works fine in my application. So I dropped what I was doing and looked through the process only to find that he didn't have the correct setup to support what he was trying to do.
The standard operating procedure around this place seems to be, if it's broken (no matter what it is), bring to me so it can be fixed. This is also true for things that I didn't originally develop.
If it continues I am going to blow a gasket.
I am also in the process of transferring my knowledge to a new team member. We just when through another re-organization and I now report to a different Application Supervisor. He it trying to get our team and his old team to be able to back each other up. The problem I have is that the person he has identified to help back me up doesn't have the skill set required. So not only am I transferring knowledge, I'm teaching the languages also.
Okay, that's enough. On the lighter side of things.
I'm still hoping to have the cabinet ready for finishing by next week. The doors should be done by the weekend (if I can breath in the shop). Then all that's left is the hardware and finishing.
0 Comments:
Post a Comment
<< Home