CST 338 Week 3
Summarize the feedback you received about your code
Identify any trends you noticed when evaluating the code of others
such as: everyone struggled with sorting or unit tests that were hard to pass
Was any part of the code a struggle for YOU?
Was any part of writing the code easy for YOU?
What is your biggest victory?
This week my group mates reviewed some of my code from the Reader class and Book class assignment. My code ran as intended and they thought that my code was well structured. They also pointed out some small issues in my code. My code passed the unit tests, but these issues may affect how well others can read my code in the future. I think these minor issues stemmed from me not being as careful as I should have been. In the future, I will take my time to improve the readability of my code by doing things, such as leaving notes throughout my code, so others can better understand what I am trying to do.
Most of the work I reviewed with my classmates looked pretty similar. They all followed the prompt closely so they had the same names for variables, and their class methods had similar logic. One thing that varied from person to person were the notes in the project. After seeing how detailed some of my group mates' notes were, I will make a better effort to do the same.
None of my struggles from these assignments were caused by code. I still find that the most confusing part about these assignments for me is using Git and branching. I feel like I will become more comfortable over time as I continue to work on projects in this class.
I think my biggest victory from this assignment was the removeBook method in the Reader class. I used a try catch block to catch any errors from failing to remove a book from the list instance variable. I have not used a try catch in java in a long time, so I am proud that I incorporated one into my code. (hopefully I did it right).
Comments
Post a Comment