Design patterns are typical solutions to commonly occurring problems in software design. They are like pre-made blueprints that you can customize to solve a recurring design problem in your code.
If you’ve never played around with design patterns it can take some time to grasp the concepts. But, once you start to understand how everything works the magic floodgates open ;)
Love this website, it helped me out so much during my Java days figuring out how I should be trying to structure my code. Obviously, there’s a balance as to how much abstraction to include, but things like the Observer pattern, Strategy pattern and Adapter pattern are super super practical across many languages.
These days in TypeScript-land I don’t tend to use too many design patterns, I try to be as functional as practical, but I owe a lot of my foundations to this website.
I’ve moved into a cloud engineer position and have to use Python 90% of the time for Lambda functions. It allows me to keep things structured and avoid some of the spaghetti code that lives out in the void. I started getting into TS, but this job came up and had to change my focus some.
Do y’all use Python 2 or 3? Got many types to work with?
Python 3.10 current, we were stuck on 3.9 for awhile. 3.10 finally gave us the ability to do switch-case statements as opposed to the if else hell.
You might also enjoy Brandon Rhodes’ website which has some pretty skillful writeups on Python Patterns as well.