Загрузка видео...

Не удалось загрузить видео

На главную

Morning bathrobe rant: Design Patterns.

148,927 просмотров • 1 год назад •via X (Twitter)

Комментарии: 10

Фото профиля Daniel
Daniel1 год назад

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

Фото профиля Home Bathroomware
Home Bathroomware1 год назад

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
Foy Savas1 год назад

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
Daryl Barnes1 год назад

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
Jeremy Dean Lakey1 год назад

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 👨‍👧‍👦 💻 📷 👨🏻‍🍳
Dad 3.0 👨‍👧‍👦 💻 📷 👨🏻‍🍳1 год назад

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
XDF1 год назад

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
pavi24101 год назад

uncle figured out the algorithm

Фото профиля TheRootless
TheRootless1 год назад

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 💡
Leitz 💡1 год назад

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

Похожие видео