I write when something stays with me longer than it should.
Sometimes it's a concept that refuses to settle.
Sometimes it's a mistake I don't want to repeat.
Sometimes it's just the need to explain something to myself clearly enough that it stops feeling vague.
Most of what you'll find here didn't begin as "content."
It began as notes, experiments, or quiet attempts to understand something properly.
on LinkedIn
I write about [JavaScript] the way I learned it — slowly, practically, and without skipping steps. I share beginner projects not to show results, but to show process. Thirty days of building small things teaches you more than one big idea ever will.
→ View on LinkedInon GitHub
You'll find my [TypeScript] notes. These are structured, evolving, and sometimes unfinished. They exist so I can come back later and remember why something works the way it does, not just that it works.
→ View on GitHubon Medium (Coming Soon...)
I write longer pieces — mostly [Java] notes and explanations. That's where I allow myself to slow down. To explain fundamentals carefully. To connect ideas instead of rushing toward conclusions.
→ View on MediumNone of these live in isolation.
They're all part of the same habit: understanding by writing.
This page doesn't promise polished essays or viral takes.
It's more like a trail — moments where something clicked, didn't click, or slowly started to make sense.
If you're here to skim, that's fine.
If you're here to learn alongside me, even better.
These articles are less about teaching and more about thinking out loud — one concept at a time.
a quiet note
Everything here is still in motion.
Some ideas will grow.
Some will change.
Some will be replaced entirely.
That's intentional.
Learning doesn't happen all at once — and neither does writing.