comment on

One way to do the baby steps thing is to set up a single directory where you will try this approach. Think of it as a test site or sub-site. Then, go wild in that directory.

One of the realities of programming is that you will have bugs. Fixing these are much easier if you are not stressed about getting your whole site back on line.

As you get an idea fleshed out and (relatively) stable, you can apply that idea (and possibly code) to your main site.

I know it seems like unnecessary, extra work, but we are suggesting this based on years (in my case around 20) of development in multiple languages on and off the web. The first time you really mess up, you'll thank us. (And if you don't really mess up, you're not trying hard enough.<grin/>)

Stay curious and have fun.

G. Wade

In reply to Re^3: Seeing Perl in a new light by gwadej
in thread Seeing Perl in a new light by Lady_Aleena

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.


No such thing as a small change
	PerlMonks