Why I Began This Blog

I’ve always felt that most tutorials tell you what to do, but rarely explain how things actually work.

You follow steps.
You copy code.
You get a result.

But the understanding doesn’t stick.

So you re-watch the same tutorial again.
And again.
Just to do the same thing.

This blog exists because of that gap.

I want to build things from scratch — not in the sense of writing everything manually, but in the sense of rebuilding the mental model behind them.

This won’t be a tutorial blog.

I won’t be dumping large blocks of code or telling you exactly what to type. Instead, I’ll focus on how to think about a problem, how the pieces fit together, and why certain approaches behave the way they do.

Most posts will feel more like guided challenges than step-by-step instructions.

The goal isn’t to finish quickly.

The goal is to understand something deeply enough that you could rebuild it yourself.

When I start a series, I’ll usually recommend a language and a small set of libraries. But none of that is mandatory. You can follow along in any language you like, using equivalent tools — or avoiding libraries entirely if you prefer.

Follow this however it works best for you.

I only have one request:

Understand what you build, before you build more on top of it.