“Writing code that lasts” … or writing code you won’t hate tomorrow.
50 likes3,440 views
The document emphasizes the importance of writing maintainable and comprehensible code, highlighting common pitfalls such as anti-patterns and bad design. It advocates for practices like testing, simplicity, and the use of object calisthenics to improve code quality. The overall message encourages developers to evolve and adapt their coding practices over time.
“Writing code that lasts” … or writing code you won’t hate tomorrow.
- 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
- 6. 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
- 7. photo: Rob Allen (@akrabat)
- 9. REWRITE ALL THE CODE! image: hyperboleandahalf
- 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
- 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
- 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. Design Patterns photo by halloweenstock
- 37. Composer
- 39. guzzlehttp/guzzle HTTP client for RESTful API clients photo by j_regan
- 40. league/tactician A flexible CommandBus implementation
- 43. whitespace
- 45. R&D Team for MIH/Naspers São PauloCape Town
- 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.
- 66. Try Object Calisthenics for a month.
- 69. Thank you. http://slides.doh.ms http://doh.ms @rdohms we are hiring! http://tech.sym.bid/jobs
- 70. http://l.doh.ms/oc-material Video recording Slides Books Resources on Object Calisthenics