Week 8

 Week 8 Learning Journal

  1. Understanding Core Concepts Instead of Memorization
    One of the most important things I learned in this course is the value of truly understanding concepts rather than just memorizing information. At the beginning, I relied more on memorization, but I found that I would forget things quickly or get stuck when problems were slightly different. As I started focusing on understanding the reasoning behind concepts, I became more confident and flexible in applying what I learned. I chose this because it completely changed how I approach studying and made learning more meaningful.
  2. Problem-Solving Strategies
    I learned how to break down complex problems into smaller, manageable steps instead of trying to solve everything at once. This included identifying what the problem is asking, organizing information, and solving step by step. This approach reduced mistakes and made difficult tasks feel more achievable. I chose this because it improved both my accuracy and my confidence when facing challenging assignments.
  3. The Importance of Practice and Consistency
    This course showed me that learning requires consistent effort over time. The more I practiced, the more comfortable I became with the material. Even when I didn’t fully understand something at first, repeated exposure helped it “click” later. I chose this because it reinforced the idea that improvement comes from persistence, not just natural ability.
  4. Using Mistakes as Learning Opportunities
    I learned that making mistakes is a normal and important part of learning. Instead of getting discouraged, I started reviewing my errors to understand what went wrong and how to fix it. This helped me avoid repeating the same mistakes and strengthened my understanding. I chose this because it helped me develop a more positive mindset toward challenges.
  5. Effective Use of Resources and Tools
    Throughout the course, I became better at using resources such as lecture notes, practice problems, online tools, and examples. I also learned when to ask for help and how to find reliable information. This made me more independent and efficient in my learning process. I chose this because it helped me succeed even when the material was difficult.
  6. Time Management and Organization
    Another important lesson I learned was how to manage my time effectively. Balancing assignments, studying, and other responsibilities required planning ahead and staying organized. I learned to avoid procrastination and break work into smaller tasks. I chose this because it helped reduce stress and allowed me to perform better overall.
  7. Building Confidence Through Progress
    Over the duration of the course, I noticed a significant increase in my confidence. At first, I doubted my ability to understand the material, but as I improved, I became more willing to participate and take on challenges. I chose this because confidence plays a big role in motivation and success.
  8. Applying Knowledge to Real-World Situations
    I learned how the concepts in this course can be applied outside of the classroom. Seeing real-world connections made the material more interesting and relevant. I chose this because it showed me the practical value of what I was learning.

Comments

Post a Comment

Popular posts from this blog

Week 3

 Week 3 Learning Journal Git is really useful for managing source code. One good thing about Git is that it keeps track of all the changes you make, so if something breaks you can go back to an older version. It also makes it easier for multiple people to work on the same project at the same time without messing up each other’s work. Another helpful feature is branching, where you can work on new ideas or features separately without affecting the main code. Git also shows who made changes and when, which helps when trying to figure out problems. Even though Git is helpful, merging code is not always perfect. Sometimes Git can combine code without showing any errors, but the program still does not work correctly because the changes do not fit well together. This is called a logical conflict. Git also cannot fix situations where developers write code in different ways that do not match. Another problem is when people do not communicate well, which can make merging harder and more con...
Read more

Week 4

One of the most interesting things I learned from Software Engineering at Google is how seriously Google treats code reviews as a core part of engineering culture rather than just a formality. I was surprised to learn that code reviews are not only about finding bugs, but also about improving code readability, maintainability, and ensuring long-term ownership of the codebase. In particular, the idea that reviewers focus on whether future engineers will understand and be able to maintain the code stood out to me. This shifts the mindset from just “making code work” to “making code sustainable.” I also found it interesting that Google encourages small, frequent code reviews instead of large ones, which helps improve quality and efficiency. Overall, this changed how I think about collaboration in software development - code is not just written for machines to execute, but for other engineers to read, understand, and build upon.
Read more