Здравствуйте, Alxndr, Вы писали:

A>Есть еще такое понятие как "экономическая целесообразность". Если тебе к завтрашнему дню нужна утилита, то, возможно, более оптимальным является "нахачить по-быстренькому" без архитектурных изысков и метапрограммирования, а возможно даже (о ужас) и с копипастом.

How to Recognize If an Application Will Be Long Lasting
Speaking of long-lasting applications, I especially remember one particular application I was asked to build. A global data communication service provider asked me to build a preliminary help desk application to be used at their new office in Sweden. Time was tightthey needed it the next day so that they weren't sitting there with paper and pen in their high-tech office when the press came to the opening day. Because it was going to be exchanged for a company policy standard application just a few weeks later, however, they told me that building it well wasn't important.

Yep, you guessed right. The quick-and-dirty application I built was still being used in production five years later. Sure, we improved it a lot, but I couldn't convince them to change from the platform I started using to something more suitable for a mission-critical application.

(с) Applying Domain-Driven Design and Patterns... By Jimmy Nilsson

Это я к тому, что в долгосрочной перспективе экономическая целесообразность может отличаться от ее же в краткосрочной перспективе.