For a long time, I thought being a software engineering student was mostly about learning programming languages, completing assignments, passing exams, and building projects whenever they were required.
I could build things. I could learn a new technology when I needed to.
But somewhere along the way, I realized that knowing how to code wasn't the same as becoming a software engineer.
I started noticing the gap between what I knew and what I could actually do.
I could follow tutorials, but sometimes struggled when there was no tutorial to follow. I could start projects, but finishing and maintaining them was a different story. I knew different technologies, but I didn't always understand why I was choosing them.
That realization changed something for me.
I stopped wanting to simply learn more technologies and started wanting to understand how to build things properly.
I started caring more about writing code that someone else could understand. About architecture. About debugging instead of immediately looking for the answer. About understanding why something broke rather than just fixing the error. About reading documentation. About finishing projects.
And most importantly, I started treating software engineering as a skill I was building not just a degree I was studying for.
Working on real projects made that difference even clearer.
Real projects don't give you perfectly defined requirements. They don't tell you exactly which technology to use. Things break. Requirements change. You make decisions with incomplete information. Sometimes the problem isn't even technical.
That's where I started learning what software engineering actually feels like.
I also realized that I don't want to spend the next few years simply collecting technologies I have touched.
I want to become someone who can look at a problem, break it down, make thoughtful technical decisions, build a solution, and keep improving it when things don't go as planned.
I’m still very much learning.
There are things I don't understand yet. There are projects I haven't finished. There are technologies I haven't touched. And there are plenty of mistakes waiting for me.
But that's exactly why I'm taking it seriously now.
Not because I suddenly know everything.
Because I finally understand how much there is to learn.
And maybe that's what changed for me.
I stopped trying to look like a software engineer and started working toward actually becoming one.