👏👏 SHAPE REVIEW

This week included peer code review, more unit testing, and a lot of reflection on how I approach programming assignments. I reviewed Luke McCormick’s project and found that his variable names and formatting made the code easy to follow. Most of his tests passed, but one test revealed a problem in ShapeFactory. Malformed input could contain fewer than the expected three values, and the program attempted to access them before checking the array length. Reviewing someone else’s code helped me practice explaining not only what went wrong, but also how it could be improved.

The feedback I received on my own project was mostly positive. My code and tests were cleanly formatted, and everything passed, but I could have included more comments explaining the purpose of certain methods. I tend to focus heavily on making the program work, so this was a good reminder that readable code also needs enough documentation for another developer to understand my reasoning.

The Triangle tests were probably the most challenging part of the assignment, although my biggest struggle was honestly just getting started. Once I stopped staring at the project as one giant task and began working through it one method at a time, it became much more manageable. I am also becoming more curious about inheritance and how classes such as Rectangle and Triangle could share behavior through Polygon.

My favorite part was telling myself that I was building what felt like an unnecessarily serious, enterprise-level factory for creating shapes, including all of the “evil mutant shapes” produced by bad input. I celebrated finishing the week with slushies from my Ninja Slushi served in fancy glasses that I pre-chilled in the freezer, which felt appropriately dramatic.