Why Software Engineering Is More Than Just Writing Code

Introduction
I’m Hassan Tech, currently a college student pursuing software engineering. Even though I’m still in school, the journey so far has been eye-opening. I’ve come to realize that software engineering is more than just writing code. In this article, I want to share how it all started, the challenges I faced, and the lessons I’ve learned along the way.
My Initial Assumptions
Before stepping into this field, I spent a lot of time watching YouTube videos about what it’s like to be a developer. That gave me the impression that coding is only one part of the bigger picture. I knew there was more to it — but I didn’t fully understand how much more until I started working on real projects.
My First Impressions
As I began diving into projects and coursework, one thing stood out immediately: the importance of collaboration. Software engineering is not a solo journey. Working with classmates and team members showed me how valuable teamwork really is. I also had to get familiar with tools that make development smoother — from version control systems to connecting backend logic with frontend interfaces.
Challenges I Encountered
At first, project structures felt overwhelming. I wasn’t always sure where to begin, and understanding how everything connected was tough. Code reviews were another challenge. I didn’t know how to properly review someone else’s code or how to handle feedback on mine.
Another adjustment was working with tickets. It wasn’t easy to understand the context behind each task and how it fit into the overall system. These things took time and patience to get comfortable with.
If I Could Go Back in Time
Looking back, I would remind myself to ask more questions without hesitation. There’s no such thing as “too many” questions when you’re learning. I would also start participating in code reviews much earlier — they’re one of the best opportunities to learn from others and improve my own code.
Most importantly, I’d remind myself not to overthink or stress too much about being perfect. Growth takes time.
What I Did to Improve
To keep myself on track, I started keeping an engineering diary where I wrote down:
What I learned each day
Areas I needed to improve
What I’d do differently if I could restart the day
I also took a course on code reviews that completely changed my approach to both authoring and reviewing PRs. Alongside that, I watched videos on common beginner mistakes in tech and built side projects using the same tools we learn in class. That hands-on practice accelerated my learning.
Conclusion
For me, software engineering is not just about coding — it’s about teamwork, problem-solving, and continuous growth. Even as a student, I know this is a lifelong journey of learning, and I’m excited to keep moving forward.
0
5
0