Week 15/16: CST 338 Module 7/8

 This is the sixteenth week of the CSUMB computer science program.

HW01 - Markov:

During these two weeks we have implemented various java programs with android studio, which has brought up the notion of revisiting how we would approach the Markov assignment now after having gone through a majority of CST-338 thus far. 

I would look into the prompt first as opposed to creating the comments, as creating comments before the program's methods are implemented seems like putting the cart before the horse. Basically, the idea of commenting beforehand is to prepare ahead of time; however, I can only get the program done before adding comments on what the methods actually do. In the end, I would follow the prompts descriptions; while using the available resources available in canvas to fill in any blanks I have in how the code should work

If there isn't a prompt and instead relies on videos to implement the logic, I would look into the resources available within the course materials and look into any relevant definitions, methods, java logic, etc. as to be more well equipped in implementing the methods, as simply winging it with if-statements and for loops isn't always the greatest way to implement code, as there are many available shortcuts or built-in methods that do the same thing.

Victories:

• I improved on my code implementation and problem-solving approach, as I initially winged it with loops and if-statements to get by. I have gained awareness that structuring a plan before implementation through method stubs, dependencies, etc. can make coding much more efficient in the long run. One of the biggest victories has been transitioning from trail-and-error coding through winging it, to a structured, methodical approach that allows me to create more efficient programs. Therefore, I understand how to develop a more methodical approach to problem-solving.
• I am more comfortable with working on multiple java classes, structuring code using object-oriented principles, and navigating through dependencies between methods. Basically, I have learned how to properly implement a coding structure or style, while understanding the inner methodology that is required to implement and explain programming structures. Compared to HW01, where I relied on loops and if-statements to get me by, I now have a deeper understanding of how to structure Java applications using object-oriented principles, which makes my code more maintainable.
• I now really understand how to work with a group-based Git repository through a GitHub workflow. Before this course, I have never worked with GitHub, thus it was an eye-opener to work with others on a repository to do pull requests, branching strategies, and issue tracking. In the end, learning how to do something you don't know is certainly a game changer, especially when it's something that can get multiple people to work on.