The concept of desk-checking as a part of the classical life cycle was valid in principle, but never was done. Walkthroughs not only detect errors in advance of testing, but encourage developers to think out their ideas more completely before review The result is that more debugging is done on paper, less on the machine. Procedures for peer review provide the following advantages:
- detecting problems earlier
- spreading familiarity and expertise
- homogenizing style and method
Institution of walkthroughs has a further effect of breaking down the attitude that a program is the very private personal property of the developer, really no one else's business. By the time the walkthrough is complete, reviewers have been co-opted into considering the product as much theirs as the original developer's.
This is from Concise Notes On Software Engineering, by Tom de Marco. New York, NY., Yourdon Inc., 1979. ISBN: 0-917072-16-2.
As to why this kind Internet experience might cause you to react differently from other modes of communication, keep in mind that most of this is without real time context. No body language or other clues generally forces worst case evaluation, which is most likely not the case at all. And it certainly isn't just you, it's all of us. The reason that words like 'troll' and 'flame' and such have become so well known is that they are useful descriptions of some of the markers of this new territory well all find ourselves in.
–hsmIn reply to Re: How can I grow a thicker hide?
by hsmyers
in thread How can I grow a thicker hide?
by rje
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |