Clean Code: Successive Refinement

Clean Code: Successive Refinement

• 1.
  CHAPTER 14 CLEAN CODE
• 3.
  the process ofremoving impurities or unwanted elements from a substance condition of being impure its possible to start with dirty code and then clean it. Cleaning step here is a must!
• 4.
  is software developmentapproach in which test cases are developed to specify and validate what the code will do. +15% from last month test cases for each functionality are created and tested first and if the test fails then the new code is written in order to pass the test and making code simple and bug-free
• 6.
  • • •
• 7.
  Its hard tounderstand and hard to maintain which we call bad code stop adding new feature and start refactoring there is a working bad code and programmer feel like code is full of messy
• 8.
  • Refactoring canlead to undo of code from previous refactor. • Refactoring: make it work and then make it right. • Refactoring can cause crash or break features. • When complexity increased with new cases stop and take time to do successive refinement. • To avoid this we need TDD.
• 9.
  • •
• 10.
  • • •
• 11.
  😅 • •
• 12.
  • Clean Code:A Handbook of Agile Software Craftsmanship by Robert C. Martin, Chapter 14 • https://www.guru99.com/test-driven-development.html • https://medium.com/@dnkilic/clean-code-chapter-14- successive-refinement-f16d541adaa • https://blog.jakubholy.net/2011/02/19/hidden- dependencies-are-evil-arguing-with-the-clean-code/
• 13.
  https://www.linkedin.com/in/ali-a- jalil-ab9a176b/