CS 214 Exam 2: Clean Questions with all Correct & 100%
Verified Answers |Latest Version |Guaranteed to Pass
T or F: Flag arguments are useful. ✔Correct Answer--False
T or F: Keeping code clean at all times is not a cost effective solution. ✔Correct Answer--False
T or F: Messy code is okay to meet a deadline. You can clean it up later. ✔Correct Answer--
False
T or F: A parallel redesign is usually required to fix messy code. ✔Correct Answer--False
What is the ratio of time spent reading versus writing code.
1.) 5:1
2.) 10:1
3.) 2:1
4.) 1:1 ✔Correct Answer--2.) 10:1
T or F: Longer names are generally better than shorter names since they can give more context.
✔Correct Answer--False
T or F: Different classes can use different words for the same concept. ✔Correct Answer--False
T or F: Polymorphism is preferable to switch statements. ✔Correct Answer--True
T or F: Names should vary in small ways. ✔Correct Answer--False
T or F: Names should be pronounceable. ✔Correct Answer--True
T or F: Productivity decreases asymptotically to zero over time with messy code. ✔Correct
Answer--True
T or F: Functions should be small. ✔Correct Answer--True
T or F: Do not use single character variable names except for loop counters. ✔Correct
Answer--True
T or F: Method names should only be verbs or verb phrases. ✔Correct Answer--True
T or F: Class names should only be nouns. ✔Correct Answer--True
, T or F: Functions should do something or answers something, not both. ✔Correct Answer--
True
T or F: Clever names can help aid understand and memory. ✔Correct Answer--False
T or F: It is easier to name functions that are smaller and more focused. ✔Correct Answer--
True
When should you clean up bad code?
1.) when someone asks
2.) when writing tests
3.) as soon as you notice it
4.) during regularly scheduled periods ✔Correct Answer--3.) as soon as you notice it
T or F: Arguments complicate testing due to combinations. ✔Correct Answer--True
T or F: Historical discussion comments can be useful. ✔Correct Answer--False
T or F: The same name can be used for different purposes in different classes. ✔Correct
Answer--False
T or F: Most names provide meaningful context, in and of themselves. ✔Correct Answer--
False
T or F: Output arguments are preferable to input arguments. ✔Correct Answer--False
T or F: Solution domain names are preferable to problem domain names to make it easier for
the programmer. ✔Correct Answer--False
T or F: Attributions in the code can be useful. ✔Correct Answer--False
T or F: Three or more function arguments should be avoided. ✔Correct Answer--True
T or F: Comments can make up for bad code. ✔Correct Answer--False
T or F: Adding more staff can maintain productivity with messy code. ✔Correct Answer--False
T or F: Functions should change state of object rather than use output arguments. ✔Correct
Answer--True
T or F: Functions with 2 or more arguments can be confusing because of order. ✔Correct
Answer--True
T or F: Every function/method should have a Javadoc. ✔Correct Answer--False
Verified Answers |Latest Version |Guaranteed to Pass
T or F: Flag arguments are useful. ✔Correct Answer--False
T or F: Keeping code clean at all times is not a cost effective solution. ✔Correct Answer--False
T or F: Messy code is okay to meet a deadline. You can clean it up later. ✔Correct Answer--
False
T or F: A parallel redesign is usually required to fix messy code. ✔Correct Answer--False
What is the ratio of time spent reading versus writing code.
1.) 5:1
2.) 10:1
3.) 2:1
4.) 1:1 ✔Correct Answer--2.) 10:1
T or F: Longer names are generally better than shorter names since they can give more context.
✔Correct Answer--False
T or F: Different classes can use different words for the same concept. ✔Correct Answer--False
T or F: Polymorphism is preferable to switch statements. ✔Correct Answer--True
T or F: Names should vary in small ways. ✔Correct Answer--False
T or F: Names should be pronounceable. ✔Correct Answer--True
T or F: Productivity decreases asymptotically to zero over time with messy code. ✔Correct
Answer--True
T or F: Functions should be small. ✔Correct Answer--True
T or F: Do not use single character variable names except for loop counters. ✔Correct
Answer--True
T or F: Method names should only be verbs or verb phrases. ✔Correct Answer--True
T or F: Class names should only be nouns. ✔Correct Answer--True
, T or F: Functions should do something or answers something, not both. ✔Correct Answer--
True
T or F: Clever names can help aid understand and memory. ✔Correct Answer--False
T or F: It is easier to name functions that are smaller and more focused. ✔Correct Answer--
True
When should you clean up bad code?
1.) when someone asks
2.) when writing tests
3.) as soon as you notice it
4.) during regularly scheduled periods ✔Correct Answer--3.) as soon as you notice it
T or F: Arguments complicate testing due to combinations. ✔Correct Answer--True
T or F: Historical discussion comments can be useful. ✔Correct Answer--False
T or F: The same name can be used for different purposes in different classes. ✔Correct
Answer--False
T or F: Most names provide meaningful context, in and of themselves. ✔Correct Answer--
False
T or F: Output arguments are preferable to input arguments. ✔Correct Answer--False
T or F: Solution domain names are preferable to problem domain names to make it easier for
the programmer. ✔Correct Answer--False
T or F: Attributions in the code can be useful. ✔Correct Answer--False
T or F: Three or more function arguments should be avoided. ✔Correct Answer--True
T or F: Comments can make up for bad code. ✔Correct Answer--False
T or F: Adding more staff can maintain productivity with messy code. ✔Correct Answer--False
T or F: Functions should change state of object rather than use output arguments. ✔Correct
Answer--True
T or F: Functions with 2 or more arguments can be confusing because of order. ✔Correct
Answer--True
T or F: Every function/method should have a Javadoc. ✔Correct Answer--False
