Lessons from the Big Ball of Mud

It's important to have a repertoire of patterns we can call on as we design and build our projects.It's also important to recognize non-optimal choices or so-called "anti-patterns."How do we do that? What does that even mean? Should the anti-pattern always be avoided, by definition?
Identify code smells, manage your technical debt, and hover one foot off the ground! (Maybe not that last one.)

Have a look at the sites linked above, and also:
Anti-patterns from Wikipedia
and if you really want to dive into it...
Join the discussion!

Subject Author Replies Views Last Message
No Comments