Тёмный

Loose & Tight Coupling: Why Code is Hard to Change 

Bran van der Meer
Подписаться 3,7 тыс.
Просмотров 6 тыс.
50% 1

🍝 I'll get to the core of why code bases can turn into big balls of mud: tight coupling. Managing tight and loose coupling will allow you to come up with high quality code and solution designs! I'll talk about the mechanisms and design patterns to take control of and reduce tight coupling! 🔗
Source code used in the video: gist.github.com/branneman/584...
Interface-First Programming: • Interface-First Progra...

Наука

Опубликовано:

 

2 ноя 2022

Поделиться:

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист
Посмотреть позже
Комментарии : 15   
@KamalMettananda
@KamalMettananda 4 месяца назад
One of the best videos to get a clear understanding about the big picture. Thanks a lot.
@santhoshninjakhan7880
@santhoshninjakhan7880 4 месяца назад
This channel is gold mine for Developers thank you soo much! Please make more videos thanks once again for your valuable lessons to us
@vinlandish555
@vinlandish555 2 месяца назад
This was very useful!
@riquesse3185
@riquesse3185 15 дней назад
I'm a bit confused about why there is loose coupling between A and B in the example at 2:33. I thought there was no coupling between A and B since they are not dependent on each other. By the way, great video!
@tanzimchowdhury320
@tanzimchowdhury320 Год назад
Thank you Bran for your high-quality content :) Please keep making videos like these.
@ericsiddiq7634
@ericsiddiq7634 10 месяцев назад
Excellent explanation ❤
@andreyshedko6155
@andreyshedko6155 Год назад
Would be nice to see similar videos about SOLID principles
@branvandermeer
@branvandermeer Год назад
Yes, they're in the planning!
@cidhighwind8590
@cidhighwind8590 Год назад
Great video. And cool shirt!
@kozas0
@kozas0 Год назад
I like how you mention "both sides of the story" at the end, and that if you add too many interfaces and decouple too much there might be consequences. I have seen that on a codebase with DI + interfaces for pretty much everything + multiple impementations, where the code was nearly untracable unless you used a debugger. DI is a great decoupling tool especially when you have a framework that supports it, like Spring or Angular, so you don't have to pass along objects all around your object graph just to feed them somewhere. Also worth mentioning imo is that in stable codebases (or even more in "legacy" ones) the general consensus is that you want to move as little parts as possible, and that kind of colludes with the idea to refactor a codebase to loose its coupling.
@branvandermeer
@branvandermeer Год назад
Adding too many interfaces and decoupling too much will usually lead to more complexity indeed. It's always a checks and balances game!
@oleksii_gozha
@oleksii_gozha Год назад
Thank you for high quality content. Could you share some thoughts on freelancing in very specific language ABAP for SAP. It is used in 90% of S&P firms and external people are quiet exensive. So I thought is would be a good idea to become also an external self employed Abap developer. On my Region every company is using German on documentation and on code itself (methods name for example ), so without German no other cheaper outsourced company can not provide service to them. What do you think about such unpopular languages (Abap , cobol) where there is some demand but there are almost no people ? O like your content
@branvandermeer
@branvandermeer Год назад
I'm not familiar with these languages, and such I can't really speak of it. You kind of answered your own question though: betting on specialising in only a very obscure language probably is a more risky career strategy. But if you develop broadly-applicable skills, that might lower the risk of not being able to find a job in the future.
@edgeeffect
@edgeeffect 10 месяцев назад
Watching this on my phone with my old man's eyes.... the code examples are unreadable... a big chunky font or a zoomed in screen would be better... thanks.
@branvandermeer
@branvandermeer 10 месяцев назад
Sorry! Unfortunately youtube does not allow changing video after the fact, so all I can recommend is reading the code on the gist, or re-watching on a desktop resolution. gist.github.com/branneman/584f31eb298751ca65b14220e7bb55ce
Далее
How I write High Quality Unit Tests
18:34
Просмотров 2,5 тыс.
Coupling and Cohesion Explained
11:43
Просмотров 3,6 тыс.
IQ Level: 10000
00:10
Просмотров 7 млн
Dependency Injection, The Best Pattern
13:16
Просмотров 780 тыс.
Software Architecture Tips I WISH I Knew Sooner
18:04
Introducing 0DE5
39:38
Просмотров 3,6 тыс.
The Simplest Design Pattern: Facade
8:43
Просмотров 3,3 тыс.
What is Dependency Injection?
6:48
Просмотров 114 тыс.
Dependency Injection, simplified
9:55
Просмотров 3,9 тыс.
Coupling and Cohesion to Write BETTER C# CODE
17:19
Просмотров 2,6 тыс.
Driver/Navigator style of Pair Programming
15:17
Просмотров 2,3 тыс.
How principled coders outperform the competition
11:11
iPhone 16 - 20+ КРУТЫХ ИЗМЕНЕНИЙ
5:20