I don't have a problem with people answering at different levels of abstraction.
Neither do I. But the path of abstraction should be visible, and understandable. The post from merlyn you cite is not so much about abstraction, but about how skilled guessing works: not presuming too much, and not sending off people with a premature answer that really doesn't help solve X or Y entirely.
Throwing in consultancy jargon quotes from a random bullshit bingo chart which might, by several twists of the mind, yield some remote connection to the problem at hand is not that sort of abstraction, or skilled guessing. It is throwing shiny shingles on a fishing line into the river - it is trolling: trolling with baits, and more often than not, they are toxic.
perl -le'print map{pack c,($-++?1:13)+ord}split//,ESEL'
-
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.
|
