The Data Structures grades had just been posted.
I found my name, saw the number beside it, and went quiet. Not dramatic quiet. The kind of quiet where your face stays normal because there are people around, but something inside you has already sunk.
Right beside me, a classmate closed his laptop after solving the dynamic programming problem our professor had given "to challenge the whole class." He had finished it in five minutes, yawned, and said, "That one was easy."
I had spent two evenings on the same problem. Three pages of scratch paper. Several tabs open. A headache. And still, I could not explain where my logic had fallen apart.
Around me, people were discussing big-O and edge cases as casually as deciding what to eat for lunch. I sat there with a blank mind and one small, sharp question:
Do I even belong here?
I was grading myself with everyone else's best subject
For a long time, I lived with the feeling that I was the slowest person in rooms full of fast people.
The unfair part is what I did with that feeling. I did not compare myself with one real person. I compared myself with a fictional monster I had assembled from everybody's strongest traits.
One friend understood algorithms quickly, so I made speed the standard. Another remembered concepts after one lecture, so I made memory the standard. Someone else had side projects, clean GitHub repos, strong English, confident presentations. I kept collecting the best part of each person and stitching them into one impossible human.
Then I stood next to that imaginary person and wondered why I felt small.
The grade sheet only made it worse. It gave me a number, and my younger brain translated that number into a verdict: you are not good enough to be here.
At night, I replayed the same questions. Did I choose the wrong major? Was I pretending? Had everyone else received a manual I had somehow missed?
It is painful when a score stops being feedback and starts becoming an identity.
Tech is bigger than the exam I was failing
It took me a while to understand something I wish someone had said more clearly:
Technology is not one narrow hallway called "be excellent at algorithms or leave."
It is a huge ecosystem with many kinds of intelligence inside it. Someone designs distributed systems. Someone builds infrastructure. Someone protects security. Someone understands data. Someone writes documentation that saves a team from chaos. Someone thinks about onboarding, accessibility, visual hierarchy, user trust, empty states, error messages, and all the tiny moments where a product either respects a person or exhausts them.
For years, I kept standing in one corner, the corner where I felt weakest, and using that corner to sentence my whole self.
There is a line people often repeat: if you judge a fish by its ability to climb a tree, it will spend its whole life believing it is stupid. I know the quote is overused, but I still understand why it stays around.
I was that fish. Sitting under the algorithm tree, watching others climb quickly, forgetting that maybe my real test was somewhere else.
The problem was not that I had no ability. The problem was that I had mistaken one exam for the entire world.
The first time a different corner felt like home
Then I took a course that touched experience design, and I opened Figma mostly out of curiosity.
Something changed.
Spacing elements until a screen felt calmer. Choosing a shade of blue that made an action feel trustworthy instead of cold. Rearranging a flow so a stranger could move through it without someone standing beside them explaining everything. Writing button copy that removed a little anxiety. Watching how one small friction point could make a whole feature feel heavier than it was.
Those things did not feel easy exactly, but they felt alive to me. I could sit with them for hours and still want to improve one more detail.
The patience I struggled to find for a broken algorithm showed up naturally when I was shaping an interface. That did not make me better than the algorithm genius beside me. It made me different.
He was building the engine. I was drawn to the steering wheel, the seat, the dashboard, the feeling of whether a person trusted the car enough to drive it. The product needed both.
That realization did not give me permission to become lazy. I still needed technical literacy. I still needed to understand enough code to collaborate well, enough logic to not design impossible things, enough humility to keep learning.
But I no longer had to turn someone else's gift into proof of my failure.
So I made a decision my younger self would have called betrayal: I stopped trying to become perfect at algorithms.
I studied enough to understand. I practiced enough to pass what needed passing. But I stopped treating every slow solution as evidence that I had chosen the wrong life. I put that energy into the corner that kept pulling me back: product, design, user experience, the human side of technology.
The relief was almost embarrassing. Nobody had locked the weight onto my shoulders. I had strapped it there myself, because I thought struggle in the wrong place looked more respectable than curiosity in the right one.
If you are sitting under your own tree right now, watching other people climb and feeling foolish, I hope you pause before calling yourself untalented.
Maybe you are not lazy. Maybe you are not behind. Maybe you are using the wrong ruler.
This does not mean every hard thing should be abandoned. Some discomfort is the price of growth. But there is a difference between a challenge that stretches you and an arena that slowly convinces you that you have no value.
Pay attention to where your patience appears without needing to be dragged. Pay attention to the problems you keep thinking about after class, after work, after everyone else has moved on. Pay attention to the kind of difficulty that makes you tired but not smaller.
The fish does not need to win a tree-climbing contest to prove it is real.
It needs water. Then it needs the courage to stop apologizing for swimming.