This criterion is linked to a Learning Outcome Readability. Code needs to be readable to both you and a knowledgeable third party. This involves: - Using indentation consistently (e.g., every function's body is indented to the same level). -Adding whitespace (blank lines, spaces) where appropriate to help separate distinct parts of the code (e.g., space after commas in lists, blank lines between functions or between blocks of related lines within functions, etc.), -Giving variables meaningful names. Variables named A, B, and C or foo, bar, and baz give the reader no information whatsoever about their purpose or what information they may hold. -Names like principal, maximum, and counter are much more useful. Loop variables are a common exception to this idea, and loop variables named i, j, etc. are okay. -The code should be well organized.

Functions should be defined in one section of the program, code should be organized into functions so that blocks of code that need to be reused are contained within functions to enable that, and functions should have meaningful names. This is a concept that we will be learning about as we write more and more code, and so few points, if any, will be taken off for organization issues that we have not yet addressed in class. 30.0 pts - Exceeds; No errors, code is clean, understandable, and well- organized. 17.0 pts - Meets; Minor issues with consistent indentation, use of whitespace, variable naming, or general organization. 15.0 pts - Nearly Meets; At least one major issue with indentation, whitespace, variable names, or organization. 12.0 pts - Does Not Meet; Major problems with at least three or four of the readability subcategories.