in reply to a bit of monastery zen

Lately I've been feeling different about asking questions. Yes, do what you can to solve the problem as that's where most experience will develop but why not share it with the community? I've beat myself up about asking questions. That can be good as it's forced me to improve my Perl and general problem solving skills but I sometimes feel that I (and others) benefit from different perspectives provided in the monastery.

While most of my questions have been of the type that I SHOULD (and do) solve on my own, some I feel were worth sharing. Recently I've been a little confused about regex lookarounds and when best to use them. I have questions about creating good data structures or how to find relationships within the raw data. Has it been asked before? Almost definitely. Are there readily available examples and lessons on these topics? Without a doubt. But I should sometimes try to present my own perspective and context to problems. I should put in the 15 or 20 minutes to compose those thoughts into a question that spurs discussion.

And for each of those times that we do solve our own questions following a good struggle, are they worth a meditation? Not always but maybe more often then we think.


"...the adversities born of well-placed thoughts should be considered mercies rather than misfortunes." — Don Quixote

Replies are listed 'Best First'.
Re^2: a bit of monastery zen
by locked_user sundialsvc4 (Abbot) on May 24, 2011 at 05:25 UTC

    As for me, I would answer ... “very urgently and emphatically... yes.

    If a colleague has good thoughts ... good to him or to her ... then, “I want to hear them, perchance to ignore them completely.”

    If editing (or ignoring) is to be done, then let it be done after the thought has been committed forevermore to digital posterity.