anchor.diff:  
   == Use Logging `[LO-Logging]`
   
  -Note <<DeveloperGuide#31-logging, how the AddressBook app uses Java's `java.util.log` package to do logging>>.
  -
  -*Resources*
  -
  -* Tutorials
  -** http://tutorials.jenkov.com/java-logging/index.html[Logging using java.util.logging] - a tutorial by Jakob Jenkov
  -** http://docs.oracle.com/javase/7/docs/technotes/guides/logging/overview.html[Logging tutorial] - a more detailed tutorial from Oracle.
  -* Logging best practices
  -** http://commons.apache.org/proper/commons-logging/guide.html#Message_PrioritiesLevels[Apache Commons Logging guide]
  -** https://www.javacodegeeks.com/2011/01/10-tips-proper-application-logging.html[10 Tips for Proper Application Logging]
  -** https://wiki.base22.com/display/btg/Java+Logging+Standards+and+Guidelines[Base 22 Java Logging Standards and Guidelines]
  +Note <<DeveloperGuide#logging, how the AddressBook app uses Java's `java.util.log` package to do logging>>.
  +
  +*Resources*
  +
  +* https://se-edu.github.io/se-book/errorHandling/logging/[se-edu/se-book: Implementation: Error Handling: Logging]
   
   === Exercise: Add more logging
   
  
positive.code: * Note how some PRs in this project have been reviewed by other developers. Here is an https://github.com/se-edu/addressbook-level4/pull/147[example].
  * Also note how we have used https://www.codacy.com[Codacy] to do automate some part of the code review workload (https://www.codacy.com/app/damith/addressbook-level4?utm_source=github.com&utm_medium=referral&utm_content=se-edu/addressbook-level4&utm_campaign=Badge_Grade[image:https://api.codacy.com/project/badge/Grade/fc0b7775cf7f4fdeaf08776f3d8e364a[Codacy Badge]])
  
  Here are some things you can comment on when reviewing code:
  
  * Read the code from the perspective of a new developer. Identify parts that are harder to understand and suggest improvements.
  * Point out any coding standard violations.
  * Suggest better names for methods/variables/classes.
  * Point out unnecessary code duplications.
  * Check if the comments, docs, tests have been updated to match the code change.
  * Check for violation of relevant principles such as the SOLID principles.
  * Point out where SLAP can be improved. e.g. methods that are too long or has too deep nesting.
  * Suggest any other code quality improvements.
  
  *Resources*
  
  * https://www.kevinlondon.com/2015/05/05/code-review-best-practices.html[Code Review Best Practices] - Blog post by Kevin London
  * https://www.atlassian.com/agile/code-reviews[Why Code Reviews Matter] - An article by Atlassian
  
  === Exercise: Review a PR
  
  * Review a GitHub PR created by a team member.
  
negative.code: 
  === Exercise: Write more automated GUI tests
  
  * Covered by `[LO-SystemTesting]`
  
  '''
  
  