CSU MB

What was your group’s strategy for solving the assignment? My group members each had their own approach. Some started coding right away and refined as they tested. Others planned more like I did. Overall, they seemed to rely heavily on incremental testing and verifying that smaller parts worked before moving forward. How would you change your strategy after working with them? I would adopt a more test-as-you-go workflow. Seeing my classmates test frequently made me realize I should have implemented and verified smaller pieces first. With the IDE problems I had, testing early could have helped me realize my setup was failing before the deadline. According to your classmates, how well does your code follow the Google Java Style Guide? Since my code did not compile correctly, my classmates couldn’t fully evaluate it. However, they mentioned that if I continue practicing structured formatting consistent indentation, clear naming, and method organization it will align better with the Goo...

For Project 1, I worked with a couple classmates while I built out my LDPM (Legally Distinct Pocket Monsters) program. We mainly compared structures, talked through our approaches, and made sure everyone’s classes worked cleanly together. Before jumping into coding, I took a minute to look over Morgan’s Hangman program from earlier coursework. Not to copy code just to get inspiration on how to clean up my structure, keep things organized, and upgrade the way I handled methods and class responsibilities. It helped me rethink how I designed the base class and how subclasses should act differently but still fit the same mold. My process was simple: Understand what the base Monster needed Build that first Add each monster subclass with its own small twist Test attacks/defense as I went Keep everything clean and readable My classmates had slightly different approaches one coded right away, one mapped things out and talking through our styles made the whole thing smoother. They sai...

During week 1, I focused on designing and building the Hangman game in Java. This was my first chance to really dust off my object-oriented programming habits and apply encapsulation, creating separate classes and methods that worked together cleanly. I built small reusable methods for guessing letters, tracking hints, and managing the word array, which helped me see how organized code makes debugging far easier. Setting up branches in GitHub and merging changes through IntelliJ was another learning curve but seeing my commits stack up and actually run without breaking anything was rewarding. What challenged me most was managing so many moving pieces at once: creating logical method groupings, documenting them with Javadoc, and writing code that stayed readable. I also learned to appreciate version control having a branch dedicated to experimentation meant I could try risky refactors without fear. Converting everything into a final PDF for submission tested my workflow discipline. Over...