FAIL
Just Fail Already.
I've never really been afraid of failing.
That doesn't mean failure doesn't hurt.
It does.
I've had projects that didn't work.
Ideas that didn't become what I imagined.
Moments where I looked at something I had built and wondered whether the work had been worth it.
But I don't think I've ever really asked myself:
"Am I capable of doing this?"
I ask different questions.
"What did I miss?"
"What do I need to learn?"
"Did I make a mistake?"
"Do I need to work harder?"
"What can I do differently next time?"
Maybe that's the difference.
I don't see failure as a verdict.
I see it as a report.
Something went wrong.
Now find out why.
"Failure doesn't tell me who I am. It tells me what I still need to understand."
TWO STARTUPS
I've tried building two startups.
Neither became the success I imagined.
At some point, I had to stop them.
And for a while, stopping something I had invested my time and energy into felt like failure.
But looking back...
I don't think those attempts were meaningless.
They taught me things.
They showed me what it takes to turn an idea into something real.
They showed me how different an idea feels once you actually have to build it.
They gave me experience I couldn't have gained by simply thinking about starting something.
And eventually, I understood something:
Stopping a project doesn't necessarily mean the attempt failed.
Sometimes stopping is part of building.
"Not every project is meant to survive. Some exist to teach you how to build the next one."
The real failure would've been letting those projects convince me to stop building altogether.
THEN CAME THAT PROJECT
Then there was the school project.
I was in Grade 10.
I had spent around four or five weeks working on it.
I was reporting directly to my Director.
I had also been asked to integrate AI into the project.
So I started working on it.
There was a person at my school who trained students in AI and was also the CAIO.
He noticed what I was doing.
He asked for the Git repository.
I sent it.
I expected a review.
Maybe feedback.
Maybe suggestions.
Maybe criticism.
Instead...
he looked through it in roughly fifty seconds.
And what followed wasn't something I remember because of the technical feedback.
I remember it because of how I was treated.
I was criticized.
Mocked.
Scolded.
Humiliated.
Demotivated.
The project I'd spent weeks working on suddenly felt like something that wasn't worth much.
Maybe there were genuine problems with the project.
Maybe there were things I should have known.
Maybe he had reasons I couldn't understand at the time.
I can't know what was happening inside someone else's head.
But I know what the moment felt like from my side.
It felt like comparison.
It felt like dismissal.
He had much more industry experience than I did.
I was still a student.
Still learning.
Still figuring out what I was capable of.
And yet, for a moment, it felt like the attempt itself was something to be ashamed of.
"Sometimes the hardest part of failure isn't the mistake. It's having someone make you feel small for making it."
It hurt.
But it didn't end there.
IT DIDN'T MAKE ME ASK "CAN I?"
That's the strange thing.
Even after that...
I didn't start thinking:
"Maybe I can't do this."
I started thinking:
What did I do wrong?
What didn't I know?
What should I have learned?
How can I improve?
How do I make sure I don't repeat this?
Maybe I need to know more.
Maybe I need to work differently.
Maybe I need more experience.
Maybe I need to think more carefully.
"One mindset closes the door. The other asks where the door is."
That's the mindset I try to keep.
THE LAPTOPS
Some failures aren't dramatic.
They don't happen in front of anyone.
They're quiet.
For me, one of those things is independence.
I've earned money.
I've built things.
I've tried to create something of my own.
But I'm still dependent on my father for things.
I needed a new laptop.
My first laptop was my father's.
It was extremely old.
Eventually, I had another laptop.
And that one became a dead unit because I didn't use it enough and didn't take care of it properly.
I think about things like that.
Not because I want to punish myself.
But because I know what things cost.
My parents gave me resources before I was capable of giving anything back.
And I still have things I want to repay.
Maybe that's one of the quieter failures I carry.
I'm not independent enough yet.
I haven't given back everything I feel I owe.
But I'm still working toward it.
"Some failures aren't about losing. They're about realizing you haven't yet become the person you want to be."
THE FAILURE I CHOSE
There was another situation that made me question what failure actually means.
My school's COO once challenged me to hack all the devices.
I believed I could try.
But I didn't want to.
So I didn't.
And later I wondered:
Was that a failure?
I had the capability.
But I chose not to act on it.
That made me think about the difference between being able to do something and choosing to do it.
"Capability creates possibilities. It does not create obligations."
Sometimes not doing something isn't weakness.
Sometimes it's a decision.
I don't regret that choice.
But I remember it.
Because it taught me to question what I even mean when I call something a failure.
I DON'T BREAK
My response to failure is usually the same.
I think.
I analyze.
I find the problem.
I try to understand what happened.
Then I improve.
Sometimes that process takes time.
There are moments when I disappear for weeks.
I isolate myself.
Not because I've given up.
Because sometimes I need silence.
I need to process everything without everyone else's opinions around me.
I need to understand what happened before I decide what happens next.
And eventually...
I come back.
Clearer.
With more questions.
With a better approach.
"Stepping away is not always surrender. Sometimes distance is where understanding begins."
I don't need to respond to every failure immediately.
Sometimes I need to understand it first.
MORE QUESTIONS
Failure changed the way I work.
I started asking more why questions.
Why did this happen?
Why did this work?
Why didn't this work?
What am I missing?
What assumption did I make?
What should I have checked first?
I still move fast.
I still try things.
I still break things.
But I think more now.
I investigate.
I question.
I try to understand before repeating the same mistake.
"Experience isn't simply remembering what happened. It's learning to ask better questions because of it."
Maybe that's what failure gave me.
Not fewer problems.
Better questions.
FAILURE ISN'T THE OPPOSITE OF SUCCESS
I've started seeing the process differently.
START → TRY → FAIL → THINK → LEARN → CHANGE → TRY AGAIN
Failure isn't the opposite of success.
It's part of the process that gets you there.
The important part isn't whether something failed.
The important part is what happened afterward.
Did I learn?
Did I change?
Did I improve?
Did I try again?
"Failure only becomes final when you stop learning from it."
And I'm not interested in making failure final.
JUST FAIL ALREADY
Maybe that's what I mean when I say:
Just fail already.
Stop being so afraid of getting it wrong.
If it fails—
find out why.
If you make a mistake—
learn from it.
If you don't know something—
learn it.
If you need to work harder—
work harder.
If you need to stop—
stop.
If you need to restart—
restart.
But don't turn one failed attempt into a permanent conclusion about yourself.
"I don't need every attempt to succeed. I need every attempt to leave me better than it found me."
That's how I want to measure failure.
Not by whether something worked.
But by whether I understood more afterward.
Because failure never made me smaller.
It gave me more questions.
And questions mean...
there is still something left to learn.