Linda’s Learning Journal - CSUMB

  Open Project 1 : Solitaire. Read through your own code. The code is organized and has a lot of comments. The comments are detailed and provided good information on what each method is doing. There were no issues with the code. The code was able to build and run. Going back through the code, I would leave a note of where the TODOs were and mark them as completed, so that I can recall exactly where I contributed to the pre-written code from the instructor. For the Pile class, I would change the order in which I wrote the code so that the code is easier to read and follow. The order I would change is for the methods in the java class to follow the UI test class. This would help to look for certain certain methods and what is being tested. Celebrate two victories from Project 1. Two victories of Project 1 is the code was able to build and run successfully and I learned a lot of how-to’s through the TODOs and had something to start with. Initially during the first part of the ...

I worked with Nettra, Kevin, and Sean on this review. We collaborated on Discord and shared our code that way. Next time we could dedicate a time to meet and take turns running through our code. When I approached the Markov assignment, I first watched the intro, read the prompt all the way through, went through the code and wrote everything out in pseudocode, and then proceeded to code going down through the prompt. Initially I felt stuck on how to get started after reading the prompt, but once I got the pseudocode down the coding part went smoothly. I did also get stuck when I believe I had finished but ran into errors when running the tests. I was able to resolve the error when using the debug tool to see where my errors were. My classmates approached the problem in a similar manner, one difference was they did it without the pseudocode. I don't think I would change my approach, because putting it in pseudocode helps me understand the steps a lot clearer and provides me a map of ...