This week, I worked with Adan to tackle aspects of Project 1, focusing mainly on the Book, Reader, and Shelf classes. Adan's feedback on my code was very helpgull. He spotted a major hiccup in my Book.java Class that had been causing headaches across my entire project. We started off storng looking through code, but soon realized the importance of slowing down. Adan brought a sharp eye for detail, emphasizing clean code practices and ensuring our code aligned closely with the project's requirements. Looking ahead, I'm definitely taking away the lesson to integrate more planning and regular code reviews into my workflow to nip issues in the bud early on and maintain a smoother development process. It was a reminder that sometimes a fresh perspective and a new approach can make all the difference in untangling coding issues.

Comments

Post a Comment

Popular posts from this blog

This week I focused a lot on understanding time complexity and recursive analysis. It was challenging at first to figure out how to break down recursive functions and write the correct recurrence relations. Applying the Master Theorem was especially tough because I had to carefully identify each part of the formula and decide which case applied. I also spent time reviewing the difference between Big O, Big Omega, and Big Theta, which helped me better understand how to describe the efficiency of an algorithm. These concepts took time to click but working through examples really helped.
Read more
Over the past few days I completed the final sections of the Google Cloud Digital Leader certification. These modules reinforced my understanding of how cloud systems scale, maintain availability, and how services like compute and storage work together in real-world environments. At the same time I worked on drafting my capstone presentation. I organized it around the three certifications and focused on clearly explaining what I learned and how the concepts connect. Overall, this stage was about bringing everything together and making sure I could clearly communicate what I’ve learned.
Read more
When I started this course I thought Software Engineering would mostly be about writing code and learning new tools. After week one I see it’s more about understanding how different parts of a system connect and work together. Building and testing the REST API showed me that software isn’t just about making something run, it’s about planning, structure, and testing to make sure it’s reliable and easy to maintain in the long run.
Read more