On 22 May 2013, at 10:06 , David Kastrup wrote:
It's just a matter of efficiency. To find the problem, you need to
boil
down the code to the essential part anyway. Not doing this in advance
is only efficient if the expected number of helpers is below 1 or if
their time is to be valued less than that of the person having the
problem. But making it easy for people to help also makes it more
satisfying for them, so it is also an advantage for the long term.
AND: boiling down the problem makes sure there IS a problem. Sometimes
a problem you experience goes away when boiling down, so when you
compile at stages in between you'll might find what caused the problem
itself. And (ideally) that process mostly happens before you put it on
the list.
Boiling down then also gives any helper the assurance you looked at
the problem yourself seriously.
Regards,
Wim.
_______________________________________________
lilypond-user mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-user
