The First Post

Welcome to my blog, this first post is about the motivation behind the blog, the journey I have gone through creating it and the future plans for my blog and hobby projects.

The motivation is simple: the reality of the world has created a need for experts in any field, especially in the tech industry to step up and share their knowledge, expertise; essentially becoming content creators/influencers.

I am really bad, terrible at self expression, I am bad at expressing my thoughts, ideas and work. This blog is an attempt to improve on that, increase visibility and reach of my work and experience. I will write about my work, thoughts and ideas in an interesting and comprehensible way to me and hopefully to others.

Iterations, iterations, iterations...

This blog is my second attempt at blogging, the first attempt was a failure for two reasons:

1. I overcomplicated the setup
2. I was focused on the technical aspects, design and cool factor rather than the content itself.

I overcomplicated the setup

The setup was overly complicated for what I wanted to do: write posts with a freedom for customization of every one of them, fully, depending on the content and ideas I have in mind. The first version was based on the architecture of the blog with headless CMS for managing content heavily inspired by Josh W. Comeau's blog↗, which is a great blog and a great example of how to build a blog with a headless CMS, but it was not the right choice for me right now, in case the blog grows I will need to re-evaluate my approach and build something more scalable and complex.

While it was functional, and pleasing to build an app that works and achieves its goals, it felt similar to building a personal metro system that gets you to a place you only visit once or twice a month, it was not worth the effort and time I had to put into it. At first, it led to procrastination and later, frustration from unaccomplished goals. That is why this, current solution is built with a different mindset and focused on the content and the writing itself, rather than the technical aspects of the blog.

Every post on this blog is a simple Nextjs page with a bunch of react components, wrappers for precise control in an IDE rather than publishing it with Vercel's CD, instead of relying on publishing it on headless CMS with poor developer experience and a need for a lot of work configuring everything, which leads me to the next point.

I was focused on the technical aspects, design and cool factor rather than the content itself.

I was focused on making sure the blog worked with all the layers of complexity I envisioned, refusing to sacrifice any of the technical aspects, design and cool factor for the sake of content and writing itself. This led to a lack of writing, procrastination and a blog with no posts at all.

The solution was simple build a blog as simple as possible, sacrificing only one aspect: the technical complexity of publishing a post. More about it further down below.

The current solution

The current solution is built with NextJS with each of the posts being a simple React component that can be easily edited and customized. Deployment of the new version of the website publishes new posts at the same time. Retaining full control over the content and layout. Creative freedom like this:

I believe building something like this would not have worked as naturally in my previous setup. The point is not novelty for its own sake, but freedom to shape each post around the idea itself. If this space helps me keep writing consistently, then it is already doing exactly what I built it for.

Building my own tools is part of the point

Another benefit of this approach is that I can build small tools directly inside the same project where I write. Instead of waiting for a plugin or changing a CMS schema, I can design exactly what I need and ship it right away.

That turns the blog into a practical learning lab. Every tool I build here improves my understanding of UI architecture, performance tradeoffs, and product decisions, because I feel the consequences in real usage immediately.

Over time, this creates a feedback loop: better tools make writing easier, and writing more helps me discover the next tool to build. It is slower than copying templates in the short term, but much more valuable for long-term skill growth.

This is only the beginning, and I am excited to see where this journey takes me. I have a lot of ideas for future posts and projects, and I am looking forward to sharing them with you!