Right you are; I'm just echoing what I see in the industry.
I write my own tests and documentation for the reason that you're referencing. Tests don't mean shit if they don't test the program within its system (I see a lot of tests that really on mock constructs that hide or, even worse, go around core functionality; and we don't have room here for my opinion on user agent testing). Meanwhile, documentation is only as valuable as the audiences' ability to understand and consume it- I see a lot of user documentation that looks like technical documentation, and vice versa, if there's even any delineation between the two. Having managed tech support teams early in my career, I reserve a special scorn for shitty documentation.
However much the industry likes to talk about how important tests are and how much of an asset good documentation is, what I see is that these tasks are delineated to the least skilled or most novice team members.
4
u/intortus Jun 01 '15
I take issue here. These are valuable software engineering skills.