Download as PDF, PPTX
Uploaded byRafael Dohms
“Writing code that lasts” … or writing code you won’t hate tomorrow. - #PHPSRB16
The document focuses on writing sustainable code, emphasizing the importance of clarity, comprehensibility, and flexibility. It discusses various programming principles and best practices to avoid common pitfalls like bad design and complexity. Additionally, it advocates for ongoing improvement and self-undertaking in coding skills through techniques such as object calisthenics.
More Related Content
Similar to “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
- 1. Writing code that lasts. RafaelDohms @rdohms photo: djandyw.com #ocforphp
- 2. Writing code youwon’t hate tomorrow. Rafael Dohms @rdohms photo: djandyw.com #ocforphp
- 3. Rafael Dohmsor @rdohms ontwitter
- 4.
- 7. No Tests. Wrote hisown 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 wefind balance? photo: Kalexanderson
- 16. Code has an expirationdate photo: CarbonNYC
- 17. Code is perishable, itrots. photo by: massdistraction
- 18. Code Evolves photo by:kevin dooley
- 19.
- 20. You evolve. photo by:Kaptain Kobold
- 21.
- 22.
- 23.
- 24. NIH source: Urban dictionary photoby: John 'K'
- 25. NIH | nɒt ɪnˈventɪdhɪə | 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.
- 27.
- 28. Improve code make iteasier to comprehend
- 29. Improve code make iteasier to comprehend make it flexible
- 30. Improve code make iteasier to comprehend make it flexible make it tested
- 31. Improve code make iteasier to comprehend make it flexible make it tested make it easier to replace, refactor
- 32. Improve code make iteasier to comprehend make it flexible make it tested make it easier to replace, refactor make it not exist
- 33.
- 34.
- 35. SOLID Single Responsibility Open andClose Liskov substitution Interface Segregation Dependency Inversion
- 36.
- 37. Design Patterns photo byhalloweenstock
- 38.
- 39.
- 40.
- 41. guzzlehttp/guzzle HTTP client forRESTful API clients
- 42. league/tactician A flexible CommandBusimplementation
- 43.
- 44.
- 45.
- 47. R&D Team forMIH/Naspers São PauloCape Town
- 48.
- 49. Calisthenics /ˌkaləsˈTHeniks/ Calisthenics are aform 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, notrules or standards photo by: david_a_l
- 51. #1 Only one indentation level permethod. photo by: justinliew
- 52. #2 Do not useelse photo by: justinliew
- 56. #3 Wrap primitive types, ifthey contain behavior photo by: justinliew
- 57.
- 58.
- 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. photoby: justinliew
- 63. #7 Limit your instance variables toless then 5 photo by: justinliew
- 64. #8 Use first class collections photoby: justinliew
- 65. #9 Don’t use getters andsetters. photo by: justinliew
- 66. #10 Document your code. photo by:justinliew
- 67.
- 68.
- 69.
- 70.
- 71. Try Object Calisthenics fora month.
- 72.
- 73.
- 74.
- 75. http://l.doh.ms/oc-material Video recording Slides Books Resources on Object Calisthenics