@Arthur P. Bloom posted:A corollary to this topic is the frustrating activity of attempting to help a person with a technical question, and, in doing so, taking a significant amount of reflection and dissecting the problem, and then, asking in return, the OP to answer a few questions before the helper can render an opinion.
I have many times asked an OP to answer 4 or 5 simple step-by-step questions, much like a verbal flow chart, to get the OP to understand, before any advice is given, what the problem really is. Many times, the OP will answer one or two questions, and answer a few that weren't even asked. It's like pulling teeth, but we soldier on, because it's the right thing to do.
Many questions are not answered simply. There are variables, misconceptions, and misunderstood assumptions. (Bad spelling, bad grammar and colloquialisms don't help, either.) Simply to answer and go on with one's life is not in the best interest of the OP. He needs to see the big picture, broken down into little pictures, and then be presented with the opportunity to have his own "AHA!" moment.
Take, as an example, the well-meaning members who admit that they little or nothing about electricity but want to know how to install or repair a toy that has two words: ELECTRIC and TRAINS.
To answer in a way that elevates the OP's future chances of self-made success, a little of the old Socratic method is necessary. If you don't know who Socrates was, now's the chance to Google and elevate.
(BTW, 14 gauge is the correct answer to everything.)
I have to disagree, one thing I learned commanding a warship in the Navy was “ keep it simple *****8*), details do not guarantee success but can lead to a train wreck. It is always best to “read” what they are asking, the type of question will give you the level the person is at……..than tailor the answer to his level. Not making you feel like the expert.
Go Simple or Go Home!
