Mario Cervera
Software craftsman. I write about Software Engineering (clean code, design, testing, ...) and also about Algorithms & Data Structures.
Loved this article.
Hey can you suggest me a book on design patterns.
Starting my career I had just studied the patterns and could not really recognise when seeing the codebase.
There's actually a need to know these patterns.
Hi, I like your article very much!
I'm just more mitigated about naming: I see tons of developers using a lot of terms like "strategy", "factory", "facade", etc. But we should focus on expressive naming in the domain context and these suffixes should disappear. After all, they are simply patterns...
Thank you sir for an amazing article on clearing out this.
As a fresher I usually get stuck at the point whether it will be relevant to learning DP or not.
But, today you have cleared all doubts and given some solid reasons to prioritize the Design pattern.
Amazing Article, Mario!
Eric's book is definitive a must read Many people stick to the original gang of four patterns, but we learned a lot, discovered many new ones and also deprecated some.
They never updated their book for reasons beyond this article and our profession continued to evolve.
Amazing article Mario Cervera 👍
I didn't know that this is even a question whether design patterns are relevant or not.
Design patterns are even taught in CS degrees (not very detail though). So I always assumed that they're important as they're helpful to solve problems whose solution has been thought through already plus you added another 4 good points here in this article.
Really good article Mario! I'm an advocate for design patterns so this article resonates a lot!
They might not be as used as before, but they still have plenty of value for the reasons you mentioned. And I still find myself applying them frequently enough.
Keep the quality articles coming!
Adesanoye Samson
Software Engineer
Amazing article talk about everything i have read concerning design patterns