When DRY becomes an anti-pattern: Code in Code

The anti-pattern here is applying DRY to <i>text</i> rather than intents. The identical text may appear in a different source file with a different intent, say a tax calculation for a region. It may very well be that two regions have the same formula, but it&#x27;s obvious that you shouldn&#x27;t DRY it.<p>The example used in the post had no real-world intent. The intent was to blindly apply DRY which doesn&#x27;t count as one.

I&#x27;d argue the example given in the article is bad not because it doesn&#x27;t repeat itself, but because it only concats strings. Using more advanced language features, or perhaps a ORM, I think you could easily come up with a solution that doesn&#x27;t involve repeating parts of SQL queries but is still readable.