At my job, I have to write parsers for data that comes from online information repositories. Each repository provides pretty much the same information, but each has its own quirky format. Until recently, I was writing parsers based on the domain name of the repository. The problem here is that sometimes a repository will start using a new format. Once this is detected (and it might take a while for us to realize that) I have to examine this new format and write a new parser.

Then, this morning, I noticed two repositories in a row in my queue that had the same IP address. D'oh! It turns out I've written a lot of duplicate parsers. Things that appeared different were not distinct, but only variable (e.g., an address that requires two lines instead of one). These differences between repositories made me write seperate parsers, but this IP realization has shed light on the issue.

As of tomorrow (when I should have the redundant parsers done away with and the core parsers centralized) there will be far less code to maintain, and it will be easier to deal with a change of formatting. See, if repositories A, B, and C are all the same IP address, then if that IP address's format changes, I only need to update its format. If just A changes its IP address, I can take care of A's format without worrying about B's and C's. Even better, if these repositories new IP address happens to already be covered, I don't need to anything.

Laziness, Impatience, Hubris. Amen.

Jeff japhy Pinyan, P.L., P.M., P.O.D, X.S.: Perl, regex, and perl hacker
How can we ever be the sold short or the cheated, we who for every service have long ago been overpaid? ~~ Meister Eckhart

In reply to Perl Virtue: Laziness by japhy

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.