Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Speaker Deck
PRO
Sign in
Sign up for free
Why Every Element of SOLID is Wrong
Daniel Terhorst-North
PRO
January 20, 2017
Technology
127
92k
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
Rethinking Transformation
tastapod
PRO
1
44
CUPID - for joyful coding
tastapod
PRO
3
4.1k
agility at scale - a meeting of mindsets
tastapod
PRO
1
280
SWARMing into action
tastapod
PRO
0
280
Deliberate Advice
tastapod
PRO
3
1k
Governing Agile Delivery
tastapod
PRO
14
300
Complexity
tastapod
PRO
12
780
SWARMing
tastapod
PRO
25
2k
How to break the rules - Cucumber mix
tastapod
PRO
10
850
Other Decks in Technology
See All in Technology
miisan's career talk
mii3king
0
220
覗いてみよう!現場のスクラムチーム
tkredman
0
1k
スタートアップと技術選定と AWS
track3jyo
PRO
2
320
DOM Invader - prototype pollution対応の衝撃 - / DOM Invader - prototype pollution
okuken
0
110
音のような言葉 〜ちゃちゃっとチャットで楽しむちょっとしたコツ〜 / words like sounds
satoryu
1
1.3k
モブに早く慣れたい人のためのガイド / A Guide to Getting Started Quickly with Mob Programming
cybozuinsideout
PRO
2
1.7k
#JP_Stripes Sapporo Stripeの活用例を色々ご紹介します!
miu_crescent
0
110
MRTK3 - DataBinding and Theming 入門
futo23
0
180
機械学習システムアーキテクチャ入門 #1
asei
3
1.2k
Oracle Base Database Service 技術詳細
oracle4engineer
PRO
3
9k
The application of formal methods in Kafka reliability engineering
line_developers
PRO
0
150
リファインメントは楽しいかね?
kitamu_mu
1
390
Featured
See All Featured
WebSockets: Embracing the real-time Web
robhawkes
57
5.2k
Templates, Plugins, & Blocks: Oh My! Creating the theme that thinks of everything
marktimemedia
15
940
How to Ace a Technical Interview
jacobian
265
21k
Docker and Python
trallard
27
1.6k
Scaling GitHub
holman
451
140k
Reflections from 52 weeks, 52 projects
jeffersonlam
337
17k
Visualizing Your Data: Incorporating Mongo into Loggly Infrastructure
mongodb
29
4.3k
The Invisible Customer
myddelton
110
11k
Unsuck your backbone
ammeep
659
55k
The Invisible Side of Design
smashingmag
290
48k
Designing the Hi-DPI Web
ddemaree
272
32k
The Pragmatic Product Professional
lauravandoore
19
3k
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!