Solid Development

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

5 Principles to keep in mind and apply when you are writing code.
Photo by Steffenz

Single Responsibility Principle
Open/Closed Principle
LiskovSubstitution Principle
Interface Segregation Principle
Dependency Inversion Principle
Photo by ilkegb

Photo by TomásRotger
“A class should have one, and only one, reason to change.”

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

“Derived classes must be substitutable for their base classes.”
Photo by Jeremy Brooks

“Make fine grained interfaces that are client specific.”
Photo by nosha

“Depend on abstractions, not on concretions.”
Photo by schoeband

We can talk about your feelings. Or code. Probably mostly code.
Photo by JakobMontrasio

Uncle Bob’s Principles of OODhttp://bit.ly/65ncKX
Hanselminutes #145 – Hanselman & Uncle Bob discuss SOLIDhttp://bit.ly/7inDit
Motivational Posters by Derick Baileyhttp://bit.ly/4ZE5RV
Code Examples & Tonight’s Presentation
http://bit.ly/3nOGkq
Photo by Daniel Leininger

Solid Development

by Chris Deweese on Jan 24, 2010

Accessibility

Categories

Tags

Upload Details

Usage Rights

2 Embeds 135

Statistics

Solid Development — Presentation Transcript

http://christopherdeweese.com	130
http://www.slideshare.net	5