While it's an interesting acronym, TITS is not always practical. In certain situations it can be a waste of time. If I know how to do something in one language and want to know if something in another language does that very thing, I can ask 'what will this do' and listen for clues of what i'm trying to do. I could try it but if it doesn't do what I want, I have to find the next thing. To ask the question saves time. For newbies like myself, I would rather ask than try 10 different modules and never find what I was looking for. Once I ask and hear that the module will do it, then I will TITS how to make it work for my purpose. IT'S GETTING TO THE RIGHT THING TO TITS!
BrowserUk hit the nail on the head! This is a great site for these questions. They may seem minor to experts but i'm just looking for a starting point. How do I ask the question? How do I find what I want? How do I google for it? I don't know so I come to perlmonks and ask the question - what does this do?
Thanks for this meditation. It was a great one and thanks BrowserUk for your comment! I look forward to learning from the more seasoned monks.
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>
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
Want more info? How to link or
or How to display code and escape characters
are good places to start.