Why I Finally Started Writing

I’ve rebuilt my portfolio more times than I want to admit.

Different layouts. Different animations. Different stacks. Different “perfect” designs that eventually got deleted at 2AM because they suddenly felt wrong.

But one thing stayed consistent:

I never wrote anything.

Not because I had nothing to say.

Mostly because I thought I needed to become an expert first.

The internet makes it feel like every developer blog needs to be some ultra-polished deep dive into system design, AI architecture, or some insane optimization problem.

Meanwhile I’m here debugging Tailwind spacing issues and wondering why my Next.js dev server is suddenly using 75% CPU.

But honestly, that’s probably the reason I should write.

Because most of development isn’t glamorous.

It’s spending hours fixing something caused by a missing class.

It’s rewriting the same component four times because it still doesn’t “feel right”.

It’s opening twenty tabs to solve one problem and somehow ending up reading Linux kernel forums at 3AM.

And weirdly, I enjoy that process.

Why This Blog Exists

I don’t want this blog to become another generic tutorial site.

There are already developers way smarter than me teaching advanced concepts.

What I can do is document the process.

The confusion. The experiments. The mistakes. The tiny breakthroughs.

Right now I’m still learning by building random things that interest me.

Some days I’m training ML models.

Some days I’m rebuilding my portfolio for the fifth time.

Some days I think I know what I’m doing.

Most days I absolutely don’t.

And I think that stage is worth documenting too.

What I’ll Write About

Next.js
Linux
AI/ML experiments
Portfolio design
Random bugs and fixes
Things I learn while building

Probably also some chaotic midnight debugging stories.

Building Things Taught Me More Than Tutorials

The biggest thing I’ve learned so far:

You learn faster when you build things you actually care about.

Not tutorial clones.

Not fake projects.

Real things that break in unexpected ways.

Most of my learning came from messing things up and fixing them repeatedly.

This blog is basically going to be a collection of those lessons.

console.log("starting the blog arc");

The Goal

I’m not trying to sound like an expert.

I just want to build things, learn publicly, and improve over time.

If someone reads this someday and relates to it, that’s enough for me.

This is the first post.

Let’s see where this goes.