in reply to Perl Elitist Code vs Functional Code
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.
Dave
|
|---|
In Section
Seekers of Perl Wisdom