CSE 143: Computer Programming II, Fall 2018

General Style Deductions

Students in CSE143 are expected to demonstrate good programming style in their homework solutions. Every homework assignment will describe specific style requirements and expectations that students should keep in mind when writing their solutions. This page lists general style issues that are likely to be relevant to multiple assignments. This list includes common style mistakes but does not list every possible style mistake.

TAs provide feedback on graded homework assignments and often give a "-0" warning to indicate a style issue that is not being penalized but might be in a future assignment. The list below indicates general style issues that will not be graded as "-0". Homework assignments are listed in reverse order because once a style issue is included for one homework, it is included for all future homeworks. The list is not meant to be exhaustive, although it includes the most common style issues. Students should not ask about the details of style grading on the message board, but can ask their TA or a TA at the IPL to explain any of these style categories.

• Homework 8: Huffman
  • no new style errors
• Homework 7: 20 Questions
  • class design errors:
    • not using calls on this(...) to eliminate redundancy by having one constructor call another
  • data structure errors:
    • not using x=change(x) when appropriate to simplify code
    • poor choice of constructors when designing a node class (e.g., unused constructors or just a zero-argument constructor)
  • miscellaneous errors:
    • using \n to produce more than one line of output with a single print/println/printf
    • poor choice of constructor when using a node class (e.g., setting fields immediately after construction when they could have been set by using a different constructor)
• Homework 6: Anagram Solver
  • data structure errors:
    • poor use of collections (e.g. for each looping over a Stack)
• Homework 5: Grammar Solver
  • control structure errors:
    • structuring a recursive solution so that it has extra recursive cases or extra base cases that are not needed
  • method errors:
    • unnecessary parameters with redundant information that is available to the method from another source
  • data structure errors:
    • excessive inefficiency when using collections (e.g., using a foreach loop to find a value of a map when a call on get would return the value)
  • miscellaneous errors:
    • incorrect use of type (e.g., double instead of int, int instead of boolean, String instead of char for a value known to be exactly one character)
    • computing a value multiple times when it could have been computed once and stored in a variable.
    • looking ahead in a recursive method (i.e. structuring a solution that handles a base case preemptively rather than leaving it for a future recursive call)
• Homework 4: Evil Hangman
  • method errors:
    • using if/else instead of if for exception code (non-exception code should not be in an else branch)
    • not decomposing complex methods into logical subtasks that each have their own method
  • data structure errors:
    • excessive inefficiency when using collections (e.g., using a foreach loop to find a value of a map when a call on get would return the value)
  • miscellaneous errors:
    • Incorrect use of type (e.g., double instead of int, int instead of boolean, String instead of char for a value known to be exactly one character)
    • Computing a value multiple times when it could have been computed once and stored in a variable.
• Homework 3: Assassin
  • commenting errors:
    • method header does not describe the purpose of each parameter or does not describe the meaning of the return value of a non-void method
    • commenting on a specific client of the class (e.g. AssassinMain)
  • readability errors:
    • nondescriptive names for local variables or methods
  • control structure errors:
    • bad use of if/else (e.g., empty branch, if/if instead of if/else, poor factoring, unnecessary tests)
    • bad use of loops (e.g., including an unnecessary check before a loop that repeats the loop test)
  • method errors:
    • not throwing exceptions at the top of a method when detecting the error does not require significant computation
    • using if/else instead of if for exception code (non-exception code should not be in an else branch)
    • modifying a parameter to a method when such modification was not part of the intended behavior
  • miscellaneous errors:
    • failure to simplify code (e.g., not factoring out common code, extra tests or loops that aren't necessary)
• Homework 1: LetterInventory
  • commenting errors:
    • class header missing or doesn't describe both student and program
    • method header missing or does not document pre and post-conditions
    • method header does not describe exceptions that are thrown when preconditions are violated, including the specific type of exception and the conditions under which it is thrown
    • method header does not document important behavior including subtle cases like an empty structure or a search value not found
    • blind copying of text from assignment writeup
  • readability errors:
    • bad indentation
    • some method or constructor does not have a blank line before it
  • control structure errors:
    • bad Boolean Zen
  • data structure errors:
    • extra data structures that aren't necessary
    • bad usage of arrays (e.g., funky/incorrect indexing/usage)
  • class design errors:
    • extraneous data fields
    • initializing non-final data fields outside of a constructor
    • non-private data fields
  • miscellaneous errors:
    • using a specific numerical value when the value can be obtained in a more general way (e.g., even if an array called data is expected to be of length 100, code to manipulate it after construction should use data.length instead of 100)

note: "e.g." should be read as "for example" and "i.e." should be read as "in other words"

In general, once a class has been discussed, it is available for use by students. For example, the String class and the Arrays class were covered in the CSE142 course, so it is reasonable to assume that you can use methods from those classes without asking permission. Student should realize, however, that saying that you are not forbidden from using a certain construct is not the same thing as saying that it is a good idea to use a certain construct. We don't give advice to students about which constructs to use. You have to use your best judgment to decide and you might lose style points if you make a poor choice. In addition, there are some constructs that you are not allowed to use, as described in the next paragraph.

Forbidden features

Java has grown to be a complex language with many features. We don't have time to teach all of these features in CSE143. We have a general rule that students should not use "advanced" material that we have not covered in class. In addition, we have identified several Java features that we do not want students to use. It is not bad style to use these features, but we want to have a level playing field for all students. For any one of these features, we prefer that either everyone in the class knows about it and can use it or nobody is allowed to use it. The following features should not be used in CSE143 homework or exam solutions:

• break, continue, return from a void method
• try/catch, annotations
• the <> operator
• Java 8 features (e.g., lambdas, streams, method references)
• toArray, clone
• StringBuilder, StringBuffer, StringJoiner, StringTokenizer, and String methods toCharArray, join, matches
• Arrays.asList, Arrays.copyOf, Arrays.copyOfRange, Arrays.sort
• Collections.copy, Collections.sort
• LinkedHashMap

Many students find themselves wondering, "What is that feature you are describing?" If you don't recognize it, then you're unlikely to use it, so the best answer is, "Something that we have decided not to teach you in this class so that we will be able to focus on the really important concepts you need to learn."