CST438 Learning Journal 1

Before starting this Software Engineering course, I expected it to focus primarily on programming techniques and learning how to write better code. I assumed most of the class would be about using different programming languages, design patterns, and frameworks to build applications. I also expected to spend time learning debugging techniques and improving coding efficiency. While I knew teamwork might be discussed, I did not realize how much emphasis software engineering places on the overall process of developing and maintaining software.

After completing the first week, my perspective has changed. I now understand that software engineering is much broader than just programming. Writing code is only one part of creating successful software. The course introduced concepts like maintainability, sustainability, testing strategies, version control, and the importance of making design decisions that support long-term development. These topics highlighted that software often lives for many years and may be worked on by many different developers, making clear organization and documentation just as important as writing functional code.

I also found it interesting to learn about ideas like shifting left, which encourages considering testing, security, and performance early in development instead of treating them as afterthoughts. This approach made me realize that preventing problems is usually more effective than fixing them later. Additionally, discussions about trade-offs and deferred maintenance showed that software engineering often involves balancing ideal solutions with practical constraints such as deadlines and available resources.

I now see it as a discipline focused on building software that is reliable, maintainable, and adaptable over time rather than simply creating programs that work. I expect the rest of the course to continue developing these principles while also teaching practical techniques that will help me become a more effective software developer.

Comments

Post a Comment

Popular posts from this blog

Computer Science BS Journal (CST334) : Week 3

  This week in CST334 our lectures covered: Address Spaces, C Memory API, Address Translation & Base-and-bounds, Segmentation, Free Space Management. We also started working on our first group project this week. In this learning journal I'll write and explanation/what I think to be the most important bits of each subject. 1. Address Spaces An address space is the range of memory addresses that a process can use. Each process has its own virtual address space, isolated from others, managed by the operating system. Key Takeaways: Provides process isolation . Helps with security and stability . Enables virtual memory and memory protection. 2. C Memory API The C memory API includes functions for dynamic memory allocation and deallocation: malloc() , calloc() , realloc() , and free() . Key Takeaways: malloc(size) allocates a block of memory. calloc(n, size) allocates and zero-initializes memory. realloc(ptr, new_size) resizes previously allocated memory. ...
Read more

Computer Science BS Journal (CST334) : Week 5

    This week in CST334 our lectures covered: Concurrency and Threads, Threads API, Locks, and Lock-based data structure. In this learning journal I'll write and explanation/what I think to be the most important bits of each subject. We also had our midterm this week and I didn't do as good as I wanted to, I definitely need to focus some more on my studies. Concurrency and Threads Concurrency is the ability of a system to handle multiple tasks at the same time. Threads are the smallest units of execution within a process. Concurrency allows threads to run independently, improving efficiency, especially on multi-core processors. Key Takeaways: Concurrency enables better CPU utilization. Threads share the same memory space within a process. Context switching allows threads to appear to run in parallel. Can lead to race conditions if not properly synchronized. Threads API Threads APIs provide the functions and mechanisms to create, manage, and synchronize threads....
Read more

Computer Science BS Journal (CST334) : Week 8

 This was the final week for CST334. I just finished my final exam a little while ago and I can't tell you how happy I was that the time we were given to finish the final was two hours rather than one. My midterm suffered because I could not finish my exam in time, I had to "YOLO" a few questions for partial credit and ended up misreading two questions and putting answers not even related to those questions haha.  CST334 has been an amazing class. My biggest takeaways from CST334 had to of been Address Spaces, Files and Directories, and File Systems(Access and Data). These were honestly some of the things that were easier for me to understand so I feel like I learned the most from these topics. I think the biggest challenge for me in this class was learning to convert hex to decimal and vice versa. I know that seems ridiculous but only at the very end of the class did I get the hang of it and realize how simple it was. Another challenge for me was trying to remember all o...
Read more