Week 77

-

 What did you expect a course in Software Engineering would cover?   

    Honestly, I never really gave it much thought. Even before starting my Computer Science journey, I always heard the position of "Software Engineer" mentioned so much. It seemed like a dream job back then, and it still is one today. When I hear Software Engineer, I think of someone in a company who is a programmer. Working together with other programmers to create something. So before week 1, I expected to just learn more about programming, whether that be new concepts, frameworks, and/or developer tools.
 
    After completing week 1, I realized it is much more about learning to write code. Software engineering is programming integrated over time, meaning you will learn how to build software that can be maintained, adapted, and scaled over many years. I expect to learn topics such as maintaining software over time, working on teams, scalability, managing tradeoffs, and testing quality and assurance. 

    I learned the difference between a programming class that teaches you how to write code, while software engineering teaches how to build, maintain, and evolve software successfully over time with other people. 

Comments

Post a Comment

Popular posts from this blog

Week 27

-
 Write a 1 - 2 paragraph journal post, of at least 250 words, on what you learned this week in CST 334.      This week in CST334, I deepened my understanding of memory virtualization, focusing on segmentation as a key mechanism to optimize memory usage. Segmentation divides a process’s address space into logical segments (code, heap, stack), each with its own base and bounds registers. Unlike the simpler base-and-bounds approach, which allocates the entire address space contiguously, segmentation allows the OS to allocate only the physically used portions of memory. This significantly reduces internal fragmentation while enabling sparse address spaces, where large virtual memory regions don’t require physical memory unless actively used.      The hardware translation process became clearer. Virtual addresses are split into a segment selector (top bits) and an offset (remaining bits). The hardware combines the segment’s base register with the offset to ...
Read more

Week 32

-
 Wow... It really is the last week of CST 334. I vividly remember the week when we went through and downloaded Docker. Using PowerShell and terminal seemed like something straight out of a movie, but learning low-level stuff like that is key to success as a computer scientist. The PA codes were also a hurdle to get accustomed to. Coding tasks are always daunting, but doing it in C was even more of a pain. But once again, languages where you're in charge of memory allocation are very important and equally important to learn. Over the course, we learned about processes and how you manage them. We had a lot of emphasis on memory virtualization, and then we had the midterm. Then, concurrency and persistence. And as I'm writing this, I'm preparing for the upcoming final exam. As for the final exam, I will try to be more cognizant of the time. On the previous midterm, I had been surprised by the time, as I thought I had more. I did all the big questions to realize I only had 12 m...
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