Week 84

-

 List the 5 most important things that you learned in the course, and why you chose them.

    The five most important things I learned in this course were:

1. Agile Development - I learned how Agile development, including BDD and TDD, helps teams develop software in smaller iterations. I chose this because it showed me how software teams can continuously improve and adjust their work throughout a project.

2. Git and GitHub Projects - I learned how to use Git for version control and GitHub Projects to organize tasks, issues, and pull requests. I chose this because these tools made it much easier to collaborate with a team and keep track of everyone's progress

3. REST APIs with Spring and React - I learned how a React frontend can communicate with a Spring backend through REST APIs. I chose this because understanding how the frontend and backend work together is an important part of building complete software applications.

4. Software Testing with JUnit and Selenium - I learned how to use JUnit for automated testing and Selenium for end-to-end system testing. I chose this because testing helped me understand how developers verify that individual components and the complete application work correctly.

5. Cloud Deployment with AWS - I learned how software can be deployed to AWS and provided as a cloud-based service. I chose this because deploying an application helped connect the development process to how real software can be made available to users.

Comments

Post a Comment

Popular posts from this blog

Week 67

-
     Overall, my experience working on LibreOffice easy hacks went really well. I was able to contribute to a real open source project, which felt meaningful because my work will actually be used by others. One thing that went well was learning how to navigate such a large codebase and follow contribution guidelines. Over time, I got more comfortable looking at the code and understanding how the codebase is connected.     If I could improve anything, I would try to start earlier and ask more questions sooner. At times, I spent too long trying to solve things on my own when I could have saved time by reaching out to my instructor or peers for help. The most impactful part of this experience was seeing my contributions reviewed and accepted, making the work feel real, and showing me how collaboration works in a professional environment.           One challenge I faced was with my environment setup. I got it working for the most part, ...
Read more

Week 58

-
 This week was a little rough because I had so much work. I am still in the process of tackling it, but I figured I'd get this out of the way. I even got called in on my day off, but we push. AVL, 2-3, and max heap trees are all new to me. But it was nice to see something pop up from my Data Structures & Algorithms course from back in the day. Hashing, it's probably my favorite data structure. I think it's super neat and unique. Handling collisions is also fun. I was so stumped on the puzzle this week, but then again,n I always am. After this class engagement, it's straight to the programming assignment for me.
Read more

Week 54

-
 It's been a little over 1 year since I started my journey at Monterey Bay, which is crazy to think about.  This week, we learned about a lot of stuff, including notations for algorithm analysis, definitions of time efficiency notations, nonrecursive algorithms, and more. One thing that stumped me a lot during the readings was the understanding of the difference and how to remember the difference between big O, theta, and omega. I had to use ChatGPT to break the concepts down a lot and explain any misconceptions I had/ reinforce any ideas I got right. For the first time, I got one of the puzzles on my own, the 4-gallon puzzle, which wasn't too bad. I almost got the racing one down, but I said 6 instead of 7, forgetting about the other cars from group A.
Read more