Bloating something that could be done robustly, maintainably, and with clarity from fifty lines to two hundred isn't a practice I would consider "best."
On the other hand, taking something that could be done robustly, maintainably, and with clarity in 200 lines, and instead writing it without those qualities in fifty lines could be a bad practice.
If you haven't yet seen the benefits of modularity, generalized solutions, maintainability, separation of concerns, thorough testing, and tools such as version control, I recommend going with the flow for now, and opening yourself to trying to understand why so many others consider such practices meritorious.
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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||