design-patterns-for-humans VS coding-interview-university

2. Design patterns for humans

For the first point, what really helped me is taking a look at the various design patterns that are usually used. However, do not force a design pattern into code, it should come naturally to you which pattern fits to a problem. A great resource I can recommend is the README.md file on this GitHub project.

I'd recommend reading gang of four design patterns https://github.com/kamranahmedse/design-patterns-for-humans

If you want to learn more about design patterns, don't forget to take a look at Design Patterns for Humans, it's an incredible repository with many interesting examples that you can apply when you want to use a design pattern to solve a specific problem.

Ideally, we would write a facade for those methods and provide an API like:

https://github.com/kamranahmedse/design-patterns-for-humans#-singleton

✅ jwasham/coding-interview-university : https://github.com/jwasham/coding-interview-university

4) Coding Interview University: Conquer the dreaded coding interview with this battle-tested arsenal of algorithms, data structures, and interview prep strategies. Sharpen your problem-solving skills, optimize your coding efficiency, and ace those technical assessments with this invaluable resource. (https://github.com/jwasham/coding-interview-university)

View on GitHub

I stumbled upon a github post called coding interview university and with the shiny object syndrome I have, I kinda want to ditch the roadmaps and start something new like this one in github, or the random dude I found in YouTube, telling his audience that he passed the FAANG interviews. The annoying part of me is that whenever I hear stuff like “I passed the FAANG”, I will immediately try to follow their path because their method works for them or to some other people