The document discusses best practices for writing sustainable and maintainable code, emphasizing the importance of comprehensibility, flexibility, and testing. It presents various design principles and rules for code organization, such as limiting indentation levels and keeping classes small. The author encourages continuous improvement through reading, writing, and sharing code.

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
Bella

6. photo: Rob Allen (@akrabat)

8. REWRITE
ALL THE CODE!
image: hyperboleandahalf

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

12. How do we find
balance?
photo: Kalexanderson

13. Code has an
expiration date
photo: CarbonNYC

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

15. Code Evolves
photo by: kevin dooley

16. Languages evolve.
photo by: raneko

17. You evolve.
photo by: Kaptain Kobold

18. Complexity
kills
Comprehension
photo: osbornb

19. Bad Design
photo: miskan

20. Bad specs

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
make it easier to comprehend
make it flexible
make it tested
make it easier to replace, refactor
make it not exist

24. Testing
photo by: jeffkrause

25. Good Design
Concepts

26. SOLID
Single Responsibility
Open and Close
Liskov substitution
Interface Segregation
Dependency Inversion

27. STUPID
Singleton
Tight Coupling
Untestability
Premature Optimization
Indescriptive Naming
Duplication

28. Design Patterns
photo by halloweenstock

29. Package
Managers

30. Composer

31. PIE
Proudly
Invented
Elsewhere

32. Readability
photo: Morgenland

33. paragraphs
photo: Trossachs Photography

34. whitespace

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

37. Object
Calisthenics
photo by: boston_public_library

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

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

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

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

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

44. $component->repaint(false);

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

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

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

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

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

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

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

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

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

54. Your turn.

55. Improve
yourself!

56. Read lots of
code!

57. Write simple
code.

58. Try Object Calisthenics
for a month.

59. Use someone
else’s code.

60. Share bite size
libraries.

61. Thank you.
http://slides.doh.ms
http://doh.ms
@rdohms
https://joind.in/talk/745ec

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