In order to keep track of our company assets I started entering data into a MySQL database. I planned it out, and thought it would be a good idea create a CGI interface that grabs and presents data with DBI. I was able to get something simple up that has a pull-down menu that shows the selected user's assets when a submit button is pressed. As I started getting ready to increase the functionality of my plucky little application, I started thinking about file structure because I figured as the application started to get bigger I would want to make sure that my code was organized. I was more than happy to include all of the right modules in my own application, but after thinking about the replies I received and reading about mvc in Joost's article, then seeing what maypole could do, I started doing the Catalyst tutorial and found it to be quite useful.

However, I see a drawback in that I am not writing as much of the application and thus am not learning as much perl. I feel this is made up a certain amount by the fact that I am learning how more experienced perl hackers are doing things. For example, I am being exposed to database schemas. I never would have thought to do that with my queries if I hadn't started playing with Catalyst. I guess my question is this:

When considering the merits of working with the catalyst framework(faster deployment) and the drawbacks (not learning as much perl as catalyst object structure and templating), Is working with catalyst good or bad for my perl education?

My end game is to get more perl work; so I figure if I can deploy quickly and my web app is impressive, then it should be a good thing. What do you think? Am I going in the wrong direction? Will I get a more perly experience if I use something like CGI::Application?

-Actualize

In reply to Is using Catalyst cheating? by actualize

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.