Edu González — Data & Cloud engineer. I document technical decisions.

I write about decisions that official tutorials skip: why this architecture was chosen over that one, what trade-offs were made, what failed in production that nobody documented.

Sometimes the post will answer your question directly. Other times it will give you the uncomfortable answer that forces you to figure it out — because there are no universally correct answers in engineering, only decisions that fit a use case better or worse.

I also publish for fun. I spend weekends exploring things that interest me without a clear goal, like when I started. Those are the posts I enjoy writing most.

When I need to solve something, the first question I ask is: has someone already spent years building a validated solution for this? The answer is almost always yes.

Learning to read real production code — understanding why each design decision exists, not just how it works — is what has taught me the most. It requires humility, especially for things that seem trivial.

We're at an inflection point. AI is automating repetitive technical work at record speed — it's estimated that 46% of GitHub Copilot users' code is generated directly by AI.

The problem is that AI accelerates everything: the good and the bad. A poorly designed architecture will explode much sooner today than five years ago, because adding features is nearly free. Whatever you don't decide, the AI will decide — and AI fills gaps with what's statistically plausible, not what's strategically appropriate.

The value today is in being the person trusted to make technical and strategic decisions — someone who understands the business, understands the technology, and uses AI as their own resource, not as an external consultant delegated the judgment.

I'll publish regularly, without calendar promises. I work in consulting, I have a life outside the screen, and I prioritize mental health over forced consistency. What I can guarantee is that when I publish, there will be something concrete to take away.

Subscribe via RSS — no newsletter, no notifications. If you're working on something interesting or want to discuss topics from the blog, write to edunavata@gmail.com . I read everything, though I don't always respond quickly.