Home/ Questions/Q 405253
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-12T17:23:00+00:00

I often find myself reading books and articles that outline patterns, best practices, and

  • 0

I often find myself reading books and articles that outline patterns, best practices, and how to write “clean code.” However, some of these concepts just seem to be over engineered and at times obscure the essence of the underlying problem, making the code more difficult to relate to the problem domain being modeled.

How often do you find yourself refactoring a piece of code that works well in favor of a “pattern?” Have you encountered a situation where the “pattern” actually complicated the code or obscured its meaning? I felt this way a while back after seeing a solution to a problem I solved with a simple class rewritten using lambdas and closures.

I struggle with this and I’m curious how others approach find the right balance.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You should never refactor your code just to make it fit to a pattern you’ve read in some book.

    Patterns really help you to train your brain in terms of thinking about good software design. I would actually say that I acquired much of my programming skills and knowledge through reading of pattern books and by reflecting about them and by learning to understand how they work out and what advantages they’ll give you. And that’s actually the key. Their purpose is to make things easier, more maintainable, easier to test etc… not to make your life harder 🙂

    I think that’s also the “difficulty”. Patterns give you a frame, a point to start from when you encounter a problem. Example: You really want to unit test your code, but you’re just not able to because it depends on UI logic or is too much coupled. That’s your problem, so you may get to a solution by knowing about the MVC pattern and the concept of dependency injection and IOC. They may give you a starting point since the MVC for instance explains you on a high level concepts of an Observer, Observable, Controller view etc…and how they are related to each other. It is then your task as a good programmer to choose the right approach and to what extend you find it reasonable to apply the pattern. Don’t just apply it ’cause the pattern tells you. Remember, it is just a frame, you may modify and adapt it s.t. it is suitable for your specific circumstances.

    • 0