As developers we write code everyday, only to frown at it a week after that. Why do we have such a hard time with code written by others and ourselves, this raging desire to rewrite everything we see? Writing code that survives the test of time and self judgment is a matter of clarity and simplicity. Let's talk about growing, learning and improving our code with calisthenics, readability and good design.

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…

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

10. photo: Rob Allen (@akrabat)

12. REWRITE
ALL THE CODE!
image: hyperboleandahalf

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

17. How do we find
balance?
photo: Kalexanderson

18. Code has an
expiration date
photo: CarbonNYC

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

20. Code Evolves
photo by: kevin dooley

21. Languages evolve.
photo by: raneko

22. You evolve.
photo by: Kaptain Kobold

23. Complexity
kills
Comprehension
photo: osbornb

24. Bad Design
photo: miskan

25. Bad specs

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

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

28. The Solution™
photo: Ian Sane

29. Improve code

30. Improve code
make it easier to comprehend

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

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

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

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

35. Testing
photo by: jeffkrause

36. Good Design
Concepts

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

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

39. Design Patterns
photo by halloweenstock

40. Package
Managers
photo by cocoachuchu.etsy.com

41. PIE
Proudly
Invented
Elsewhere

42. Readability
photo: Morgenland

43. paragraphs
photo: Trossachs Photography

44. whitespace

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

47. Object
Calisthenics
photo by: boston_public_library

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

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

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

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

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

56. $component->repaint(false);

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

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

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

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

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

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

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

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

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

66. Your turn.

67. Improve
yourself!

68. Read lots of
code!

69. Write simple
code.

70. Try Object Calisthenics
for a month.

71. Use someone
else’s code.

72. Share bite size
libraries.

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

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