The document emphasizes the importance of writing sustainable and maintainable code, highlighting that code can quickly become obsolete. It suggests principles for improving code quality, such as adhering to design concepts and keeping methods simple and comprehensible. The author encourages developers to continuously learn and refine their coding practices.

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

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

3. Let me
introduce
you to
someone…

6. No Tests.
Wrote his own framework.
500 line methods.
Used Singletons!

7. photo: Rob Allen (@akrabat)

9. REWRITE
ALL THE CODE!

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

14. How do we find
balance?
photo: Kalexanderson

15. Code has an
expiration date
photo: CarbonNYC

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

17. Code Evolves
photo by: kevin dooley

18. Languages evolve.
photo by: raneko

19. You evolve.
photo by: Kaptain Kobold

20. Complexity
kills
Comprehension
photo: osbornb

21. Bad Design
photo: miskan

22. Bad specs

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

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

25. The Solution™
photo: Ian Sane

26. Improve code

27. Improve code
make it easier to comprehend

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

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

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

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

32. Good Design
Concepts

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

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

35. Design Patterns
photo by halloweenstock

36. Composer

37. PIE
Proudly
Invented
Elsewhere

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

39. morrisonlevi/ardent
A library of collections for PHP

40. Readability
photo: Morgenland

41. paragraphs
photo: Trossachs Photography

42. whitespace

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

45. Object
Calisthenics
photo by: boston_public_library

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

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

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

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

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

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

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

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

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

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

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

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

61. Your turn.

62. Improve
yourself!

63. Read lots of
code!

64. Write simple
code.

65. Try Object Calisthenics
for a month.

66. Use someone
else’s code.

67. Share bite size
libraries.

68. Thank you.
http://slides.doh.ms
http://doh.ms
@rdohms
we are hiring!
https://joind.in/11594
please rate me!

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