comment on

Thanks for the responses, everyone. They bring to mind some things I should go about learning, and some things I should clarify.

First off, things I should learn - I'll be picking up Mastering Regular Expressions and Higher Order Perl fairly quickly.

Secondly, a clarification - right now, I don't actually work with Perl for my dayjob(or at least, not most of the time - our sysadmin gets me to write him tools every once in a while) - my employer is running a pure M$ shop, and so I work primarily with ASP.Net and C# for my day job - all of my own personal projects are Perl, however.

I know a few other languages, in addition to the standard Web Developer pile - Javascript, XHTML, CSS, and at least one server-side language(in my case Perl, although I can fumble my way along with PHP as well).

I actually already own a copy of Object Oriented Perl - I thought it was interesting(as was Moose), but I haven't encountered a situation where it immediately sprang to mind that "hey, I should use OOP for this!" - I generally design my projects in such a way as to not need OOP. I do use it for some things - I just don't encounter too many situations where I'd like to use OOP and don't already.

I guess, really, I'm looking for cool things I can learn that I don't already know that can speed up my development time and let me reduce repetition. That's why learning about things like map and grep was awesome - because I could instantly see how much they saved on time(and keystrokes).

website army

In reply to Re: Finding the path by Spidy
in thread Finding the path by Spidy

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> <u> <ul>
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 intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Problems? Is your data what you think it is?
	PerlMonks