Why this blog — Diazin

I could have waited.

Waited for the portfolio to be ready, the projects to look nice, GitHub to be tidy, the domain to be perfect, and all those things we put in front of something when, deep down, we just need to start.

So I started.

This blog exists because I noticed how quickly things move in our day-to-day.

A problem shows up, we investigate, we make a call, we fix it, we move on to the next one, and a few months later we barely remember why we chose that path.

I want to change that.

I want to record not only what I did, but mostly why I did it.

Because a technical decision rarely happens in a perfect setting.

There is a deadline. There is production. There is legacy code. There is a business rule. There is a client. There are people. And there is that service nobody wants to touch because “it has been working since 2019”.

That is the context that makes the decisions interesting.

What I intend to write

I do not want this to be a showcase of technologies.

I want to talk about projects, architecture, leadership, study, mistakes, decisions, and real problems that show up when software stops being an exercise and starts serving actual people.

Some posts will probably be quite technical.

Others might just be reflections from someone trying to understand software engineering better while living through it.

And that is fine.

This blog is also a way to talk to the Kaique of a few years from now.

I want to be able to come back here and think:

“Man… did I really believe that?”

Or, with a bit of luck:

“I was not that far off.”

What this is not

It is not an attempt to look more senior.

It is not a list of stacks.

It is not a content factory for an algorithm.

And I am definitely not going to invent an article because I learned how to install some tool yesterday.

If there is no context, no lesson, no decision, or no story worth telling, it probably does not need to become a post.

The cadence will follow that idea.

I would rather write when I have something to say.

In the end, this is just the start of a public record of a career that still has a lot left to happen.