The really Bad Thing about not thinking about the
application, is that every time you add something, something
else will inevitably break. It's like those squishy tubes
that you sqeeze and they fly out of your hand...an endless process of adding in kludges.
h0mee and I were driving around one night discussing breakage,
and came to the conclusion that It's All About The Data.
Knowing your data will be the difference between breakage, non-breakage;
a maintenence nightmare, and a maintenence pleasure. For example,
in Programming Pearls, in the first column, Bentley (the author)
discusses an old school problem of sorting thousands of 1-800 numbers
using about a megabyte of memory. They ran into some Really Bad time-space issues with certain algorithms, so they used a bitmap vector
to map the data. It was a novel solution because it was engineered to the
data. The problem is maintaning a symbiotic relationship between data
and algorithm whilst preventing breakage. Verily, this is very difficult.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||