With whom did you work?
I worked with Branden Woods, Richard Alvarenga, and Taylor Farner. We shared our approaches, reviewed each other’s code, and gave feedback on how closely we followed the Google Java Style Guide. We also discussed what strategies worked best and what we might do differently next time.
What was your strategy for solving the assignments?
My strategy was to take a modular approach—breaking down the prompt into its required classes and responsibilities, then building and testing each part incrementally. I started with the base Monster class, implemented required methods one by one, and ensured each output matched the expected formatting. I also planned early how subclasses would extend behavior without repeating code unnecessarily. I tried to keep my code clean, readable, and well-documented as I went.
Did you start writing code right away? Did you plan it out on paper?
I spent some time up front planning—mentally and in my notes—how the class structure would be laid out. While I didn’t use formal UML tools, I made sketches of inheritance relationships and mapped out which fields/methods belonged where. Once I had a general plan, I jumped into coding and adjusted as needed based on testing and feedback.
What was THEIR strategy for solving the assignments?
Branden focused on building each piece methodically. He started with the Monster class and created each subclass one at a time. He tested as he built and used Git branches to stay organized and avoid getting overwhelmed.
Taylor began by transferring the UML diagram to his notes. He used this to guide his planning, focusing on identifying reusable features and noting where subclass-specific changes would be needed.
Richard took a clear object-oriented approach with well-structured inheritance and emphasis on clean design. His use of comments and clear method responsibility stood out in our code review.
How would you change your strategy having worked on the assignment?
Next time, I’d sync up more frequently during the early design phase. We each had strong ideas for code structure, and comparing notes earlier might have helped avoid duplicated effort. I’d also try to run an automated linter or formatter earlier to catch minor style guide issues right away.
According to your classmates: how well does your code follow the Google Java Style Guide?
Branden said my code follows the guide well overall—clean naming, consistent indentation, well-organized class structure, and clear Javadoc comments. He noted some small improvements like avoiding boxed types and cleaning up comment formatting.
Richard gave Branden similar praise, noting that naming conventions and documentation were excellent, but suggested switching from tabs to 2-space indentation and cleaning up unused imports.
Taylor also showed attention to planning and reuse, and his code structure reflected that well.
Did you know you can automate applying some of the style guide rules?
Yes! I learned about Google Java Format, and going forward I plan to integrate it into my workflow to save time and catch formatting issues early.
What was the most challenging part?
Ensuring that subclass behavior was both unique and respectful of the base class was tricky. Making sure output formatting exactly matched the sample was also tedious—especially with different monsters requiring specific phrases or attacks.
What was the most interesting?
The inheritance structure was the most interesting for me. It was fun to figure out what should be abstract vs. implemented, and how to override methods in creative ways to reflect different monster behaviors.
What are you the most proud of?
I’m proud of how readable and reusable my code turned out. I focused a lot on clean method responsibility, minimizing duplication, and writing comments that actually helped explain logic. The positive feedback from my peers confirmed that this effort paid off.
How did you celebrate completing the assignment?
After wrapping it up, I took the night off and treated myself to dinner and some gaming—simple, but satisfying. It felt good to close the tab and take a mental break.
If you didn’t, how will you celebrate?
Even if I hadn’t celebrated yet, I’d definitely make time. Celebrating wins—even small ones—is important for motivation and balance. As Dr. C says: we’ve got the right to party!