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.
Rafael Dohms
or @rdohms on twitter

4.
Developer
Herder
at AmsterdamPHP

5.
Lead Backend
Developer
at Symbid

6.
Let me
tell you about
someone else…

7.
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

8.
photo: Rob Allen (@akrabat)

9.
REWRITE
ALL THE CODE!
image: hyperboleandahalf

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

11.
How do we find
balance?
photo: Kalexanderson

12.
Code has an
expiration date
photo: CarbonNYC

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

14.
Code Evolves
photo by: kevin dooley

15.
Languages evolve.
photo by: raneko

16.
You evolve.
photo by: Kaptain Kobold

17.
Complexity
kills
Comprehension
photo: osbornb

18.
Bad Design
photo: miskan

19.
Bad specs

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

21.
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'

22.
The Solution™
photo: Ian Sane

23.
Improve code

24.
Improve code
make it easier to comprehend

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

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

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

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

29.
Testing
photo by: jeffkrause

30.
Good Design
Concepts

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

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

33.
Design Patterns
photo by halloweenstock

34.
Package
Managers
photo by cocoachuchu.etsy.com

35.
PIE
Proudly
Invented
Elsewhere

36.
Readability
photo: Morgenland

37.
paragraphs
photo: Trossachs Photography

38.
whitespace

39.
R&D Team for MIH/Naspers
São Paulo
Cape Town

40.
Object
Calisthenics
photo by: boston_public_library

41.
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

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

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

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

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

46.
$component->repaint(false);

47.
$component->repaint( new Animate(false) );

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

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

50.
if($sx >= $sy) {
if ($sx > $strSysMatImgW) {
$ny = $strSysMatImgW * $sy / $sx;
$nx = $strSysMatImgW;
}
if ($ny > $strSysMatImgH) {
$nx = $strSysMatImgH * $sx / $sy;
$ny = $strSysMatImgH;
}
}

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

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

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

54.
#9
Don’t use getters
and setters.
photo by: justinliew

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

56.
Your turn.

57.
Improve
yourself!

58.
Read lots of
code!

59.
Write simple
code.

60.
Try Object Calisthenics
for a month.

61.
Use someone
else’s code.

62.
Share bite size
libraries.

63.
Thank you.
http://slides.doh.ms
http://doh.ms
@rdohms
we are hiring!
http://careers.symbid.com

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