Tuesday, April 10, 2012

I Haven't Been Trained On That (or a mild work rant...)

For years at a previous job, where over time I'd written a lot of code for a number of modules of our software, including creating whole modules by myself, one of my favorite jokes was when someone would come to my desk to ask me how a particular part of the software worked, especially if I knew the querent knew I wrote that part, I'd answer "don't ask me, I haven't gotten training on it yet."

I was just trying to be a little funny, and even if I said it with a straight face, I still didn't let them leave my desk without giving an answer to their actual question.  Whether it was funny or not is not my current point...

Unfortunately at my current job, that is the actual answer I get to a lot of my queries of other developers who've been working on the software far longer than I have.  The developers who wrote parts of the software tell me things like "I know I wrote it, but I don't remember how it works, you'll have to figure it out on your own."

For the last few months I've had one task on my plate that has me sort of whipped...  But I can't get any instructions on how to set up the test data to duplicate the problem so I can come up with a solution.  The answer I get from the developers who've worked on it is "talk to So-and-So" and when I talk to that person, "I don't remember, read the source code."

And it's not like I remember every detail about all the code I've written, and when people have asked me questions about my code, I haven't always been able to give an immediate answer.  I've resorted to "let me review and do a little research, and I'll get back to," but currently I don't really get that, I just get a "I don't know, you're on your own," sort of answer.

No comments:

Post a Comment