3 ms·
The only work I consider 'dirty' work is work that doesn't help the final product. User documentation, support documentation, test plans, etc... all help the f
by matwood 13y ago
The only work I consider 'dirty' work is work that doesn't help the final product. User documentation, support documentation, test plans, etc... all help the final product. I actually enjoy doing them as part of the process and as a break from heads down coding.
The only work that I genuinely consider dirty work is useless work. Things like status reports or faux process fall into the useless category.
- mathattack 13y agoYou may be the exception. I have yet to see a software shop where the documentation and test cases were all current. You never know when status reporting can help... If done right. If 20 teams who each impact the final deadline all are 90% of the time on time, you'll still likely have a late project because that 10% adds up. And in most companies that 90% is lower. It helps to have quantifiable progress metrics to understand where the trouble lies. This might not be the type of status you're referring too though.