Patterns that every developer should know

Readability is indeed more important than cleverness!

"A common phrase I use across my blog posts and in my general philosophy towards writing code is: readability is more important than cleverness." <-- Thank you! There are times when I've worked on projects where I swear some programmers made the code illegible in the hopes it would make them look smarter than anyone else. Being the only one to understand what you've written doesn't make you clever...

I wonder where this author would sit on the debate of class components vs. functional components in React. His advice and patterns are in C# and it's not something I have a lot of familiarity in. However, hooks have been around now since 2018 and it feels like in 2022 you run into them more and more.

I'm still of the mindset that people should know the lifecycle method and write classes because classes are a central idea to other languages (like C#), but I also understand that hooks are "easier" for some people, even though they really just abstract the lifecycles methods.

As an indie dev, it doesn't matter which we use, since no one is reading our code. But in a gig, class > hooks for readability..

I thought every software engineer took this class/have this book:

Design Patterns: Elements of Reusable Object-Oriented Software:
Erich Gamma, Richard Helm, Ralph Johnson, John Vlissides

It's always sitting on my shelf.

Thank you for sharing really useful content :)

Patterns are great, but so is clean readable code, I'd recommend pairing this with "Clean Code" by Robert C. Martin. When you marry patterns with readable code, you achieve coding nirvana.

Thanks for sharing, this is well-written.