One Minute everything works.

The next minute, the same code suddenly decides it has never seen me before 💀.

So... I started a tech blog.

The hardest part about writing is the start. The general rule is: Whatever you write first is your worst version. And that's OK. You overthink the title, you rewrite your first sentence 10 times, you delete entire paragraphs because they don't sound good enough.

The idea of creating a space to share my thoughts, my journey and the lessons I've learned feels both empowering and vulnerable. Writing is personal, it's like putting a piece of yourself into the world not knowing who exactly will read it or how exactly they'll feel. And that's what makes it exciting.

I attended a blogging masterclass by Nelly Xiaomao and it reminded me that blogging is less about impressing and more about truly connecting with your reader.

I didn't start blogging because I felt like an expert, but because I am tired of pretending that my learning journey has been linear.

Spoiler, it hasn't 😂.

If you’re reading this, welcome to a very honest corner of my tech life, the part that lives between “my code works, I have no idea why” and “why is this still not compiling?”.

I’m a computer science student, still very much in the middle of learning, unlearning, and re-learning. Most days look like this: I get excited about a new tool, I install it, something breaks, I fix it, I forget how I fixed it, I suffer again and the loop repeats itself.

So I made a decision: Instead of letting my struggles disappear into browser history, I’ll turn them into stories.

This blog is not a highlight reel

You won’t find “How I became a full-stack developer in 30 days” here.

What you will find is: the setup that took way longer than expected or the bug that only existed because of one invisible space or the concept that finally made sense after I explained it to myself three different ways.

I want to write the version of tech learning I actually live.

Not the clean one, the real one.

I used to think I had to wait

For a long time, I told myself I’d start writing after I became better.

After I built more projects.
After I felt more confident.

But then I realized something uncomfortable: If I wait until I feel ready, I might never start.

Because learning in tech has no finish line. There’s always a new framework, a new update, a new “recommended way” of doing the same thing you just learned yesterday.

So I’m choosing to write from where I actually am not where I think I should be.

Maybe some of it will resonate with you. Maybe it won't make sense to you. Maybe you'll find it silly. Honestly, who cares? I don't know what I am doing and I don't know where this will go. I am however curious and excited to see how this will turn out.

This blog is me learning out loud. And most of all, I want to remind myself that struggling doesn’t mean I’m bad at tech, it means I’m learning.