1.
Writing code
that lasts.
Rafael Dohms
@rdohms
photo: djandyw.com
#ocforphp

2.
Writing code
you won’t hate tomorrow.
Rafael Dohms
@rdohms
photo: djandyw.com
#ocforphp

3.
Let me
introduce
you to
someone…

4.
No Tests.
Wrote his own framework.
500 line methods.
Used Singletons!
shhh.. don’t tell Grumpy.
.. and used it.
.. and every other anti-pattern out there.
… not even methods, they were functions

5.
photo: Rob Allen (@akrabat)

6.
REWRITE
ALL THE CODE!
image: hyperboleandahalf

7.
Real Developers,
SHIP STUFF.
photo: Glyn Lowe Photoworks

8.
How do we find
balance?
photo: Kalexanderson

9.
Code has an
expiration date
photo: CarbonNYC

10.
Code is
perishable, it rots.
photo by: massdistraction

11.
Code Evolves
photo by: kevin dooley

12.
Languages evolve.
photo by: raneko

13.
You evolve.
photo by: Kaptain Kobold

14.
Complexity
kills
Comprehension
photo: osbornb

15.
Bad Design
photo: miskan

16.
Bad specs

17.
NIH
source: Urban dictionary
photo by: John 'K'

18.
NIH
| nɒt ɪnˈventɪd hɪə |
Not Invented Here —The German art of humiliating any technology,
agricultural product, or (medical) scientific work that has not been
invented or produced in Germany, Switzerland, or Austria.
source: Urban dictionary
photo by: John 'K'

19.
The Solution™
photo: Ian Sane

20.
Improve code

21.
Improve code
make it easier to comprehend

22.
Improve code
make it easier to comprehend
make it flexible

23.
Improve code
make it easier to comprehend
make it flexible
make it tested

24.
Improve code
make it easier to comprehend
make it flexible
make it tested
make it easier to replace, refactor

25.
Improve code
make it easier to comprehend
make it flexible
make it tested
make it easier to replace, refactor
make it not exist

26.
Testing
photo by: jeffkrause

27.
Good Design
Concepts

28.
SOLID
Single Responsibility
Open and Close
Liskov substitution
Interface Segregation
Dependency Inversion
photo by j_regan

29.
photo by lofink
STUPID
Singleton
Tight Coupling
Untestability
Premature Optimization
Indescriptive Naming
Duplication

30.
Design Patterns
photo by halloweenstock

31.
Composer

32.
PIE
Proudly
Invented
Elsewhere

33.
guzzlehttp/guzzle
HTTP client for RESTful API clients
photo by j_regan

34.
league/tactician
A flexible CommandBus implementation

35.
Readability
photo: Morgenland

36.
paragraphs
photo: Trossachs Photography

37.
whitespace

38.
R&D Team for MIH/Naspers
São PauloCape Town

39.
Object
Calisthenics
photo by: boston_public_library

40.
Calisthenics
/ˌkaləsˈTHeniks/
Calisthenics are a form of dynamic exercise consisting of a variety of
simple, often rhythmical, movements, generally using minimal
equipment or apparatus.
photo by: boston_public_library

41.
Its about perception,
not rules or standards photo by: david_a_l

42.
#1
Only one
indentation level
per method.
photo by: justinliew

43.
#2
Do not
use else
photo by: justinliew

44.
#3
Wrap primitive
types, if they
contain behavior
photo by: justinliew

45.
#4
Only one
-> per line
photo by: justinliew

46.
#5
Do not
abbreviate.
photo by: justinliew

47.
#6
Keep your
classes small.
photo by: justinliew

48.
#7
Limit your
instance variables
to less then 5
photo by: justinliew

49.
#8
Use first class
collections
photo by: justinliew

50.
#9
Use getters
and setters.
photo by: justinliew

51.
#10
Document
your code.
photo by: justinliew

52.
Your turn.

53.
Improve
yourself!

54.
Read lots of
code!

55.
Write simple
code.

56.
Try Object Calisthenics
for a month.

57.
Use someone
else’s code.

58.
Share bite size
libraries.

59.
Thank you.
http://slides.doh.ms
http://doh.ms
@rdohms
we are hiring!
http://tech.sym.bid/jobs

60.
http://l.doh.ms/oc-material
Video recording
Slides
Books
Resources on
Object Calisthenics