CST 338: Wk05 Learning Journal Markov
Tim Shaker
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 I understand everything fully so I can write proper documents for each methods and fields.
For this particular assignment I believe I was spending more time debugging and fixing the logic of my methods versus to setting up everything. Error logic is the worst bug one can encounter since the code runs with no error, so I am left to just stepping through everything and see where I did wrong. Maybe next time double or even triple check if methods are properly coded with the required logic.
Comments
Post a Comment