View Single Post
  #52   Spotlight this post!  
Unread 12-11-2015, 14:27
gblake's Avatar
gblake gblake is offline
6th Gear Developer; Mentor
AKA: Blake Ross
no team (6th Gear)
Team Role: Mentor
 
Join Date: May 2006
Rookie Year: 2006
Location: Virginia
Posts: 1,934
gblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond repute
Re: On being rude ...

Quote:
Originally Posted by Lil' Lavery View Post
Blake,

If someone shot you an e-mail or PM with such a question, sure, respond in a short fashion according to your own time limits.

However, this is a public forum. If you don't have time to post more than "read the manual," you should probably simply let someone else respond to the question.
Someone else likely will. Until they do, the person asking the question will know that the answer they want is in whatever manual is mentioned in the short answer.

That person asking the question can also assume that the person who wrote the short reply is either busy (but still wanted to help), or is teaching them what others have surely already tried to teach them about asking good questions, or is rude.

Why assume "rude"? What gives anyone the justification to apply a blanket label of "that came from someone rude." to a short reply?

Why tell people who are willing to take the time to supply a short, useful answer, that their attempt to help isn't needed/allowed?

Answering my own questions, I know that I get irritated by people who fail to do their own homework/prep, and whose sloppy questions waste other people's time. And, the more often it occurs the more irritated I get. And the more irritated I get, the greater the chance I will be rude.

But, that does not mean that a short "Read the XYZ manual." isn't the best help someone could offer at the moment, or that it doesn't explicitly and implicitly contain a valuable, practical lesson for someone learning how to ask good questions. Absent evidence, I believe it would be rude to think otherwise.

YMMV

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

Last edited by gblake : 12-11-2015 at 14:56.
Reply With Quote