Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Writing code
that lasts.
Rafael Dohms

@rdohms
photo: djandyw.com
#ocforphp
Writing code 

you won’t hate tomorrow.
Rafael Dohms

@rdohms
photo: djandyw.com
#ocforphp
Rafael
Dohmsor @rdohms on twitter
Developer

Herder
No Tests.
Wrote his own framework.
500 line methods.
Used Singletons!
shhh.. don’t tell Grumpy.
.. and used it.
.. and eve...
photo: Rob Allen (@akrabat)
REWRITE
ALL THE CODE!
image: hyperboleandahalf
Real Developers,
SHIP STUFF.
photo: Glyn Lowe Photoworks
How do we find
balance?
photo: Kalexanderson
Code has an
expiration date
photo: CarbonNYC
Code is
perishable, it rots.
photo by: massdistraction
Code Evolves
photo by: kevin dooley
Languages evolve.
photo by: raneko
You evolve.
photo by: Kaptain Kobold
Complexity 

kills
Comprehension
photo: osbornb
Bad Design
photo: miskan
Bad specs
NIH
source: Urban dictionary
photo by: John 'K'
NIH
| nɒt ɪnˈventɪd hɪə |

Not Invented Here —The German art of humiliating any technology,
agricultural product, or (medi...
The Solution™
photo: Ian Sane
Improve code
Improve code
make it easier to comprehend
Improve code
make it easier to comprehend
make it flexible
Improve code
make it easier to comprehend
make it flexible
make it tested
Improve code
make it easier to comprehend
make it flexible
make it tested
make it easier to replace, refactor
Improve code
make it easier to comprehend
make it flexible
make it tested
make it easier to replace, refactor
make it not e...
Testing
photo by: jeffkrause
Good Design
Concepts
SOLID
Single Responsibility

Open and Close

Liskov substitution

Interface Segregation

Dependency Inversion
STUPID
Singleton

Tight Coupling

Untestability

Premature Optimization

Indescriptive Naming

Duplication
Design Patterns
photo by halloweenstock
Package
Managers
Composer
PIE
Proudly

Invented

Elsewhere
guzzlehttp/guzzle
HTTP client for RESTful API clients
league/tactician
A flexible CommandBus implementation
Readability
photo: Morgenland
paragraphs
photo: Trossachs Photography
whitespace
R&D Team for MIH/Naspers
São PauloCape Town
Object
Calisthenics
photo by: boston_public_library
Calisthenics
/ˌkaləsˈTHeniks/
Calisthenics are a form of dynamic exercise consisting of a variety of
simple, often rhythmi...
Its about perception,
not rules or standards photo by: david_a_l
#1
Only one
indentation level
per method.
photo by: justinliew
#2
Do not 

use else
photo by: justinliew
#3
Wrap primitive
types, if they
contain behavior
photo by: justinliew
$component->repaint(false);
$component->repaint( new Animate(false) );
#4
Only one 

-> per line
photo by: justinliew
#5
Do not
abbreviate.
photo by: justinliew
if($sx >= $sy) {
if ($sx > $strSysMatImgW) {
$ny = $strSysMatImgW * $sy / $sx;
$nx = $strSysMatImgW;
}
if ($ny > $strSysMa...
#6
Keep your
classes small.
photo by: justinliew
#7
Limit your
instance variables
to less then 5
photo by: justinliew
#8
Use first class
collections
photo by: justinliew
#9
Don’t use getters
and setters.
photo by: justinliew
#10
Document
your code.
photo by: justinliew
Your turn.
Improve
yourself!
Read lots of
code!
Write simple
code.
Try Object Calisthenics
for a month.
Use someone
else’s code.
Share bite size
libraries.
Thank you.
http://slides.doh.ms
http://doh.ms
@rdohms
https://joind.in/talk/6236e
http://l.doh.ms/oc-material
Video recording
Slides
Books
Resources on 

Object Calisthenics
“Writing code that lasts” … or writing code you won’t hate tomorrow. - #PHPSRB16
“Writing code that lasts” … or writing code you won’t hate tomorrow. - #PHPSRB16
“Writing code that lasts” … or writing code you won’t hate tomorrow. - #PHPSRB16
“Writing code that lasts” … or writing code you won’t hate tomorrow. - #PHPSRB16
“Writing code that lasts” … or writing code you won’t hate tomorrow. - #PHPSRB16
“Writing code that lasts” … or writing code you won’t hate tomorrow. - #PHPSRB16
“Writing code that lasts” … or writing code you won’t hate tomorrow. - #PHPSRB16
“Writing code that lasts” … or writing code you won’t hate tomorrow. - #PHPSRB16
“Writing code that lasts” … or writing code you won’t hate tomorrow. - #PHPSRB16
“Writing code that lasts” … or writing code you won’t hate tomorrow. - #PHPSRB16
Upcoming SlideShare
Loading in …5
×

“Writing code that lasts” … or writing code you won’t hate tomorrow. - #PHPSRB16

1,059 views

Published on

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.

Published in: Technology

“Writing code that lasts” … or writing code you won’t hate tomorrow. - #PHPSRB16

  1. 1. Writing code that lasts. Rafael Dohms
 @rdohms photo: djandyw.com #ocforphp
  2. 2. Writing code 
 you won’t hate tomorrow. Rafael Dohms
 @rdohms photo: djandyw.com #ocforphp
  3. 3. Rafael Dohmsor @rdohms on twitter
  4. 4. Developer
 Herder
  5. 5. 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
  6. 6. photo: Rob Allen (@akrabat)
  7. 7. REWRITE ALL THE CODE! image: hyperboleandahalf
  8. 8. Real Developers, SHIP STUFF. photo: Glyn Lowe Photoworks
  9. 9. How do we find balance? photo: Kalexanderson
  10. 10. Code has an expiration date photo: CarbonNYC
  11. 11. Code is perishable, it rots. photo by: massdistraction
  12. 12. Code Evolves photo by: kevin dooley
  13. 13. Languages evolve. photo by: raneko
  14. 14. You evolve. photo by: Kaptain Kobold
  15. 15. Complexity 
 kills Comprehension photo: osbornb
  16. 16. Bad Design photo: miskan
  17. 17. Bad specs
  18. 18. NIH source: Urban dictionary photo by: John 'K'
  19. 19. 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'
  20. 20. The Solution™ photo: Ian Sane
  21. 21. Improve code
  22. 22. Improve code make it easier to comprehend
  23. 23. Improve code make it easier to comprehend make it flexible
  24. 24. Improve code make it easier to comprehend make it flexible make it tested
  25. 25. Improve code make it easier to comprehend make it flexible make it tested make it easier to replace, refactor
  26. 26. Improve code make it easier to comprehend make it flexible make it tested make it easier to replace, refactor make it not exist
  27. 27. Testing photo by: jeffkrause
  28. 28. Good Design Concepts
  29. 29. SOLID Single Responsibility
 Open and Close
 Liskov substitution
 Interface Segregation
 Dependency Inversion
  30. 30. STUPID Singleton
 Tight Coupling
 Untestability
 Premature Optimization
 Indescriptive Naming
 Duplication
  31. 31. Design Patterns photo by halloweenstock
  32. 32. Package Managers
  33. 33. Composer
  34. 34. PIE Proudly
 Invented
 Elsewhere
  35. 35. guzzlehttp/guzzle HTTP client for RESTful API clients
  36. 36. league/tactician A flexible CommandBus implementation
  37. 37. Readability photo: Morgenland
  38. 38. paragraphs photo: Trossachs Photography
  39. 39. whitespace
  40. 40. R&D Team for MIH/Naspers São PauloCape Town
  41. 41. Object Calisthenics photo by: boston_public_library
  42. 42. 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
  43. 43. Its about perception, not rules or standards photo by: david_a_l
  44. 44. #1 Only one indentation level per method. photo by: justinliew
  45. 45. #2 Do not 
 use else photo by: justinliew
  46. 46. #3 Wrap primitive types, if they contain behavior photo by: justinliew
  47. 47. $component->repaint(false);
  48. 48. $component->repaint( new Animate(false) );
  49. 49. #4 Only one 
 -> per line photo by: justinliew
  50. 50. #5 Do not abbreviate. photo by: justinliew
  51. 51. if($sx >= $sy) { if ($sx > $strSysMatImgW) { $ny = $strSysMatImgW * $sy / $sx; $nx = $strSysMatImgW; } if ($ny > $strSysMatImgH) { $nx = $strSysMatImgH * $sx / $sy; $ny = $strSysMatImgH; } }
  52. 52. #6 Keep your classes small. photo by: justinliew
  53. 53. #7 Limit your instance variables to less then 5 photo by: justinliew
  54. 54. #8 Use first class collections photo by: justinliew
  55. 55. #9 Don’t use getters and setters. photo by: justinliew
  56. 56. #10 Document your code. photo by: justinliew
  57. 57. Your turn.
  58. 58. Improve yourself!
  59. 59. Read lots of code!
  60. 60. Write simple code.
  61. 61. Try Object Calisthenics for a month.
  62. 62. Use someone else’s code.
  63. 63. Share bite size libraries.
  64. 64. Thank you. http://slides.doh.ms http://doh.ms @rdohms https://joind.in/talk/6236e
  65. 65. http://l.doh.ms/oc-material Video recording Slides Books Resources on 
 Object Calisthenics

×