Code review changes

[MSG17]

This is my code review pull request. I added my rationale to each change through inline Github comments. I aimed to make the project more complete and standardized as well as introduce test-driven design.

[discospiff]

Several good suggestions that reduce technical debt. I recommend merging this branch.

[MSG17]

Adding some comments: What does the program do? This program allows users to keep track of their pets and tasks they need to do to care for them through a web interface. Users can log in and see what tasks they need to do and what tasks have already been completed, as well as assign responsibilities to members of their household. Was the program available on time? Yes, I was able to pull, run and review it on time. Does the program compile? Yes, but the web interface only displays an error page when run. What did you learn from this code review? I learned several concepts from this exercise:

• I gained more experience with Thymeleaf and SpringBoot, and better understood how they work and what ways they can be configured.
• I made further inroads into test-driven design and learned how to better plan unit tests and develop for them. I also learned more about the testing mechanisms itself.
• My knowledge of code standards and good practices was reinforced. The readings that I did for this code review also educated me on more best practices, such as optimal size limits for files to avoid over-complicated/spaghetti code. Further recommendations: Integrate CircleCI to automate unit tests and better implement TDD/BDD.