You know, every time I read something about Design Patterns and I end up reading about a specific pattern and I laugh, because I can recall all the times I've used that pattern before without even knowing the official name for it.
This isn't a problem for me as I've done most of my development work as a solo developer, but communicating a certain approach to a problem can be made simpler by knowing the official name. Makes sense.
Now please, don't decide you're going to use pattern A, B, C, X and Y, and then start thinking about the problem you're trying to solve, because you might just end up building a marvellous monstrosity versus a natural approach that, where afterwards you say, "Oh cool, I used Pattern C".
This way, the situation dictates the exact solution.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
You know, every time I read something about Design Patterns and I end up reading about a specific pattern and I laugh, because I can recall all the times I've used that pattern before without even knowing the official name for it.
This isn't a problem for me as I've done most of my development work as a solo developer, but communicating a certain approach to a problem can be made simpler by knowing the official name. Makes sense.
Now please, don't decide you're going to use pattern A, B, C, X and Y, and then start thinking about the problem you're trying to solve, because you might just end up building a marvellous monstrosity versus a natural approach that, where afterwards you say, "Oh cool, I used Pattern C".
This way, the situation dictates the exact solution.