comment on

Personally, I figured out a long while back that if I can't summarize the problem in one or (at most) two sentences, I probably don't really understand it.

I often ask people asking for help in EFnet's #perlhelp to describe the problem in 12 words. This makes answering questions much easier, if only because when shortening their question they often realise they already know the answer :)

12 words is a rather small limit, but this is necessary to force them to abstract it and leave all external factors that have nothing to do with the problem out. It also helps people learn jargon.

So far, most questions that couldn't be summarized in 12 words or less turned out to be composed of multiple related questions or to be about some very awkward program design.

Yes, I do think even questions should be refactored when possible.

(And it can of course be 13, 14, 15 words. But if you say 15, you get 20, and that is too many.)

Juerd # { site => 'juerd.nl', plp_site => 'plp.juerd.nl', do_not_use => 'spamtrap' }

In reply to Re^2: How do YOU find the answer to your question? by Juerd
in thread How do YOU find the answer to your question? by Velaki

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Pathologically Eclectic Rubbish Lister
	PerlMonks