|
Re: On being rude ...
Folks,
The "Read the manual" subtopic here, is one I'm going to try to pull out of.
If what I have written so far about avoiding placing an asymmetric burden on writers, and about applying "rudeness" yardsticks carefully and symmetrically, isn't persuasive, writing more probably won't change opinions.
I'm not trying to get in the "last word" on "RTM" (other folks may do that if they like), but I am curious if there is anything else related to this thread's original thesis that anyone wants to discuss? What are some other rabbit holes to dive down?
Blake
__________________
Blake Ross, For emailing me, in the verizon.net domain, I am blake
VRC Team Mentor, FTC volunteer, 5th Gear Developer, Husband, Father, Triangle Fraternity Alumnus (ky 76), U Ky BSEE, Tau Beta Pi, Eta Kappa Nu, Kentucky Colonel
Words/phrases  I avoid: basis, mitigate, leveraging, transitioning, impact (instead of affect/effect), facilitate, programmatic, problematic, issue (instead of problem), latency (instead of delay), dependency (instead of prerequisite), connectivity, usage & utilize (instead of use), downed, functionality, functional, power on, descore, alumni (instead of alumnus/alumna), the enterprise, methodology, nomenclature, form factor (instead of size or shape), competency, modality, provided(with), provision(ing), irregardless/irrespective, signage, colorized, pulsating, ideate
|