CSCI 303 Laffra's Chapter 8: "Code" 

Questions to answer during "roll call" Wednesday October 30th.
1. What is the ratio of time spent reading versus writing code according to 
   Robert Martin in his book _Clean Code_ ?   
   
2. Identify Kent Beck's "four rules of Simple Design".  

3. Briefly explain each of Kent Beck's "four rules of Simple Design". 
   Passes all tests - 
   Expresses intent -
   No duplication - 
   Minimalistic - 

4. How do we write code that is both readable and elegant?

5. What are "linters" (or linting tools) used by software developers?
  
6. When to use the program "Comments" and what are they to say? 
  
7. What is the "litmus test for code readability"?
 
8. Describe the "Commit Messsage Structure".
 
9. What is meant by using the imperative mood when writing Commit Titles?
   Give an example.
      
10. Explain the action of "Bundling Commits". 

11. Identify what to look for in a code review.

12. How can code reviews become objective and egoless? 

13. Why make code reviews fast?

14. What are steps to follow when you have to do a code review from someone
    where you have a hard time being objective? 

15. How should a code review be rejected?
    
16. When doing code reviews, give reasons to allow "one-click Suggestions".
    
17. Discuss "Reviewing Hard Cases." 

18. Why should you be expected to "Demo Your Code"?