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
98
How to bake a change
tastapod
PRO
0
390
The Most Dangerous Phrase
tastapod
PRO
7
6k
Rethinking Transformation
tastapod
PRO
1
320
CUPID - for joyful coding
tastapod
PRO
4
6.9k
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
業務ヒアリングと知識の呪い
tamai_63
0
290
入社半年(合計1年)でGoogle Cloud 認定を全冠した秘訣🤫
risatube
1
210
テストコードの品質を客観的な数値で担保しよう〜Mutation Testのすすめ〜
ysknsid25
12
3.2k
スタサプ ForSCHOOLアプリのシンプルな設計
recruitengineers
PRO
3
570
KubeVirt Networking ONIC 2024
orimanabu
3
540
Case Study: Concurrent Counting
ennael
PRO
0
120
プロダクト開発の貢献をアピールするための目標設計や認知活動 / Goal design and recognition activities to promote product development contributions.
oomatomo
5
860
ゼロから実装まで!機械学習入門
natsuki0726
0
180
電子辞書にステータスバーを実装する
puhitaku
0
100
Grafana エコシステムの活用事例 on ABEMA
tetsuya28
2
180
LINE-ChatGPT 倫理問題を整理する全力肯定彼氏くん [LuC4]に訪れたサービス開始以来の最大の危機
o_ob
1
150
Webセキュリティのあるきかた
akiym
32
10k
Featured
See All Featured
Producing Creativity
orderedlist
PRO
341
39k
Visualization
eitanlees
143
15k
Fashionably flexible responsive web design (full day workshop)
malarkey
404
65k
Creatively Recalculating Your Daily Design Routine
revolveconf
217
12k
Building a Scalable Design System with Sketch
lauravandoore
459
32k
Git: the NoSQL Database
bkeepers
PRO
425
64k
Being A Developer After 40
akosma
84
590k
Building an army of robots
kneath
302
42k
Agile that works and the tools we love
rasmusluckow
327
21k
Building Better People: How to give real-time feedback that sticks.
wjessup
362
19k
How to Ace a Technical Interview
jacobian
275
23k
Designing for humans not robots
tammielis
249
25k
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!