From 4d2b0de4602ef312accc8b1939e9dd9258389ad7 Mon Sep 17 00:00:00 2001 From: maryrosecook Date: Tue, 16 Jan 2018 16:19:29 +0000 Subject: [PATCH] Updates chapter9/README.md Auto commit by GitBook Editor --- chapter9/README.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/chapter9/README.md b/chapter9/README.md index 4c91446..bd53d1f 100644 --- a/chapter9/README.md +++ b/chapter9/README.md @@ -482,4 +482,8 @@ Here are some helpful rules of thumb to picking the right abstraction when writi 1. Can you name your method in a simple way, without using the word 'and'? Does it do one thing, and nothing more? 2. Can you name your method after what it returns, instead of what it does? For instance, `average(test_scores)` is a better name than `averages_scores(test_scores)`. For another example, `score(hand)` is a better method name than `scores_cards(hand)`. -If you can answer 'yes' to both 1 and 2, your method is more likely to be a good one. \ No newline at end of file +If you can answer 'yes' to both 1 and 2, your method is more likely to be a good one. + +## Complete the mastery quiz for chapter 9 + +Use your mastery quizzes repository to complete the quiz for chapter 9. \ No newline at end of file