My first reply was strictly based on Komodo as a product, but I think your real question deserves some additional comments as well.

I am always on the quest for more consistent and faster to produce code. When I was managing other developers this seemed even more important, but I feel that most of this comes back to the individual doing the coding. Tools can no doubt help, but I find that the editor or IDE can only go so far. The biggest improvement for me when using a product like Komodo is its error highlighting, this has kept me from having to do a compile to find out I made a mistake, and I do feel my level of output has increased because of it. However I feel my coding method and quality has increased more by adding durable testing code and processes to the development cycle.

With your current tool set (cvs,emacs) I don't think you will get a large enough advantage out of Komodo, but I am not sure which feature in Komodo is most attractive to you.

See Ovid's recent node on testing , and my reply for more info.

If you are already using testing code then I would suggest that you look at how to move more of the code into rules or configuration files rather then keeping it all in code, this has been a big help in my development cycle as well. I like using Config::Auto along with Class::Accessor to create method calls for each of my configuration values which goes a long way in providing a flexible consistent means of getting and setting application parameters. This is all OO Perl and if you are not doing OO Perl I am not sure how to best bend it to your needs.

In reply to Re: Activestate Perl and the Komodo IDE by trs80
in thread Activestate Perl and the Komodo IDE by monkfish

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.