The document discusses techniques for writing sustainable code over time, including testing code, following design principles like SOLID, using package managers, prioritizing readability, practicing object calisthenics, improving code through refactoring, and continually learning. The goal is to write code that is easy to comprehend, flexible, tested, and replaceable as needs change over time.

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

5. Lead Backend
Developer

6. Let me
introduce
you to
someone…

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

41. Composer

42. PIE
Proudly
Invented
Elsewhere

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

44. league/tactician
A flexible CommandBus implementation

45. Readability
photo: Morgenland

46. paragraphs
photo: Trossachs Photography

47. whitespace

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

50. Object
Calisthenics
photo by: boston_public_library

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

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

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

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

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

59. $component->repaint(false);

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

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

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

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

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

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

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

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

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

69. Your turn.

70. Improve
yourself!

71. Read lots of
code!

72. Write simple
code.

73. Try Object Calisthenics
for a month.

74. Use someone
else’s code.

75. Share bite size
libraries.

76. Thank you.
http://slides.doh.ms
http://doh.ms
@rdohms
we are hiring!
http://careers.symbid.com/
https://joind.in/talk/d3749

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