Remember the Second Rule of Systems Design:
If it ain't broke, don't fix it
I have had my fill of 'change for the sake of change' from my managers over the years. We have something that works superbly (most of the time) and supports a thriving and vibrant community (see, all those hours spent in meetings with the marketing droids has enlarged my vocabulary).
And this brings us to the First Rule of Systems Design:
The New System has to work AT LEAST as well as the system it will replace.
Any new "improvement" has a high bar to reach.
Also, "If I must read a large block of code here, I really need to put a zoom of 25% or 50%...", I submit that it is high time you had your eyes checked and your glasses prescription updated. I only need a 5% increase in size.
I Go Back to Sleep, Now.
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:
Outside of code tags, you may need to use entities for some characters:
- 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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||