Why I Decided to Write a Blog
For years, I've found myself learning - and often re-learning - through the words of brilliant engineers across the internet. Technical blogs have always been a window into how others think, reason, and create. I've spent countless hours reading posts from Marc Brooker's blog (current blog draws CSS inspiration from his), the Meta Engineering Blog, the Google Cloud Blog, the Netflix Tech Blog on Medium, and even detailed Google postmortems analyzing outages and incidents. Each of these sources taught me something different - not just technical details, but also how to approach complexity, communicate clearly, and remain humble in front of the systems we build.
I built my own template engine for this blog because I wanted complete ownership of it, ensuring my Markdown files were entirely separate from the engine itself. With today's AI, developing this template engine took me only two prompts and twenty edits, so I don't have any particular attachment to it. It's simply my imagination transformed into reality by software.
Those writings are more than just documentation or announcements - they are thought processes made visible. They show the human side of computing: the trade-offs, the mistakes, the lessons learned. Reading them regularly doesn't only expand my technical knowledge; it inspires me with entirely new ways of thinking. Sometimes a single paragraph can trigger an idea, a new mental model, or a way of solving a problem I hadn't even noticed before.
During my short but meaningful time teaching at the University of Oviedo, I learned an invaluable lesson: the best way to learn something deeply is to explain it. When I prepared lectures, I discovered that teaching forced me to confront my own gaps in understanding. Writing, in a sense, is the same - it's a form of structured reflection. Translating thoughts into words requires clarity, precision, and honesty. It's an intellectual exercise that helps me think better, not just communicate better.
This blog isn't intended to be a reference, a tutorial hub, or a source of ultimate truth. It's fine if no one reads it at all. For me, writing is a way to record my own journey - the things I've built, learned, broken, and fixed along the way. I want it to serve as a personal log of progress, ideas, and curiosities that shaped me as an engineer.
If one day someone stumbles upon a post and finds a piece of insight that helps them - the same way others' writings have helped me - that would be a wonderful bonus. But even if not, I'll be content knowing that I've left traces of my own learning process behind.
In the end, I'm writing this blog for the same reason I read others: to learn, to reflect, and to keep the conversation - however quiet - alive.