Week 1 Learning Journal- CST438

Before starting CST438, I had the common programmer's perspective: that the central skill lay in writing functional code and mastering complex syntax or data structures. I anticipated the course would focus heavily on project management and architectural design, the mechanics of building features.

However, after reviewing the labs and materials, it's clear that Software Engineering is fundamentally different from programming. It's defined as "programming integrated over time", meaning the primary challenge is not creation, but ensuring the software's sustainability and maintainability over a lifespan that could span decades.

After the first week, my opinion has profoundly changed, shifting the focus from individual code creation to organizational sustainability over time. It's now clear that the central engineering problem isn't getting code to work once, but ensuring it survives, scales, and is safely maintainable for decades. The course emphasizes that the original code is merely the foundation; the real work lies in:

• Process, Not Magic: Recognizing that managing large, long-lived systems requires formal tools and processes , not just relying on individual genius.
• Hyrum's Law: Understanding that everything in a system, even undocumented behavior, will eventually be relied upon, making change incredibly costly.
• Continuous Quality: Quality assurance must be integrated early and continuously (shifting left), using a massive, disciplined test suite to mitigate the exponential cost of catching bugs late in the development cycle.
• Scale and Team: Viewing software development as a team endeavor where effective collaboration, built on the pillars of Humility, Respect, and Trust, is critical for project success.

The course is teaching that engineering requires discipline, oversight, and a systemic approach to keep the software maintainable and valuable for decades, long after the original programmers have moved on.