No Boilerplate"A modern developer need not know the Gang of Four "Design Patterns",
but they should at least have forgotten them."
Agree? 🤔
boost appreciated, let's find out!
Yep, still relevant
No, it's not 1994
The what patterns? (see replies)
Poll ended at .
b4ux1t3 
#1️⃣@noboilerplate as with all things: it depends.
Design patterns as a concept exist as a sort of lingua franca in software development.
It doesn't matter what language you use, a repository pattern is a repository pattern; it may be implemented with a repository object in dotnet, or a repository module in rust, or a separate service fed by a message queue; the pattern is flexible enough to describe a way of solving a common problem without reference to an actual implementation. 1/2
@noboilerplate but, you hardly need to read a book on to get the benefits of abstracting away persistence to a separate, discrete place; I was using repositories long before I knew it had a name, because it's common sense once you've experienced the problems that it solves.
So, like, I don't think a developer _needs_ to familiarize themselves with the "official names" of common design patterns. But it doesn't hurt, so long as you take them as what they are: patterns, not implementations. 2/2
@noboilerplate P.S., you'll notice I didn't mention any of the big four, because I feel like those four are often overly prescriptive of implementation. They don't _have to be_, but they are. But there are lots of design patterns, and looking at the general concept of patterns is, to my mind, more useful than examining four specific ones from a book.