Which design template looked the most terrifying at first glance, but turned out to be the most beautiful after it was implemented?

I ask because most models are pretty intimidating at first glance, and I did not have much experience coding them. Most of what I had the opportunity to realize was worth the effort, but some made me feel like I wasted my time. I would like to try to bring down the beast and find that it was not such a big fight as it initially seemed.

Here are some suggestions for what I'm looking for in a good answer:

  • Short description or resource link
  • Why did you think that was ugly
  • Why it turned out to be beautiful.
  • Idea for a small project that can be wrapped around a template to show its usefulness.

Please do not send the code. I want this to be a learning experience.

+3
source share
2 answers

For me it was DI / IOC and Mocking.

It started with me, learning how to unit test. I quickly realized that this means that when you call the code, it will run ALL of your code directly into the database. So I asked the following obvious question: "How can I unit test my business logic without entering my database?"

When they told me about ridicule that sounded like a lot of extra work. Especially all the code that I would have to write chose when to use the layout in the test, and when to use the β€œreal” version in production.

, : " ?". ", , DI IoC. , . , OPPOSITE , 10 .

, , . , . , !

, ? DotNetRocks.

+3

MVC + iPhone/Mac. , , .

MVC. Builder .

+1

Source: https://habr.com/ru/post/1719578/


All Articles