Wednesday, March 2, 2011

If You Write It, Nobody Will Read It

I realized my complete insignificance at my job today.  My team was meeting to discuss the tasks that were left to do.  The project leader made a comment that he felt that a lot of the requirements were being missed in the code, mostly because he didn't think the programmers were reading my requirements documents.  So, he point blank asked them, starting with the fact that he was guilty of not always reading them.  One of them said that she tried, but sometimes she got too busy and didn't always make it back to the documents.  The other one said that he didn't read the documents, nor did he have any intention of reading them.  At least he was honest, I guess, but it still hurt.

No intention of reading them.  I guess they provide no practical benefit to him.  I guess outlining exactly what the system should do, the steps describing exactly how it should do it, and pseudocode to further show how it should be accomplished is useless.  Then again, that's probably why I write up more defects on his code than anybody else's.  His stuff doesn't work as expected.  There's stuff missing.  But who cares?  It doesn't matter what the client wants.  It doesn't matter that missing requirements puts the company into risk of liability.  It doesn't matter that the users of the system will lose money in their accounts, because he decided that he wanted to do this calculation before that one.

My favorite part is when I write up a defect, and he blames me for it.  Says that I didn't document it correctly in the requirements document.  How would he know?