Loading video...

Video Failed to Load

Go Home

Morning bathrobe rant: Design Patterns.

148,927 views • 1 year ago •via X (Twitter)

10 Comments

Daniel's profile picture
Daniel1 year ago

It’s amazing how little you can say in a full 90 seconds

Home Bathroomware's profile picture
Home Bathroomware1 year ago

Transform your bathroom space with our stunning Clifton floating vanity! 🚽✨ Choose from various cabinet and handle finishes to match your style. Designed and made in Australia, just for you.

Foy Savas's profile picture
Foy Savas1 year ago

I used to disregard GoF's Design Patterns. But then you code them enough times and you're thankful for the names. What I still think sours the Design Patterns is that some devs treat the book's examples as strict interface specs.

Daryl Barnes's profile picture
Daryl Barnes1 year ago

The primary benefit of "Design Patterns" is that we programmers now have a common language to describe what we're doing in our programs. That's really all it is and that's awesome.

Jeremy Dean Lakey's profile picture
Jeremy Dean Lakey1 year ago

I've noticed that when devs read design patterns, their code initially gets worse (sometimes never recovers). This is probably why some view design patterns negatively.

Dad 3.0 👨‍👧‍👦 💻 📷 👨🏻‍🍳's profile picture
Dad 3.0 👨‍👧‍👦 💻 📷 👨🏻‍🍳1 year ago

The problem is every time those extreme people. Some years ago, it was the opposite, some thought you HAD to use them even before figuring out what was the problem. Not reading the book is ok, if you’re clever enough, the pattern will emerge. “Design patterns” after all are names associated with code structure.

XDF's profile picture
XDF1 year ago

The criticism is not "they're complicated." Some design patterns are ok as an abstract vocabulary. But they quickly become problematic when they are implemented literally. And they immediately become disastrous when they are treated as the atomic units of software architecture.

pavi2410's profile picture
pavi24101 year ago

uncle figured out the algorithm

TheRootless's profile picture
TheRootless1 year ago

Totally agree, I am 32 and a Staff Engineer, whenever I setup a new service I always make sure to set it up in a foundation of design patterns with clear documentation on the principles behind them. But... the newer engineers just dismiss it and start patching things randomly without following any philosophies😔

Leitz 💡's profile picture
Leitz 💡1 year ago

The original design patterns book was revolutionary. I always found it too academic and abstract though .@allenholub wrote a book with working Java examples called Holub on Patterns It has all the patterns from the original This book is great and is approachable by beginners

Related Videos