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 warm glow.

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.

Brad

---

---

• 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.