Matthias Reuter wrote: > These guys would never read documentation. We have a large set of > documentation on the architecture and styleguide and best practise of > frontend development, and somewhere in there I put "If you read this, come > to me and you get some sweets". Of all the people in our team, only one > read this.
That puts me in mind of a story (as Shadow Hamilton would say). I worked with a developer once who was forced to create an unread bit of documentation on every significant subsystem. At one point, in a meeting with the higher-ups, he said he wouldn't be doing that documentation any more. They insisted that it was crucial. "But no one reads it," he insisted. "Of course we do," was the reply. He then asked an admin in the room to go find any instance of that report and read it, coming back in when she found an appropriate reason. The meeting moved on, but it wasn't three minutes before she came back in and interrupted, asking the developer "Can I have that $100 bill, please?" He opened up his wallet, handed her the money, and explained that he'd had that bill in his pocket for more than two years. Every report had in its second paragraph a note that he'd give a $100 bill to the first person who'd read that far into the report. No one ever asked him to do that report again. -- Scott -- To view archived discussions from the original JSMentors Mailman list: http://www.mail-archive.com/[email protected]/ To search via a non-Google archive, visit here: http://www.mail-archive.com/[email protected]/ To unsubscribe from this group, send email to [email protected]
