Mohamed's journey at CSUMB

I worked with Matthew, Dakota and Jerrick.  My strategy for this assignment was first figuring out the structure of the program and what methods need to be written first, especially because we need to commit in 2 different branches. My strategy was dividing the code into 2 sections, the first section is the methods required for structuring the words hashmap  including (endsWithPunctuation, addWord, addLine, and addFromFile). When writing these methods I start with writing the necessary method that will allow me to write the next one, for example: I needed endsWithPunctuation before writing addWord.  Matthew mentioned that he tried planning out the code on paper before writing the code, although he found himself struggling with it. He had a much easier time after writing some code so that he can examine the output on the screen. Jerrick’s mostly focused on comments and more diligent commits. He did write out some planning on paper before writing the cod...

During this week I have worked with Jerrick Wallace, Matthew Ross and Dakota Fouch. My strategy for most of this assignment or at least for  'Book', 'Shelf', and 'Reader' classes is starting by looking at the UML diagram to figure out all the fields each class needed. After listing these, I use auto-generation to create the setters and getters. Then, I check the prompt to make sure the constructors were correct and tweak them as needed. Next, I auto-generate the 'hashCode' and 'equals' methods, making sure they matched the requirements. The 'toString' methods are usually a bit different, so I write it manually to get the formatting right. Once all the basic methods are set up, I move on to the logic methods, following the prompt closely and writing them out. Finally, I use the test files to make sure everything works as expected. My teammates strategy is also for the most part  reading the prompt and then just starting to write code and v...

During this week I have worked with Jerrick Wallace, Matthew Ross and Dakota Fouch. I got my code reviewed by Jerrick Wallace and Matthew Ross. It was informative to receive feedback as much as giving one.  Matthew commented that most of my code is well documented and the comments make it easy to read and understand. He also mentioned that my approach to the display method using String builder makes writing the function more efficient than building multiple strings.  Jerrick suggested that I need to work more on my comments inside the methods so it's a bit easier to understand complex methods. We had an interesting discussion about the sort function and the efficiency of bubble sort. Overall he thinks that the organization of your code is spot on.  We all had discussion on the most challenging part of the assignment (Histogram) and we agreed that it's the display method. It took the longest to complete and mostly trying to make it match the format...

 Week one has been really interesting, working on a variety of things, from building the entity for the reader part of the library project to working on the histogram homework was a lot of fun and engaging. Working on the histogram assignment was challenging yet rewarding, I liked the fact that we had a lab to go over a few parts of the histogram assignment which helped to build the foundation for completing the rest of the functionality. One of the more challenging parts of this assignment was building the display() function, it took a while to figure out how to make it look clean and similar to the one used in the prompt. Another interesting part was practicing my algorithms skills and optimizing the sort function and getting the time complexity down. The other parts of the project were easy to complete and a bit fun.