For this assignment, I worked with Alex Miller and Mathew Johann. My strategy was to tackle the easier methods first, saving the hardest method for last. This approach worked well for simpler parts of the project, such as the Book.java Shelf.java, and Reader.java files. Since these classes were straightforward, I felt comfortable jumping into the code right away. However, I realized this approach might not be ideal for more complex programs. After hearing their strategies, I learned that it's better to break down each task into smaller parts and tackle them one at a time. I really like the idea of creating diagrams and use cases to visualize how each method should function within the overall structure.
Reflecting on this experience, I recognize that my strategy was efficient for simpler code but could have been more organized and structured for complex projects. For future assignments, I plan to incorporate the strategy that I learned from this feedback by sketching out diagrams and use cases before coding. This will help me better understand the interconnections between different methods and anticipate potential issues early on.
My code largely followed the Google Java Style Guide, especially in terms of naming conventions and code structure. I also learned that certain style guide rules, like consistent indentation and spacing, can be automated, which would make it easier to maintain clean and readable code. I plan to explore these automation tools to ensure I consistently follow the style guidelines on future projects.
No comments:
Post a Comment