Balancing Coupling in Software Design - Vlad Khononov - DDD Europe 2023

[@michaelploed]

This video should be a must-watch to everyone in software design & architecture

[@stephendgreen1502]

Excellent. Very clear. Very accurate.

[@tristanludowyk9579]

Great talk thank you!

[@christophercollett5665]

TL;DR: Pain = Strength * Volatility * Distance. Reduce one of them to 0 to minimize the pain of necessary coupling.

[@murillorocha5436]

Great presentation. Hope Vlad's book comes out soon.

[@LjuboThePro]

Good stuff.

[@deekay2091]

DDD hero ❤

[@ulfdellbrugge827]

would be better if it wasn't hx-properity but part of html6

[@djgreyjoy1495]

The presented coupling ontology seems to require more thought

[@usabilist]

It is a talent to speak for about one hour juggling with words but do not come to any practical application.

[@seNick7]

Last 20 minutes were all about practical implementations. The implications aren't revolutionary though

[@nichtverstehen2045]

nobody is worried about coupling like you. people just do their jobs. more over, in most situations it makes sense to ignore problems like coupling all together, because software development is not really driven by anything but freaking profit. end of story. non-profit projects just dream to get f...d aka bought.

[@fran_sanchez_yt]

Coupling (and bad developers) is one of the main reasons for a company to fail... Code becomes hard to change, a lot of cruft is required for every minor change and innovation and improvement is drastically reduced because the system is not malleable enough... People get tired and demotivated and leave... No one is going to get through a due diligence for an acquisition with such a pile of garbage.

[@cheesebusiness]

You are not experienced enough to realize that you have problems that waste or will waste the money of the business

[@nichtverstehen2045]

@@cheesebusiness how do you know anything about me? discussing opponent's personality is the last resort for those who has nothing else to backup their argument.