<div dir="ltr">The question "who is at fault" is not meant as some kind of personal attack (= emotional is what you meant?) at the "jerk(s)" responsible, but rather as a question whose answer gives input to selecting the best course of action. Since my English isn't working today, in Racket:<div>
<br></div><div>;solve-problem : blame-who -> action</div><div>(define (alleviate-problem who)<br><div><div> (case who</div><div> [(Racket) (file-bug-report)]</div><div> [(me) (stop-being-stupid)]</div><div> [else (post-for-clarification)]))</div>
</div></div><div><br></div><div>The main use of this is to avoid filing bug reports for my own bugs.</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, May 5, 2014 at 9:59 PM, Hendrik Boom <span dir="ltr"><<a href="mailto:hendrik@topoi.pooq.com" target="_blank">hendrik@topoi.pooq.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">On Mon, May 05, 2014 at 11:58:17AM -0400, Sean Kanaley wrote:<br>
<br>
> So technically it was my fault,<br>
> but the documentation could benefit from some kind of "WARNING!" section on<br>
> each or at least especially dangerous pages for such pitfalls. Imagine if<br>
> your car explodes if you have the break depressed while turning the AC<br>
> dial. Probably don't want that info on page 87 subsection a.1.c. But<br>
> since there's no way to anticipate all potential user bugs, it's not really<br>
> the fault of the documentation writers either. So who/what is at fault?<br>
<br>
</div>A better question that 'who is at fault' would be 'what can be done to<br>
alleviate the problem'.<br>
<br>
I would make it less of an emotional issue.<br>
<span class="HOEnZb"><font color="#888888"><br>
-- hendrik<br>
</font></span><div class="HOEnZb"><div class="h5">____________________<br>
Racket Users list:<br>
<a href="http://lists.racket-lang.org/users" target="_blank">http://lists.racket-lang.org/users</a><br>
</div></div></blockquote></div><br></div>