Comments on: Don’t Get Obsessed With Design Patterns

By: The Criticisms of Design Patterns – James Blash

The Criticisms of Design Patterns – James Blash — Thu, 06 Dec 2018 14:41:43 +0000

[…] to write is similar to a pre-existing design pattern, then you have a direction to follow. This article in particular gives a great example of an application of the template pattern, and shows […]

By: The Perfect Design: How to design your next web development project

The Perfect Design: How to design your next web development project — Fri, 07 Sep 2018 13:32:30 +0000

[…] me is that I don’t like to stick to a single design pattern while coding. Why? try reading this article and thank me later.. the writer (Joel Rodriguez) did a perfect job explaining such […]

By: Joel Rodríguez

Joel Rodríguez — Mon, 18 Jul 2016 18:55:00 +0000

In reply to Aadhith Bose. Glad you liked the post, Aadhith :)

By: Aadhith Bose

Aadhith Bose — Tue, 05 Jul 2016 06:53:00 +0000

I was a manual tester, now immersing myself into Automation. Anyways this article seems good for me. Because when I completed basics of Selenium with C# I was pretty confused with which Design Pattern Should I follow. Now I learned Page Object Model and Facade Design Pattern. As you already mentioned in the Post, it’s not the design pattern but the context is what counts when selecting the design patterns.

Thanks Joel for the insights.

By: Compelling Sunday – 28 Posts on Programming and QA

Compelling Sunday – 28 Posts on Programming and QA — Sun, 19 Jun 2016 15:48:32 +0000

[…] Don’t Get Obsessed With Design Patterns – Joel Rodriguez(Simple Programmer) […]

By: Weekly Links #19 | Useful Links For Developers

Weekly Links #19 | Useful Links For Developers — Sat, 18 Jun 2016 18:10:30 +0000

[…] Don’t Get Obsessed With Design Patterns […]

By: olavgm

olavgm — Fri, 17 Jun 2016 09:42:00 +0000

In reply to Richard Irwin. Completely agree with you. Applying the template pattern on the NoteDrawer class is a perfect example of over-engineering.

By: Don Woodford

Don Woodford — Fri, 17 Jun 2016 01:55:00 +0000

In reply to Richard Irwin. You're doing it wrong. If this previous employee really over-engineered the code you should be able to use the open-closed principle to apply your changes.

By: Joel Rodríguez

Joel Rodríguez — Thu, 16 Jun 2016 17:27:00 +0000

In reply to Richard Irwin.

That’s true. I didn’t go into the problems of overengineering, but it’s definitely another reason to consider.

Thanks for your comment 🙂

By: Richard Irwin

Richard Irwin — Thu, 16 Jun 2016 13:27:00 +0000

The one thing I think is missing in this article is the cost of maintain code that is overly abstracted/engineered. I’m currently working on a project that was written (by this guy that is no longer here) that took a class in design patterns and used every one that exists. To make even the simplest change in the system requires the programmer to make changes in many levels and areas of the code and takes about 10 times longer to do it compared to other less engineered systems I’ve worked on.
There is a trade off between abstraction and maintenance complexity