SOLID Development

Chris Deweese

Photo by basswulf

“The truth is, every developer is a little bit of an architect. Some of us just care a little more than the next guy.” (Lessons Learned About Being a Software Architect)

Photo by lrargerich

Photo by Steffenz

5 Principles to keep in

mind and apply when you

are writing code.

Single Responsibility PrincipleOpen/Closed Principle

Liskov Substitution Principle

Interface Segregation Principle

Dependency Inversion PrinciplePhoto by ilkegb

“A class should have one, and only one, reason to change.”

Photo by Tomás Rotger

Single Responsibility Principle

Open/Closed PrincipleLiskov Substitution Principle

Interface Segregation Principle

Dependency Inversion Principle

“You should be able to extend a classes behavior, without modifying it.”

Photo by laurenmarek

Single Responsibility Principle

Open/Closed Principle

Liskov Substitution PrincipleInterface Segregation Principle

Dependency Inversion Principle

“Derived classes must be substitutable for their base classes.”

Photo by Jeremy Brooks

Single Responsibility Principle

Open/Closed Principle

Liskov Substitution Principle

Interface Segregation PrincipleDependency Inversion Principle

“Make fine grained interfaces that are client specific.”

Photo by nosha

Single Responsibility Principle

Open/Closed Principle

Liskov Substitution Principle

Interface Segregation Principle

Dependency Inversion Principle

“Depend on abstractions, not on concretions.”

Photo by schoeband

We can talk about your feelings. Or code. Probably mostly code.

Photo by Jakob Montrasio

Uncle Bob’s Principles of OOD http://bit.ly/65ncKX

Hanselminutes #145 – Hanselman & Uncle Bob discuss SOLID http://bit.ly/7inDit

Motivational Posters by Derick Bailey http://bit.ly/4ZE5RV

Code Examples & Tonight’s Presentationhttp://bit.ly/3nOGkq

Photo by Daniel Leininger