[Nomad Coders Challenge] Clean Code - Assignment #04

 

 

📍 It is part of a book club challenge on a programming learning website called Nomad Coders. The challenge is to demonstrate what I have learned after reading Clean Code by Robert C. Martin.

 

📝 It will consist of the following sections over three weeks: the range of reading, the top quotes from the book, my review, and remaining questions. 

  🔗Challenge Schedule

---

💻 I plan to read Clean Code in JavaScript and Python, referring to the GitHub repositories shared by Nomad Coders with the challengers.

 

Assignment #04

• 📚 Chapter 3. Functions - 함수를 잘 만드는 법
• ✔️ TIL 
  • Top quotes from the book
  • My review
  • Remaining questions

---

 

📝 Top quotes from the book

• 작게 만들어라
  • 함수가 작을수록 더 좋다
  • if 문/ esle 문/ while 문 등에 들어가는 블록은 한 줄이어야 한다는 의미다.
    

•  Functions should do one thing. 그 한가지를 잘 해야 한다. 그 한가지만을 해야 한다.
  

  • TO RenderPageWithSetupsAndTeardowns

    페이지가 테스트 페이지인지 확인 한 후 -> 테스트 페이지면 -> 설정 페이지, 해제 페이지를 넣는다. 테스트 페이지든 아니든 -> HTML로 렌더링한다. 
  •  함수가 '한 가지'만 하는지 판단하는 다른 방법 - 의미 있는 이름으로 다른 함수를 추출할 수 있다면 그 함수는 여러 작업을 하는 셈이다. [G34]
  • This is by far the most important rule in software engineering. When functions do more than one thing, they are harder to compose, test, and reason about. When you can isolate a function to just one action, it can be refactored easily and your code will read much cleaner. ( @ryanmcdermott. Clean Code in Javascript: Functions. GitHub. Link )

    

•  Functions should only be one level of abstraction. 
  • When you have more than one level of abstraction your function is usually doing too much. Splitting up functions leads to reusability and easier testing. ( @ryanmcdermott. Clean Code in Javascript: Functions. GitHub. Link )
    

    

• ...

 

🖊️ My review

• ...

 

 

🔍 Remaining questions

• FitNesse
• JUnit
• Lexical grammar  Lexical analysis
• ...

---

🔗 Additional Resources

• Clean Code concepts adapted for JavaScript
• Clean Code concepts adapted for Python