Blog

I have wanted a small personal website for a long time. Nothing huge, nothing fancy. Just a tiny corner of the internet with my name on it, where I can put my resume, write about things I find interesting, and experiment a bit.

Social media never really felt like the right place for that. Posts disappear in the feed, the format is limiting, and everything is optimized for engagement instead of thought. I wanted something slower, calmer, and more “mine”.

So I finally stopped overthinking it and decided to just build this site.

Why a personal site at all?

There are a few reasons:

• I like the idea of having a “home base” online instead of being just another profile on some platform.
• I want a place to write about things I learn or find cool, without worrying whether it fits into a specific niche or trend.
• I wanted an excuse to build something from scratch, even if it is very small.

This blog will mostly be in English, and it will not always be about tech. Yes, I work with tech and most of my day is about computers, code, and debugging. But I do not want this space to be only about that. You can expect a mix of:

• tech and programming notes
• random thoughts
• small experiments
• things I wish I had read earlier myself

The usual enemies: front-end and design

The biggest obstacles to building this site were not the backend, not the hosting, not the domain.

They were front-end and design.

For some reason I have never really clicked with front-end work. I am much more at home in the terminal and in text-based tools than in visual editors and design software. I like things that are clean and simple, but turning that into an actual layout with CSS and components always felt like a different skill set.

There was also this little voice in my head:

“If I build the front-end myself, what if it looks bad?
And what if I want to update the design later? Will I regret everything?”

For a while that worry kept me from getting started. Instead of writing code, I kept thinking about design decisions and looking for the perfect plan before I even had a basic page online.

Choosing simplicity and a bit of nostalgia

Eventually I decided to stop chasing a perfect design and be realistic about what I actually needed: a simple site that works, is readable, and is easy to maintain.

I am not trying to be a designer here, and that is completely fine.

So I leaned into simplicity and realism:

• a very simple layout
• minimal styling
• a slightly old-school, early-web vibe

I like those older websites that are mostly text, with simple navigation and not too many distractions. I tried to bring a bit of that feeling here. This site is not trying to win any design awards; it is just trying to be clear, readable, and a little bit charming in its own way.

The nice part is that this simplicity makes future updates easier. If one day I want a bigger redesign, I can ask for help or evolve the design slowly, instead of being stuck in a giant mess of CSS and animations.

It actually works on mobile

One thing I am genuinely happy about is that this site works properly on mobile.

I paid attention to the layout so that it stays readable and usable on phones. Nothing fancy, just responsive enough to not break.

If you are reading this on your phone and something looks completely broken, feel free to tell me so I can pretend I am not upset and then fix it.

Building it

Once I stopped overthinking the design, the actual build process was surprisingly simple.

The backend and structure of the site came together fairly quickly. The hardest parts were mostly:

• dealing with HTML and the kind of front-end basics I usually avoid
• deciding what to actually put on the site
• figuring out what to write in this very first blog post

In the end I decided to just be honest and write about the story behind the site itself. You are literally reading the “why” of this website.

What I might write about

There is no fixed posting schedule for this blog. I am not planning to publish weekly or monthly just to fill a calendar. I will write when I have something that feels worth sharing.

When I do write, it will probably be about things like:

• notes on things I learn (mostly tech, but not only)
• opinions about tools, frameworks, and workflows
• thoughts on learning, productivity, and side projects
• an occasional completely random topic, depending on what I am obsessed with that week

The only rule I am trying to follow here is to write things that I would personally like to read later.

Talk to me

If you have ideas for the site, the blog, or topics you would like me to write about, I would be happy to hear them.

You can reach out through the “Contact me” page on this site. Whether it is feedback about the design, a bug you found, or just a quick hello, it is all welcome.

Thanks for reading this first post. I will try to make the next ones worth your time.