Studying computer science did not turn me into someone who sees code everywhere.
But it did change the way I look at things.
I think I became more curious about what happens underneath the surface.
When an app works smoothly, I wonder what had to happen behind it.
When something does not work, part of me immediately wants to understand why.
You start noticing that so many things that look simple from the outside are made of hundreds of tiny decisions.
A button is never just a button.
A recommendation is not random.
A map does not simply know where you are.
A system that seems effortless to use may have taken months or years to build.
Computer science also taught me that problems rarely arrive in the neat form they have in exercises.
In real life, half the work is figuring out what the problem actually is.
You try something.
It fails.
You change one thing.
Something else breaks.
You stare at it for much longer than you would like to admit.
And eventually, sometimes almost accidentally, you understand it.
I think that way of thinking followed me outside university.
Breaking bigger problems into smaller ones.
Looking for patterns.
Questioning assumptions.
Trying again when the first solution does not work.
It also changed the way I see technology.
Before studying it, technology often felt like something that simply existed.
Now I notice the choices behind it.
What it can do.
What it cannot do.
What someone decided it should do.
And perhaps most importantly, who those decisions affect.
The more I learned, the less technology felt like magic.
But somehow, that did not make it less interesting.
It made it more interesting.
Behind almost everything digital is someone who once sat in front of a problem and thought: There has to be a way to make this work.