I have spent years reading other developers’ blogs. The kind of blogs where articles go straight to the point, no wasted words. Blogs written by people who already went through the same problem and save you time.

So I decided to create mine.

It is not about money or fame

I do not expect to make money here. I do not expect to go viral. If people read it, great. If not, still fine. What I do want is:

To write properly. Not tweets, not corporate-style LinkedIn posts. Long-form articles where I can explain why I choose a tool, what trade-offs it has, and in which context it makes sense.

To clarify my own thinking. When you explain something in detail, you discover the gaps in your own understanding. Writing forces precision.

To keep a record of how I think about development today. Not because it is final truth, but as a reference point of where I was in May 2026.

What you will find here

  • Architecture decisions: why I chose Astro, why I do not use React everywhere, how I structure projects.
  • Setup and tools: what I use in my dev environment, why, and how to set it up if you want to try it.
  • Patterns: design systems, reusable components, and style organization.
  • Grounded opinions: not universal truths, just lessons from my own work. Use them as references, not doctrine.

Why Astro and not Next.js, Remix, or something else

That is one of the first decisions I wanted to explain. Short answer: the project is simple, so the tool should be simple too. I do not need an SPA-oriented framework for a blog.

If this were a dashboard or editor, it would be different. Here, Astro does the job perfectly. That leaves me with more time to write and less time fighting configuration.

One final note

If you read this and disagree with parts of it, good. We do not all think the same way. But if something here helps you, an idea, a tool, a way of thinking, then this blog is already worth it.

See you around.