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

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

3. Let me
introduce
you to
someone…

6. No Tests.
shhh.. don’t tell Grumpy.
Wrote his own framework.
.. and used it.
Used Singletons!
.. and every other anti-pattern out there.
500 line methods.
… not even methods, they were functions

7. photo: Rob Allen (@akrabat)

9. REWRITE
ALL THE CODE!

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

14. How do we find
balance?
photo: Kalexanderson

15. Code has an
expiration date
photo: CarbonNYC

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

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
photo by: John 'K'
source: Urban dictionary

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.
photo by: John 'K'
source: Urban dictionary

25. The Solution™
photo: Ian Sane

26. Improve code

27. make it easier to comprehend
Improve code

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

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

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

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

32. Testing
photo by: jeffkrause

33. Good Design
Concepts

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

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

36. photo by halloweenstock
Design Patterns

37. Composer

38. PIE
Proudly
Invented
Elsewhere

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

40. morrisonlevi/ardent
A library of collections for PHP

41. Readability
photo: Morgenland

42. paragraphs
photo: Trossachs Photography

43. whitespace

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

46. Object
Calisthenics
photo by: boston_public_library

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

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

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

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

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

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

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

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

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

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

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

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

62. Your turn.

63. Improve
yourself!

64. Read lots of
code!

65. Write simple
code.

66. Try Object Calisthenics
for a month.

67. Use someone
else’s code.

68. Share bite size
libraries.

69. Thank you.
@rdohms
https://joind.in/12734
http://doh.ms
http://slides.doh.ms
please rate me!

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