Downloaded 38 times
More Related Content
Similar to Clean code coding like a professional
![[DevDay2018] Let’s all get along. Clean Code please! - By: Christophe K. Ngo,...](https://cdn.slidesharecdn.com/ss_thumbnails/christophek-180419103038-thumbnail.jpg?width=640&height=640&fit=bounds)
Clean code coding like a professional
- 1. Clean Code Coding likea professional XPDay Vietnam @ Hanoi May, 2016 Nguyễn Khắc Nhật | Learning Master @ Học Viện Agile | [email protected]
- 2. | Agile |Scrum | Kanban | Lean | Java | Scala | Typescript | NodeJS | Virtual DOM | Bobril | ReactJS | AngularJS
- 3.
- 4. What is thedifference? Good CodeBad Code
- 5. Bad code lookslike this...
- 6.
- 7. Good code lookslike this...
- 8.
- 9.
- 11.
- 12. What is cleancode? “Clean code is simple and direct. Clean code reads like well-written prose. Clean code never obscures the designer’s intent but rather is full of crisp abstractions and straightforward lines of control” Grady Booch Object Oriented Analysis
- 13. What is cleancode? “Clean code can be read, and enhanced by an developer other than its original author. It has unit and acceptance tests. It has meaningful names. It provides one way rather than many ways of doing one thing. It has minimal dependencies,...” Dave Thomas OTI, Eclipse
- 14. What is cleancode? “I could list all of the qualities that I notice in clean code, but there is one overarching quality that leads to all of them. Clean code always looks like it was written by someone who cares...” Michael Feathers Working effectively with Legacy Code
- 15. What is cleancode? “In recent years I begin, and nearly end, with Beck’s rules of simple code. In priority order, simple code: Run all the tests; Contains no duplication; Express all the design ideas that are in the system Minimizes the numbers of entities such as classes, methods, functions,...” Ron Jeffries Extreme Programming Installed Extreme Programing Adventures in C#
- 16.
- 17. What make bador good code? Names Functions Comments Formats Objects and Data Structure Error Handling Unit Tests Boundaries Classes System ...
- 18.
- 19.
- 20.
- 21. Naming Rules Use Intention-RevealingNames Avoid Disinformation Make meaningful Distinctions Use Pronounceable Names Use Searchable Names Avoid Encodings Avoid Mental Mapping Class Names Don’t Be Cute Pick One Word per Concept Don’t Pun Use Solution Domain Names Use Problem Domain Names Add meaningful Context Don’t Add Gratuitous Context
- 22. Try with thiscode….
- 23.
- 24. and, how aboutthis...
- 25.
- 26.
- 27. Function Rules Functions Shouldbe Small Functions Should Do Only One Thing One level of Abstraction per Function Use Descriptive Names Function Arguments Have No Side Effects Command/Query Separation Prefer Exceptions to Returning Error Codes Don’t Repeat Yourself Multiple Returns
- 28. Demo with compareTo()method
- 29. The beauty offunctional programming
- 30. Comments "Don’t comment badcode—rewrite it."
- 31.
- 32. Formatting Vertical Formatting Horizontal Formatting Theteam’s rules first!!!
- 33.
- 34.
- 35. Objects and Datastructures Object Data Structure
- 36. Law of Demeter Givenmethod ƒ of class C, ƒ should only call methods of: ● C ● An object created by ƒ ● An object passed as an argument to ƒ ● An instance variable of C
- 37.
- 38.
- 39.
- 40.
- 41.
- 42.
- 44.