Ugh... don't blame "design patterns". They are just tools, and any good developer utilizes them nearly constantly. Are we really going to suggest that you can w

Ugh... don't blame "design patterns". They are just tools, and any good developer utilizes them nearly constantly. Are we really going to suggest that you can write good imperative code that doesn't involve delegation, strategies, or factories at some level? The issue is with a culture that thrives on complicating relatively simple concepts by abusing those tools, not with the tools themselves. Design patterns don't make for bad code, bad coders do.