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
260
The Most Dangerous Phrase
tastapod
PRO
7
5.9k
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
540
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
TDD - Test Driven Drupal
opdavies
0
3k
YJIT Makes Rails 1.7x faster / RubyKaigi 2024
k0kubun
3
460
サービス開発におけるVue3とTypeScriptの親和性について
tsukuha
10
1.8k
DevRelによる信頼構築とデータ駆動で変わるエンジニア採用 / DevRel Trust Building to Data Driven Engineering Hiring
bobtani
1
130
生成AIがもたらす変革 / GitHubGalaxy_CyberAgent
cyberagentdevelopers
PRO
2
110
[PyconUS 2024] Having fun with Pydantic and pattern matching
enforcerpl
0
170
The depthes of profiling Ruby - RubyKaigi 2024
osyoyu
0
150
AWS CLIの起動が重くてつらいので aws-sdk-client-go を書いた / kamakura.go#6
fujiwara3
6
3.2k
能動学習のいろは:書籍「Human-in-the-Loop機械学習」3〜5章
hiroyoshiito
0
290
RailsConf 2024 Keynote "Startups on Rails in 2024"
irinanazarova
0
800
大規模言語モデル (LLM)における低精度数値表現
pfn
PRO
3
820
Exadata Database Service on Dedicated Infrastructure(ExaDB-D) UI スクリーン・キャプチャ集
oracle4engineer
PRO
2
1.7k
Featured
See All Featured
Statistics for Hackers
jakevdp
790
220k
The Straight Up "How To Draw Better" Workshop
denniskardys
228
130k
Become a Pro
speakerdeck
PRO
13
4.6k
5 minutes of I Can Smell Your CMS
philhawksworth
199
19k
Why You Should Never Use an ORM
jnunemaker
PRO
51
8.7k
Fontdeck: Realign not Redesign
paulrobertlloyd
76
4.9k
Learning to Love Humans: Emotional Interface Design
aarron
267
39k
Mobile First: as difficult as doing things right
swwweet
217
8.6k
Building a Scalable Design System with Sketch
lauravandoore
457
32k
How to train your dragon (web standard)
notwaldorf
75
5.2k
The Brand Is Dead. Long Live the Brand.
mthomps
49
30k
Let's Do A Bunch of Simple Stuff to Make Websites Faster
chriscoyier
501
140k
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!