I've certainly done and redone the wheels Simon mentions.
I then found it instructive to compare the working
of my solution with others.
How does Kwiki do configuration?
How does So-And-So debug his code?
If they do something better
then I learn, if our designs converged I get a
Another thing I've tried to do, but not really succeeded,
is to think about the limitations of the way I use Perl.
After looking at Prototyped OO I found cases where I was
badly half-implementing it. Likewise with AOP.
Then the Apocalpses came out. I read along as Larry
solved the problems I couldn't even see I had (and Perl had).
This changing of perspective has teaches me most but
it's difficult to turn into a process. Therefore,
it's probably difficult to teach. I just continue to
bang my head against things I don't understand until
one or the other cracks. Good luck finding an alternative.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||