I have always believed that the best way to understand something is to build it.
This blog is a small step in that direction.
I am a backend developer and industrial engineer, and most of my work revolves around building systems, solving problems, and trying to understand how things work at a deeper level. Over time, I realized that many of the things I learn tend to disappear if I do not write them down.
So this space is my attempt to change that.
Why this blog
I do not see this as a place for polished articles or perfect explanations.
Instead, I see it as:
- A personal learning journal
- A place to document projects and experiments
- A way to structure my own understanding of software and systems
Some posts will be deeply technical. Others will simply capture ideas or lessons from real-world problems. Most of them will probably start as “notes to self”.
What you can expect
I will mainly write about topics related to backend development, software architecture, cloud, automation, and anything related to building and understanding systems.
I am especially interested in the fundamentals that stay relevant regardless of technology changes: system design, scalability, maintainability, and problem decomposition.
Tools change. Principles remain.
A final note
I do not consider myself an expert writer or someone with all the answers.
This blog exists for the same reason I write code: to learn, to improve, and to understand things a little better than before.
If anything here turns out to be useful to someone else, that is a great bonus.
Otherwise, it will still have served its main purpose.
— Enrique