How To Recognize When To Use A Design Pattern In Python

There are many design patterns that you can use in Python. But when should you use which one? In this short, I'll go over the way I learned to recognize design patterns and when to use them in my code.

#arjancodes #softwaredesign #python

[Janim]

Can you please make a video on when to recognize a pattern based on the data that the developer should be handing?

[Renan-gn]

I think this came up as i was learning programming on some good courses, it does not touch direclty on design pattern, but a lot on good principles, that when i studied design patterns i noticed that i already did make use of some without even knowing

[StenAkselHeien]

After my first PLoP conference I also started trying to over-use patterns in the beginning, but later in life I had the same experience as you describe

[henrikolsen]

I love your content, Arjan. Thanks for making this available. Will be buying your course soon. One thing regarding the productions - I think the stock clips you put in distract. One aspect I have especially appreciated in your videos, are the pureness of your content. Just you, great knowledge and demos, no BS :). I would prefer keeping it this way. Clean. Great with the great quality of sound, lighting, editing etc, but stock clips as fill. Nah.

[kayakMike]

Yeah, I noticed this too. I was super obsessed about which pattern, but as time went on I worried less and less, but you can still see facades, adapters, factories... But never singletons. Singletons are irritating magic that should just be injected in the factory anyway. Singletons wreck testability... They are a design anti-pattern.