News for hackers. Stuff that matters.
Re:The Rands Test by Periodic on Tuesday October 11, 2011 @02:19PM (#3099700)
This is the real point the author is trying to make. Any information you would put in a status report should already be in another system already. You have your task and project management system, your bug tracker, your version-control system, and your code-review system. All of these should list essentially all the things you've done and it would be easy to look back over a historic list for your user.

Status reports are generally duplication, and if they aren't, then the tasks are not being tracked properly.

Re:The Rands Test by snprbob86 on Tuesday October 11, 2011 @04:15PM (#3100117)
Not everything can easily be itemized into a bug tracker or project management system. Sometimes you just need to tell a story. This is particularly true in disciplines outside of engineering.
Re:The Rands Test by dpritchett on Tuesday October 11, 2011 @05:30PM (#3100375)
That's where the well-run meetings come in.
Re:The Rands Test by snprbob86 on Tuesday October 11, 2011 @05:51PM (#3100466)
Not all teams are co-located. Real-time communication mediums are sometimes the wrong choice, like when you need to curate your message. Meeting minutes are just another kind of team-wide status report. Collaboration is complex and nuanced. Status reports have their problems, but they have a place.
Re:The Rands Test by slantyyz on Tuesday October 11, 2011 @06:34PM (#3100684)
For every person you encounter who hates doing status reports, you'll probably find one person who hates attending or participating in meetings, even those that are well run.