Learning Journal

  Wk07/08: Learning Journal Summary   Looking back to HW 1 I would approach it differently on how I initially did it. When I first did it I didn't check the test cases first. Now that I know checking the test cases can help me understand what each function or code does, I will try to read the test cases first before jumping into coding. Second, I would do the functions that doesn't have dependency of other methods. Doing so helps me understand the flow of the logic. While I was initially reading through the documentation, I would jump from one method to another just because I don't fully understand the flow of it. Implementing methods that can work by itself helps me understand the workflow logic. Other than those two things I can't think of any major approach that I need to change. Maybe some minor changes I can do is to clean up the documentation and make sure the TODOs are done before submitting my work.   Overall through out the entire class I'm really proud and...

  Who did you work with?  Tim Shaker   What was your strategy for solving the Markov assignment? My Strategy is the same as last time but with at the same time bringing along the few things I learn from my previous projects and peer reviews feed back. I try to read the whole project and understand what is needed. Briefly go over the test cases on what are being tested to understand the functions. When it actually comes to coding I've use my previous strategy of coding methods that doesn't uses any other methods. I code the field type and constructor first then jump to methods. I was able to run the code successfully initially but was giving the wrong output and only 2 test cases pass. That is the time I try to fix the bug 1 by 1. I look for where the bug is by debugging 1 test cases at a time. Stepping through the code and check the output each steps. Once everything is done and all test cases are passing and main is running, I add the javadocs for methods. At this point...