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
100k
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
How to bake a change
tastapod
PRO
0
250
The Most Dangerous Phrase
tastapod
PRO
7
5.8k
Rethinking Transformation
tastapod
PRO
1
280
CUPID - for joyful coding
tastapod
PRO
4
6.5k
agility at scale - a meeting of mindsets
tastapod
PRO
1
530
SWARMing into action
tastapod
PRO
0
360
Deliberate Advice
tastapod
PRO
3
1.3k
Governing Agile Delivery
tastapod
PRO
14
300
Complexity
tastapod
PRO
12
910
Other Decks in Technology
See All in Technology
Zero Data Loss Autonomous Recovery Service サービス概要
oracle4engineer
PRO
0
2k
5分で分かる(かもしれない) Vector engine for OpenSearch Serverless
tsukuboshi
1
370
社内での継続的な機械学習勉強会の開催のコツ
yudai00
2
380
生成AIと産業向けソフトウェアの自動生成 〜 ハノーバーメッセ2024より〜
kioto
2
410
Exadata Database Service on Dedicated Infrastructure(ExaDB-D) UI スクリーン・キャプチャ集
oracle4engineer
PRO
2
1.7k
Kaggleで学ぶ系列データのための深層学習モデリング
yu4u
7
1.7k
Secrets of a PowerShell "Guru"
guyrleech
1
120
成長をサポートするピープルマネジメントのやり方
sioncojp
9
1.5k
Cloudflare WorkersがPythonに対応したので試してみた
miura55
0
190
AI JIMY - 登壇(インストール編)
hanacchi
0
150
DevRelによる信頼構築とデータ駆動で変わるエンジニア採用 / DevRel Trust Building to Data Driven Engineering Hiring
bobtani
1
120
パスワードを保存しますか?
hanacchi
0
240
Featured
See All Featured
Why Our Code Smells
bkeepers
PRO
331
56k
Building Adaptive Systems
keathley
32
1.9k
Keith and Marios Guide to Fast Websites
keithpitt
408
22k
4 Signs Your Business is Dying
shpigford
176
21k
The Psychology of Web Performance [Beyond Tellerrand 2023]
tammyeverts
15
1.6k
I Don’t Have Time: Getting Over the Fear to Launch Your Podcast
jcasabona
23
1.7k
The Cult of Friendly URLs
andyhume
74
5.7k
Practical Orchestrator
shlominoach
183
9.8k
jQuery: Nuts, Bolts and Bling
dougneiner
60
7.2k
Imperfection Machines: The Place of Print at Facebook
scottboms
261
12k
From Idea to $5000 a Month in 5 Months
shpigford
377
45k
Fight the Zombie Pattern Library - RWD Summit 2016
marcelosomers
228
16k
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!