Debugging My Way Out of the Monster Mash

For this learning journal, I worked with Erin Hurley.

I started coding right away, using sticky notes to jot down ideas and keep track of important logic and structure. Interestingly, I began by working on the first and second child classes first—just to make sure I understood the requirements and structure—before going back to complete the Monster base class. This helped me get a clearer sense of how everything would connect. I approached the assignment step by step, focusing on writing modular, organized code and using print statements to help with debugging when needed. My notes helped me stay on track and adjust my approach as I built out each piece.

My classmate said they felt overwhelmed at first and accidentally opened a project within another, which caused issues. After getting advice from Polina, they focused on building the simplest functions first, since the complex ones relied on them. They didn’t plan on paper due to the structured nature of the assignment. They finished all the classes before running any tests, which they later realized made things harder. Reading the README and grading rubric after finishing led to last-minute fixes—but they took it all in stride.

If I were to redo the assignment, I would spend more time planning out the structure before jumping into the code. While starting with the child classes helped me get a feel for the task, I realized that fully understanding and setting up the Monster base class first would have made everything smoother. I’d also sketch out a rough class diagram or flow on paper to map relationships and avoid rewriting sections later. Overall, I’d aim for a more top-down approach with clearer planning upfront to save time and reduce trial and error.

My code followed the Google Java Style Guide fairly well. They noted that my indentation and naming conventions were consistent and readable. However, there were a few areas I could improve on, like spacing around operators or keeping line lengths shorter for readability. Overall, the feedback was positive, with minor suggestions for polishing.

The most challenging part was organizing the Monster base class in a way that all the child classes could extend it cleanly without running into conflicts or redundant code. It took some trial and error to get the right balance between abstract methods and shared logic. Managing method overrides and making sure each child class had the proper behaviors—without repeating too much—was tricky at first. Once I got the structure down, everything started to fall into place, but getting there required some careful thinking and refactoring.

The most interesting part was seeing how each child class could take the base class structure and behave differently through overridden methods. It really showed the power of inheritance and polymorphism in a practical way, and it was satisfying to test and see the different monster behaviors come to life.

I’m most proud of how clean and modular my code ended up. Even though there were some bumps along the way, I managed to make each class readable, reusable, and easy to test. Debugging became much easier once the structure was solid, and the logic flowed nicely between the classes.

After submitting the assignment, I treated myself to a good cup of coffee and relaxed with a Netflix series. It was a small celebration, but it felt well-deserved after balancing school and work.