About
Most of us learn things only when life demands them.
A new project arrives, and suddenly we need to understand Docker. A system breaks, and we rush to learn databases. AI becomes impossible to ignore, and we spend weekends watching videos trying to catch up. Learning becomes reactive. Necessary. Urgent.
For a long time, I learned that way too.
But I remember listening to senior engineers talk about servers, databases, caching, and system design — and realizing how little I understood. I didn't need any of it at the time. I was just curious and wanted to understand what everyone was talking about.
That curiosity never really went away.
I consumed endlessly — reels, shorts, random videos, blogs, YouTube tutorials, articles, and tweets. Much of it was just mindless scrolling disguised as productivity. There was always another playlist to save, another tab to open, another idea I promised myself I would learn someday. I kept assuming I would get to it later.
Eventually, I realized that if I was going to spend time consuming content anyway, I could spend it learning something useful and documenting it. Understanding doesn't appear when we need it. It compounds long before that.
That simple thought became Learn It Anyway.
Not as a course.
Not as a portfolio.
Not as a personal brand trying to sound like an authority.
Just a notebook on the internet.
A place to document curiosity in public.
Most of the notes here revolve around software architecture, backend engineering, databases, AI, DevOps, and engineering decisions. Sometimes they drift into books, mental models, or ideas that seem too interesting not to write down.
The topics change.
Curiosity doesn't.
Learn Before You Need It
That's the philosophy behind everything here.
Because understanding something before necessity arrives changes the way you think. It creates intuition. It makes decisions easier. It makes adapting easier.
Technology changes constantly. Frameworks rise and disappear. Trends come and go.
But understanding how things work keeps paying dividends.
Learning isn't an expense.
It's compound interest.
Curiosity Is an Advantage
Darwin's idea of "survival of the fittest" is often misunderstood. The winners aren't always the strongest or the smartest.
They are the ones that adapt.
And in technology, adaptability comes from curiosity.
That matters even more now.
As AI becomes increasingly capable, writing code is becoming easier. But software engineering has never been just about typing code.
Someone still has to decide.
_Monolith or microservices?
_PostgreSQL or MongoDB?
_Redis or no Redis?
_Optimize now or later?
_Build it or buy it?
Trade-offs don't disappear. If anything, they become more important.
Good decisions require understanding.
Not memorization.
Not blindly following trends.
Understanding concepts.
Building intuition.
Thinking in trade-offs.
That's what I'm trying to learn.
From Consuming to Creating
For years, I consumed far more than I created.
Books. Videos. Podcasts. Courses. Endless information.
And plenty of reels, shorts, and hours lost to mindless scrolling.
Eventually, consuming stopped being enough.
Writing became a way to understand.
Explaining became a way to think.
Sharing became a way to learn.
This website is an attempt to create more than I consume.
Less scrolling.
More making.
So I decided to learn. One rabbit hole at a time.
No mentor to guide me through it. No team to bounce decisions off. No production system to test ideas against. Just curiosity and the internet.
And I kept running into reasons not to bother.
I can't implement this at scale right now.
I don't have the context a senior engineer has.
What if I get it wrong?
But I kept going anyway.
Even without a mentor — I'll learn it anyway.
Even without a way to implement it right now — I'll learn it anyway.
Even if I end up getting half of it wrong — I'll learn it anyway.
That's where the name came from.
Learning in Public
Nothing here is presented as absolute truth.
Some ideas will change.
Some opinions will be wrong.
Some notes will age badly.
That's fine.
Knowledge evolves, and hopefully so will I.
If you know something I don't, corrections are welcome.
If you're learning too, you're welcome to learn alongside me.
Because the goal isn't to teach from a pedestal. The goal is simply to understand how things work — and leave behind notes for whoever might find them useful.
Learn It Anyway is a curious engineer's notebook on the internet.
Curiosity over credentials.
Understanding over memorization.
Adaptability over certainty.
Creation over consumption.
And the belief that some things are worth learning long before life asks for them.