Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Why Every Element of SOLID is Wrong
Search
Daniel Terhorst-North
PRO
January 20, 2017
Technology
130
110k
Why Every Element of SOLID is Wrong
Five minute Ignite-style talk from PubConf London 2016
Daniel Terhorst-North
PRO
January 20, 2017
Tweet
Share
More Decks by Daniel Terhorst-North
See All by Daniel Terhorst-North
The best programmer I know
tastapod
PRO
2
110
How to bake a change
tastapod
PRO
0
400
The Most Dangerous Phrase
tastapod
PRO
7
6k
Rethinking Transformation
tastapod
PRO
1
330
CUPID - for joyful coding
tastapod
PRO
4
7k
agility at scale - a meeting of mindsets
tastapod
PRO
1
560
SWARMing into action
tastapod
PRO
0
370
Deliberate Advice
tastapod
PRO
3
1.4k
Governing Agile Delivery
tastapod
PRO
14
300
Other Decks in Technology
See All in Technology
AIとともに歩んだライブラリアップデートの道のり/ vue-fes-japan-2024-link-and-motivation
lmi
2
2.5k
自然言語処理を役立てるのはなぜ難しいのか
pfn
PRO
17
4.6k
20241017_俺たちは雰囲気で scope をやっているけどもうちょっとなんとかならんのか?
tokai235
0
420
いまいまMySQL2024 @ OSC Nagaoka
sakaik
3
310
Overview of file type identifiers
ange
0
150
巨大企業でDX革新を起こすということ BTCONJP 2024
yamaken66
1
490
Introduction to Indistinguishability/Ideal Obfuscation (iO)
sorasuegami
0
110
Delta Commit…の最近...
akuwano
2
140
Kubernetes Summit 2024 Keynote:104 在 GitOps 大規模實踐中的甜蜜與苦澀
yaosiang
0
130
さくっと実践!Postmanを活用した高品質で持続可能なAPI管理
yokawasa
5
370
暴カワでビデオシンセサイザーを導入する技術
yuchi
2
130
LeSS Yoake 2024 スポンサーセッション
riki_hiraoka
0
240
Featured
See All Featured
Designing Experiences People Love
moore
138
23k
Statistics for Hackers
jakevdp
796
220k
10 Git Anti Patterns You Should be Aware of
lemiorhan
653
59k
Git: the NoSQL Database
bkeepers
PRO
425
64k
Facilitating Awesome Meetings
lara
49
6k
Optimising Largest Contentful Paint
csswizardry
31
2.9k
Faster Mobile Websites
deanohume
304
30k
Unsuck your backbone
ammeep
668
57k
StorybookのUI Testing Handbookを読んだ
zakiyama
26
5.2k
Build your cross-platform service in a week with App Engine
jlugia
229
18k
Docker and Python
trallard
40
3k
Building Applications with DynamoDB
mza
90
6k
Transcript
Why Every Single Element of SOLID is Wrong! Dan North
@tastapod
Single Responsibility Open/Closed Liskov Substitution Interface Segregation Dependency Inversion
Single Responsibility Principle “one reason to change” “only do one
thing”
Single Responsibility Principle What is a single responsibility anyway? ETL:
three responsibilities or one? How can you predict what is going to change? Pointlessly Vague Principle
Single Responsibility Principle Simple code is easy to reason about
Can easily do several related things Refactor until it Fits In Your Head Write simple code
Open-Closed Principle Open for extension, closed for modification “When requirements
change, extend behaviour by adding new code, not changing code that works”
Open-Closed Principle Open for extension, closed for modification “When requirements
change, the existing code is now wrong! so replace it with code that works” Cruft Accretion Principle
Open-Closed Principle Simple code is easy to change Simple code
is easy to test Simple code is both open and closed Write simple code!
Liskov Substitution Principle “Strong behavioural subtyping” Substitution with a subtype
preserves all “desirable properties” of the original type “Provably undecidable” but useful
Liskov Substitution Principle “There is nothing quite so useless, as
doing with great efficiency, something that should not be done at all.” Stuck in is-a and has-a modelling mindset Drucker’s Warning Principle
Liskov Substitution Principle What about acts-like-a, can-be-used-as-a? Composition is simpler
than inheritance Try to avoid object hierarchies altogether Write simple code!
Interface Segregation Principle Many small interfaces are better than one
big object Design small, role-based interfaces No client depends on methods it doesn’t use
Interface Segregation Principle Practically anything is better than one big
object Design small, role-based classes No client depends on methods it doesn’t use Stable Door Principle This is already true!! —>
Interface Segregation Principle Don’t write big objects in the first
place! Write code that Fits In Your Head If a class needs lots of interfaces, simplify the class! Write simple code!
Dependency Inversion Principle High-level modules should not depend on lower-level
modules Abstractions (e.g. interfaces) should not depend on details (e.g. concrete implementations)
Dependency Inversion Principle Reuse is overrated, design for use! DIP
leads to a different kind of dependency, dependency on DI frameworks! Wrong Goal Principle
Dependency Inversion Principle See how far you get combining simple
classes new is the new new! Assemble into small components that Fit In Your Head Write simple code!
Single Responsibility Open/Closed Liskov Substitution Interface Segregation Dependency Inversion
Single Responsibility Open/Closed Liskov Substitution Interface Segregation Dependency Inversion Too
much to remember!
Single Responsibility Open/Closed Liskov Substitution Interface Segregation Dependency Inversion Write
simple code!