So… this took longer than expected.
Not because I didn’t know how to build a portfolio.
But because I didn’t know what kind of person I was trying to represent.
The Problem Was Never Technical
At some point, I realized:
Building a portfolio is not a frontend problem.
It’s an identity problem.
I could spin up a Next.js app in minutes.
Deploy it in even less.
But answering questions like:
- What do I actually care about?
- What kind of engineer am I becoming?
- What do I want someone to feel when they land here?
That took… significantly longer.
The Long Detour (a.k.a. My "Side Quests")
Instead of building a portfolio, I:
- Tried to relearn mathematics from scratch
- Got obsessed with systems thinking and distributed architectures
- Built projects that sometimes worked, sometimes absolutely didn’t
- Questioned why we design systems the way we do
- Overthought everything (still do)
At one point, I even delayed building this because:
“What if I’m not ready yet?”
Turns out, that question never really goes away.
Why I Finally Built It
Two realizations pushed me:
1. You don’t become ready — you become visible
Waiting for perfection is just a well-disguised form of hiding.
2. Your work deserves a surface
Even if incomplete.
Even if evolving.
Even if messy.
Especially if messy.
What This Portfolio Is (and isn’t)
It is:
- A snapshot of how I think right now
- A collection of systems I’ve built (and broken)
- A space to reflect and iterate
It is not:
- A finished product
- A complete representation of me
- A place where everything is polished
What You’ll Find Here
🧠 Systems Thinking
I like thinking in terms of:
- flows
- constraints
- trade-offs
- emergent behavior
⚙️ Backend & Infrastructure
- distributed systems
- observability
- reliability
- system design patterns
🤖 AI & Research Curiosity
- ML systems
- modeling ideas
- experimental thinking
📓 Reflections (this part)
Probably the most honest section.
A Small Confession
I used to think:
“Once I’m good enough, I’ll showcase myself.”
Now I think:
“Showcasing is part of becoming good.”
What’s Next
- More projects (real, messy, iterative)
- A “learning log” (what I’m currently exploring)
- Deeper system breakdowns
- Maybe fewer overcomplicated thoughts (no promises)
If You’re Reading This
You’re either:
- a recruiter
- a curious engineer
- or someone who also delays things until they become existential
Either way — welcome :)
Closing Thought
This portfolio is less of a destination
and more of a trace of movement.
And honestly,
I’m just getting started.