Can you tell us what kind of "code smells" you've observed, and also, can you tell us if you've seen any evidence they're really causing you problems? Compliance with doctrine isn't the ultimate goal, of course...
The one abuse-of-objects practice that I've seen really cause problems is "the Blob anti-pattern": one of the few things I really like about "Objects" is they way they handle encapsulation, and if you've got everything shoveled into one namespace, it hardly matters if you call that namespace an "object" or a "bloated script".
In general, I've been coming to the conclusion that having a nice barrage of automated tests is the key thing: compared to that, every other issue (choice of language; design patterns; OOP/proceedural; inside-out, upside-down or sideways, etc) is nearly insignificant.
(Though I don't think "Test First" programming isn't strictly necessary, "Test Soon" is good enough.)
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.