My CSUMB Learning Journal

Who did you work with? I worked with Isaiah Suarez. What was your strategy for solving the Markov assignment? I dove straight into the code and focused on doing one method at a time, when I would get stuck i would take a break and then focus on trying to see where i went wrong. Did you start writing code right away? Did you plan it out on paper? I started coding right away, treating inline comments as my “paper” plan rather than doing a separate sketch. What was THEIR strategy for solving the Markov assignment? Isaiah took the same approach—he jumped directly into the IDE, outlined logic with comments, and iteratively built and tested without any prior paper drafts. How would you change your strategy having worked on the assignment? Next time, I’d spend a few minutes sketching the overall class design and edge‑case flow on paper or a whiteboard before coding, to reduce minor refactors mid‑development. According to your classmate(s): how well does your code follow the Google Java St...

Project 1 Review With whom did you work? I partnered with Isaiah Suarez. What was your strategy for solving the assignment? I spent about 20 minutes sketching the class hierarchy and main workflows on paper—mapping out Monster’s methods and how each subclass would supply stats—before writing any code. Did you start writing code right away? Did you plan it out on paper? I planned on paper first. Isaiah, by contrast, dove straight into coding. What was THEIR strategy for solving the assignment? Isaiah referred back to the professor’s UML diagrams as needed and iterated quickly in the IDE without formal upfront planning. How would you change your strategy having worked on the assignment? Next time I’ll still paper-plan but also write an initial unit test (TDD style) before coding, while keeping the UML diagram handy. According to your classmate(s): how well does your code follow the Google Java Style Guide? Isaiah confirmed it largely follows the guide—two-space indentation, camelCa...

  1. Code Reviewed Isaiah’s HW01 submission Janaye’s HW01 submission 2. Reviews I Provided Isaiah Variable names: loader , game , random , numberOfHints clearly describe their roles. Consider renaming loop variable c to guessChar . Logic efficiency: Game flow works smoothly. You rebuild the display string and used‑letters list on every guess—fine for small words, but caching the display and using a Set<Character> would speed up lookups. Imports & warnings: No unused imports or compiler warnings. Note that FileNotFoundException is imported but never explicitly referenced (caught by your generic Exception ). Formatting: Indentation and braces are consistent. A couple of lengthy Javadoc lines could be wrapped for readability. Comments: Javadoc is present on every public method—just remove the extra <br> tags. Unit tests: All tests ran unchanged and passed—nice job! Janaye Variable names: PLACEHOLDER , secretWord , guessedWord , remainingGuesses , usedLetter...

   Over the past week, I worked through every step of the Pocket Monsters stub project—from reordering the instance variables in Monster.java to implementing the dice‐rolling methods and creating each subclass stub. First, arranging the fields in the exact order required by the UML took careful attention: I had to manually type each declaration in the right sequence and adjust my getters and setters accordingly. Integrating the utilities.Dice.roll(...) calls into calculateAttackModifier(), calculateAttackPoints(), and calculateDefensePoints() challenged me to locate the correct import and ensure each method signature and return type was precise. I spent a bit of time tracking down a misleading compile error caused by an incorrect package path, which taught me the importance of verifying imports immediately after writing code. Switching to Git introduced its own set of hurdles. Remembering to create and switch to the stubs branch before committing was critical—I initially commi...