A broad field you meditate on. I don't know much about Linux distributions - I do my development (at home) on a Win2k box, at work I use Solaris and Windows NT. I can offer three answers to your questions :

First, plan to throw away everything you'll write in your first two generations. In my experience, you need to have implemented a task at least three times, before you know what the important details are, and what approach will work in the end. Don't invest in a large scale object model or too detailed planning, as it will tie you to the bad ideas you had at the start. You maybe already have gathered some experience in your field with your one-off scripts, but that experience won't reach far enough for a help-desk application. In my opinion, you should first write all the one-off scripts as separate scripts, and watch out what parts can be abstracted into modules, and what parts simply aren't worth the bother. Remember that when you change a module, every program that uses it needs retesting, but when you change a copy of the module, only the program you're working on needs retesting.

From my experience, you can't have enough logging. Period. Rotate the logfiles daily, if diskspace should be of any concern, but log everything. Don't make it configurable or somebody will switch it off. Logs aren't there for when everything works as planned, but they are there for you to stare at after something unexpected happened. Plan for an easy parseable format, and for logfile viewers (CGI maybe) that allow you to specify different levels. But don't throw away the log data.

From what you describe, you'll be working alone - this is a bad idea. You need someone to discuss your thoughts with, and your boss will also need somebody to take your place when the bus runs you over. A lot of bad design ideas get killed by explaining them to somebody else.

perl -MHTTP::Daemon -MHTTP::Response -MLWP::Simple -e ' ; # The $d = new HTTP::Daemon and fork and getprint $d->url and exit;#spider ($c = $d->accept())->get_request(); $c->send_response( new #in the HTTP::Response(200,$_,$_,qq(Just another Perl hacker\n))); ' # web

In reply to Re: Developing a Suite of CGI applications by Corion
in thread Developing a Suite of CGI applications by jordanh

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.