CST338 April 2nd - April 8th Week 05

For week 5 we went over our Markov assignment with our team mates...

For this Markov assignment, I worked with two classmates: Kha Ai and Josh. We met up via discord to review our code, discuss challenges, and share ideas on implementing the assignment's requirements. 

I began by writing the initial code stubs. Instead of spending too much time on planning with extensive notes or diagrams, I trusted that the assignment prompt provided enough structure. By creating these stubs early, I established placeholders for all the required methods.

Kha Ai followed the Markov Intro Video and assignment prompt closely. She mentioned that, similar to me, she did not plan extensively on paper before coding. Instead, she jumped directly into writing code by creating stubs first, following the prompt’s order to define their methods, and running their test to confirm functionality.

Much like my teammates, I did not spend a significant amount of time planning on paper. I believe the clarity of the assignment’s requirements encouraged me to dive into coding immediately. This approach allowed for a fast start, though it meant I had to be vigilant during the testing phase to catch any oversights that might have been smoothed out with a bit more upfront planning.

Having completed the assignment and reviewed the different strategies, I would consider making a few changes in future projects such as better initial planning. Jumping right in was efficient but a more structured plan next time would be more beneficial, I only really got away with it by following the prompt which provided me said structured plan.

According to both Kha Ai and Josh, my code generally follows the Google Java Style Guide, though there’s always room for improvement. They highlighted that while my code structure is acceptable, automating parts of the style checking process could streamline compliance.