CST 338 Week 4

             This week I worked with Rene, Martin, and Krithika.

I read through the entire prompt first and then I started writing my code. I worked in order that methods were listed in the instructions. If a method required the use of another method, I would continue writing the code as if it was already implemented. I would then work on that method afterwards. I wrote the entire code first and then debugged. This worked well on the smaller projects but was a horrible idea for the big library project.

Rene worked on the project in sections and he started off with the smaller methods first. This helped him understand the project better and reduced how many times he had to jump between tasks. Martin worked in a similar way. He tackled easier problems first and then worked on difficult problems. Krithika started off by writing out class methods in pseudo code first. This strategy helped her get a better idea about what she needed to do for the project.

I would have made sure my class methods worked before I moved on to the next. I was able to get my code to pass most of the unit tests pretty quickly on the first 3 assignments, so I thought I could do the same thing for the final part of the project. This strategy did not work out well and I spent a lot of time going back and forth fixing errors in my code

One thing I strived to work on that my peers told me last week were my javadocs. I did not use them much last week and I only really remember writing notes for more complex methods. This week I made an effort to include notes for most methods in my project. I also made sure this week to format my notes neatly and follow the Java style guide. I wanted to make sure that my ideas were clearly and were organized in a consistent manner so others could understand my code.