The problem of "nonglamorous/thankless work" is easily generalizable to other fields; it's not new to the field of programming. (Thus, only a fool would discoun

The problem of "nonglamorous/thankless work" is easily generalizable to other fields; it's not new to the field of programming. (Thus, only a fool would discount this author's thoughts on the basis of her opening with her perspective disclaimer of 'not being a programmer'.) :) As to the problem, though - it's certainly not an easy one to solve, and not made any easier by the general need for QA/expertise to be attracted to that 'thankless job'. I personally believe that better tooling or processing is what's missing from the equation - an expert can (and does!) often try and relay elements of that pseudo-work to colleagues or themselves (in notes), but when it comes time to formalize into documentation, the 'joy' of thinking through the problem is instead replaced with the ardor of 'cleaning up and standardizing' one's thought process to meet a format. On the other hand, process models more readily welcoming of a few 'non-code-monkey monkeys' around to handle the useful-but-overlooked work there might be an answer too.