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
Dohmsor @rdohms on twitter

4. Developer
Herder

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

8. photo: Rob Allen (@akrabat)

10. REWRITE
ALL THE CODE!
image: hyperboleandahalf

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

15. How do we find
balance?
photo: Kalexanderson

16. Code has an
expiration date
photo: CarbonNYC

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

18. Code Evolves
photo by: kevin dooley

19. Languages evolve.
photo by: raneko

20. You evolve.
photo by: Kaptain Kobold

21. Complexity
kills
Comprehension
photo: osbornb

22. Bad Design
photo: miskan

23. Bad specs

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

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

26. The Solution™
photo: Ian Sane

27. Improve code

28. Improve code
make it easier to comprehend

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

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

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

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

33. Testing
photo by: jeffkrause

34. Good Design
Concepts

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

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

37. Design Patterns
photo by halloweenstock

38. Package
Managers

39. Composer

40. PIE
Proudly
Invented
Elsewhere

41. guzzlehttp/guzzle
HTTP client for RESTful API clients

42. league/tactician
A flexible CommandBus implementation

43. Readability
photo: Morgenland

44. paragraphs
photo: Trossachs Photography

45. whitespace

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

48. Object
Calisthenics
photo by: boston_public_library

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

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

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

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

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

57. $component->repaint(false);

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

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

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

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

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

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

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

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

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

67. Your turn.

68. Improve
yourself!

69. Read lots of
code!

70. Write simple
code.

71. Try Object Calisthenics
for a month.

72. Use someone
else’s code.

73. Share bite size
libraries.

74. Thank you.
http://slides.doh.ms
http://doh.ms
@rdohms
https://joind.in/talk/6236e

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