Week 13 (Module 4)

 For your learning journal for Week 04 I would like the following:

Prompt - Project 1

Work with some of your fellow classmates and go through your solution to project 1: LDPM
1. You can work with up to three people (you MUST work with at least one other person)
    1. With whom did you work?
2. What was your strategy for solving the assignments?
    1. Did you start writing code right away? Did you plan it out on paper? 
3. What was THEIR strategy for solving the assignments
4. How would you change your strategy having worked on the assignment?
5. According to your classmate(s): how well does your code follow the [Google Java Style Guide](https://google.github.io/styleguide/javaguide.html)
    1. Did you know [you can automate applying some of the style guide rules](https://medium.com/swlh/configuring-google-style-guide-for-java-for-intellij-c727af4ef248)
6. What was the most challenging part?
7. What was the most interesting?
8. What are you the most proud of?
9. How did you celebrate completing the assignment? 
    1. If you didn't how will you celebrate?
        1. This isn't a joke. It helps our learning to celebrate and acknowledge victories.  <-- Dr.C just fought for your right to party.
Please submit a screenshot or a link to your learning journal entry for week 04

Responses

1. Will Walter.
2. To start out, I put the UML diagram in my notes, and then added to them as I started planning out what the project was going to look like, trying to see what all I could reuse and flag what would need to be altered for each class.
3. Will's strategy was to take more time since we had to work backwards to get all of the tests (sounds like he might have had tests passing in previous assignments?). He got all of his files to pass locally as well, but ended up needing to make additional changes to get the git repo tests to pass.
4. I don't know that there was anything wrong with my strategy, but I did miss something crucial early on. I didn't see the additional link on Canvas to the github repo, and thought that part of the assignment was to create our own repo and tests from scratch, which ended up in a massive headache and panic when I tried to turn it in and realized I had to almost start from scratch.
5. I did not get feedback on my code style for this review.
6. Making sense of some of the error codes I was seeing when my unit tests failed. I think after I got my project into the classroom repo, that was what took the longest. Ultimately I was missing 1 line of code from each of my monster subclasses, but the IDE wasn't giving me very helpful responses. I ended up adding some error checking to the tests to try and pinpoint where the issue was, but had already sunk a great deal of time into the effort. I initially didn't want to alter the unit test files since they were meant to be unaltered (I did set them back to their proper format after I found the problem), but it was ultimately what saved me and got the tests to pass.
7. I was surprised that I had a decent amount of luck getting most tests to pass right off the back when I had all of my code together. I was apparently successful in piecing together what I needed to add based on the UML, prompt, and Unit Tests.
8. I have been struggling keeping up with the pace and learning Java, and was happy to say that with this project and the Strategy Lab, I've been feeling a lot more comfortable putting code together.
9. Watched a lot of Dropout TV the next night (took a night off of studying/homework, which I'm now sort of regretting, but oh well!)