I propose we add a new(?) acronym: UTFM (Understand The Finger-lickin'-good Manual) so I can say "I RTFM but I can't UTFM"...or better yet, ICUTFM (I Can't Understand The Finger-lickin'-good Manual) so I can say "I RTFM but ICUTFM"...oooh oooh, even better: IRTFMBUTFM ( I Read The Finger-lickin'-good Manual But I Can't Understand The Finger-lickin'-good Manual).

I'd have to say that I agree with this statement entirely. (As a software engineer, I even like all the acronyms.) My problem is that I'm a software engineering student and I'm much more used to writing large applications using C++/Java/Ada, etc. Also, I do my development in a Windows environment and I've done little work on Unix or Linux at all. For me, web development is a job I have on the side and something I like to do for fun. This can cause the rather "Unixy" cryptic syntax of Perl and its documentation rather frustrating. Granted, once I understand a function, the documentation makes perfect sense...it's just getting to that point where I have trouble. I need to see an example of how it's used before I can really understand it well. (See the section on books below)

Finding The Monastery was the most important step in my journey.

I'd have to go along with Mission (after all, I work for the guy) in saying that PerlMonks has been a great help. Granted, I seem to get razzed every time I post code because everyone tells me that it looks too much like C and that it's not very "Perlish" (Now that you know what I do, can you blame me?), but the monks are very helpful...and very prompt. I actually had one monk send me a lengthy e-mail (thanks again tinman) explaining what a module was and how to install new ones.

I couldn't really afford to buy books on the subject

Now if only I could convince Mission to buy me more books...

- Sherlock