Recommended
More Related Content
Similar to Clean Code
Similar to Clean Code (20)
Recently uploaded
Recently uploaded (20)
Clean Code
- 1. Clean Code Abdullah Izzuddiin Alqassam 26 April 2019 @ flip tower part 1
- 2. Definition - Why Write code is easy, read code is hard
- 3. Definition - Why Technical Debt high cost of maintenance, more bugs, slow to take off, etc
- 4. Definition - What I like my code to be elegant and efficient. The logic should be straightforward to make it hard for bugs to hide, the dependencies minimal to ease maintenance, error handling complete according to an articulated strategy, and performance close to optimal so as not to tempt people to make the code messy with unprincipled optimizations. Clean code does one thing well. - Bjarne Stroustrup, Inventor C++
- 5. Definition - What I like my code to be elegant and efficient. The logic should be straightforward to make it hard for bugs to hide, the dependencies minimal to ease maintenance, error handling complete according to an articulated strategy, and performance close to optimal so as not to tempt people to make the code messy with unprincipled optimizations. Clean code does one thing well. - Bjarne Stroustrup, Inventor C++
- 6. Definition - What Clean code can be read, and enhanced by a developer other than its original author. It has unit and acceptance tests. It has meaningful names. It provides one way rather than many ways for doing one thing. It has minimal dependencies, which are explicitly defined, and pro- vides a clear and minimal API. Code should be literate since depending on the language, not all necessary information can be expressed clearly in code alone. - Dave Thomas, Godfather of the Eclipse Strategy
- 7. Definition - What Clean code can be read, and enhanced by a developer other than its original author. It has unit and acceptance tests. It has meaningful names. It provides one way rather than many ways for doing one thing. It has minimal dependencies, which are explicitly defined, and pro- vides a clear and minimal API. Code should be literate since depending on the language, not all necessary information can be expressed clearly in code alone. - Dave Thomas, Godfather of the Eclipse Strategy
- 8. Definition - What "An fool can write code that a computer can understand. Good programmers write code that humans can understand." - Martin Frowler
- 9. Definition - What straightforward logic minimal dependencies please to read error handled does one thing tested ease to maintenance
- 11. Definition - Principle Maximize Signal, Reduce Noise Signal: TED (Terse, Expressive, Do One Thing) Noise: Repetition, Long Method, High Cyclomatic, Poorly Named
- 12. Outline Naming Function Conditional Class Comment
- 13. English: off Mixed Language: on
- 14. Naming
- 15. Naming - Principle Ccc lahir di pinggir Danau temp dan tidak pernah menginjak tanah di luar ranah nmTmpt. Masa kecilnya adalah find di rimba bukit, play di sawah berlumpur dan tentu clean berkecipak di air biru Danau temp.
- 16. Naming - Principle Alif lahir di pinggir Danau Maninjau dan tidak pernah menginjak tanah di luar ranah Minangkabau. Masa kecilnya adalah berburu durian runtuh di rimba Bukit Barisan, bermain bola di sawah berlumpur dan tentu mandi berkecipak di air biru Danau Maninjau. - Negeri 5 Menara, A. Fuadi
- 17. Naming - Principle Ngoding itu mirip menulis novel. Bayangkan kalau nama orang, nama tempat, kata kerja, kata sifat-nya tidak jelas.
- 18. Naming – General Rule Intention (don’t lie) Avoid disinformation Meaningful Distinction Pronounceable Avoid Encoding Pick One Word per Concept Use To Right Domain
- 19. Naming – Intention (don’t lie) Bad?
- 20. Naming – Intention (don’t lie) Good?
- 21. Naming – General Rule Intention (don’t lie) Avoid disinformation Meaningful Distinction Pronounceable Avoid Encoding Pick One Word per Concept Use To Right Domain
- 22. Naming – Avoid Disinformation Bad?
- 23. Naming – Avoid Disinformation Bad?
- 24. Naming – General Rule Intention (don’t lie) Avoid disinformation Meaningful Distinction Pronounceable Avoid Encoding Pick One Word per Concept Use To Right Domain
- 25. Naming – Meaningful Distinction Bad?
- 26. Naming – General Rule Intention (don’t lie) Avoid disinformation Meaningful Distinction Pronounceable Avoid Encoding Pick One Word per Concept Use To Right Domain
- 28. Naming – General Rule Intention (don’t lie) Avoid disinformation Meaningful Distinction Pronounceable Avoid Encoding Pick One Word per Concept Use To Right Domain
- 29. Naming – Avoid Encoding
- 30. Naming – General Rule Intention (don’t lie) Avoid disinformation Meaningful Distinction Pronounceable Avoid Encoding Pick One Word per Concept Use To Right Domain
- 31. Naming – Pick One Word per Concept Bad?
- 32. Naming – General Rule Intention (don’t lie) Avoid disinformation Meaningful Distinction Pronounceable Avoid Encoding Pick One Word per Concept Use To Right Domain
- 33. Naming – Use To Right Domain Good? Bad?
- 34. Naming – Boolean Yes-No Question? seperti is, has, any prefix (JavaBean Standar)
- 35. Naming – Boolean
- 36. Naming – Boolean Do’s Don’ts isOpen done isActive loggedIn open start status login
- 37. Naming – Method kata kerja
- 38. Naming – Method Do’s Don’ts
- 39. Naming – Class kata benda
- 40. Naming – Class Do’s Dont’s
- 41. Naming – Warning Waspada kalau nama method mengandung kata ‘and’, ‘or’. Biasanya melakukan lebih dari 1 hal
- 42. Naming – Rubber Duck Salah satu cara untuk mengetahui kualitas penamaan kita, coba baca code kita keras-keras. Ke siapa? Bisa ke temen sebelah atau ke bebek H. Slamet
- 43. Function
- 44. Function – General Rule Small Do One Thing Minimum Indenting Descriptive Name Few Arguments No Side Effects Prefer Exceptions Return Early
- 47. Function – General Rule Small Do One Thing Minimum Indenting Descriptive Name Few Arguments No Side Effects Prefer Exceptions Return Early
- 48. Function – Do One Thing Bad?
- 49. Function – Do One Thing Good?
- 50. Function – General Rule Small Do One Thing Minimum Indenting Descriptive Name Few Arguments No Side Effects Prefer Exceptions Return Early
- 51. Function – Minimum Indenting Bad?
- 52. Function – General Rule Small Do One Thing Minimum Indenting Descriptive Name Few Arguments No Side Effects Prefer Exceptions Return Early
- 53. Function – Descriptive Names Good?
- 54. Function – General Rule Small Do One Thing Minimum Indenting Descriptive Name Few Arguments No Side Effects Prefer Exceptions Return Early
- 55. Function – Few Arguments Bad?
- 56. Function – General Rule Small Do One Thing Minimum Indenting Descriptive Name Few Arguments No Side Effects Prefer Exceptions Return Early
- 57. Function – No Side Effect Bad?
- 58. Function – No Side Effect Good?
- 59. Function – General Rule Small Do One Thing Minimum Indenting Descriptive Name Few Arguments No Side Effects Prefer Exceptions Return Early
- 60. Function – Prefer Exceptions Good?
- 61. Function – Prefer Exceptions Bad?
- 62. Function – General Rule Small Do One Thing Minimum Indenting Descriptive Name Few Arguments No Side Effects Prefer Exceptions Return Early
- 63. Function – Return Early Good?
- 64. Function – Return Early Bad?
- 65. Conditional
- 66. Conditional – General Rule Positive Conditional Use Variable Ternary Elegance Polymorphism vs Enums
- 67. Conditional – Positive Conditional Bad? Good?
- 68. Conditional – General Rule Positive Conditional Use Variable Ternary Elegance Polymorphism vs Enums
- 69. Conditional – Use Variable Bad? Good?
- 70. Conditional – General Rule Positive Conditional Use Variable Ternary Elegance Polymorphism vs Enums
- 71. Conditional – Ternary Elegance Bad? Good?
- 72. Conditional – General Rule Positive Conditional Use Variable Ternary Elegance Polymorphism vs Enums
- 73. Conditional – Polymorphism vs Enums
- 74. Conditional – Polymorphism vs Enums
- 75. Comment
- 76. Don’t Comment Bad Code, Rewrite It - Brian Kerningham
- 77. Good Comment – Only For Legal Information Informative (Regex, Abstract, General Level) Uncommon Case Not a Zombie Code
- 78. Class
- 79. Epilog
- 80. The Boy Scout Rule “Always leave the campground cleaner than you found it.”
- 81. Refactor Only the code that you worked on it Should have test coverage to protect for regression
- 82. References
- 83. Clean Code by Uncle Bob Clean Code: Writing Code for Humans by Cory House https://app.pluralsight.com/library/courses/ writing-clean-code-humans/table-of- contents