Learning to Be Comfortable with the Uncomfortable

I grew up as an insecure kid, and that insecurity still writhes inside my weak heart.

It has taken many forms over the years. Sometimes it looks like the fear of meeting new people. Sometimes it is the hesitation to speak to old friends who seem more accomplished. Sometimes it shows up as defensiveness when someone criticises me. At other times, it is the fear of the future, the fear of the unknown, or the uncomfortable feeling of not being able to think on my feet.

If I were to write about every form my insecurity takes, I could probably write a thesis.

So, in this piece, I want to focus on just one—the insecurity I experience as a computer science professional.

The insecurity of not being able to solve a difficult problem.

There is something almost ironic about this.

I work in a profession where my job is, quite literally, to solve problems. Every day brings a new bug, a new failure, a new system behaviour that doesn't make sense, or a problem whose answer isn't immediately obvious.

And yet, when I encounter something genuinely difficult or ambiguous, my first reaction isn't always curiosity.

Sometimes, it is fear.

There is a sinking feeling in my stomach when I realise that I don't understand something completely. It becomes worse when someone starts probing deeper—asking the next question, and then the question beneath that question—and I realise that there are layers of the problem I haven't even considered.

What if I don't know enough?

What if they realise I'm not as capable as they thought?

What if I can't figure this out?

And sometimes the thought goes as far as:

Maybe I should just quit. Maybe I'm not good enough for this job.

It sounds irrational when written down.

But when you are in the middle of it, it feels very real.

I think a lot of this comes from an old expectation I have carried for a long time—the expectation that I should know everything, or at least know enough to always be on top of things.

For a long time, I associated competence with certainty.

If I was competent, I should know the answer.

If I was good at my job, I shouldn't be confused.

If someone asked me a question, I should be able to answer immediately.

But as I have grown in my career, and especially as I have taken on more responsibility, reality has slowly dismantled this idea.

The more I learn, the more I realise how much there is that I don't know.

And perhaps that isn't a sign that I am becoming less capable.

Perhaps it is a sign that I am working on harder problems.

At some point, you realise that ambiguity isn't an exception to the job.

Ambiguity is the job.

There will be days when the problem is poorly defined. There will be situations where the logs don't tell the whole story. There will be questions you haven't thought about. There will be people who see a dimension of the problem that you missed.

And there will be moments when you are standing in the spotlight, trying to think while a small voice inside your head is screaming that you are being judged.

The challenge, then, is not to magically become someone who knows everything.

The challenge is to become someone who can stay with the problem even when they don't know the answer.

To pause.

To breathe.

To ask another question.

To break the problem down.

To say, “I haven't considered that angle yet. Let me think about it.”

To communicate what you know and, more importantly, what you don't know.

To investigate instead of panic.

To deliberate instead of react.

This sounds simple when written as a list.

It isn't.

Because the real battle happens before all of this.

It happens in that few seconds when ambiguity triggers the fight-or-flight response. When your heart sinks. When your mind suddenly goes blank. When the spotlight feels unbearably bright. When not knowing the answer feels like evidence that you are not good enough.

That is the discomfort I am learning to sit with.

Not knowing.

Being questioned.

Being unsure.

Being watched while I think.

Knowing that I may be wrong.

Knowing that someone may form an opinion about my ability.

And still staying.

Perhaps this is what professional maturity looks like—not the absence of insecurity, but the ability to continue working while insecurity is sitting right beside you.

I am slowly learning that I don't have to eliminate that sinking feeling before I can act.

I can feel uncomfortable and still investigate.

I can feel judged and still think.

I can feel inadequate and still learn.

I can not know the answer and still be capable of finding it.

Maybe being good at difficult problems isn't about having an unusually powerful brain that immediately sees the solution.

Maybe it is about developing the patience to remain in the discomfort long enough for the solution to emerge.

And perhaps that is a skill worth practising—not just for my career, but for life.

Learning to be comfortable with the uncomfortable.