About me↗
Hi, I’m Eduardo. This is a little about me.
I studied applied mathematics and now work as a Site Reliability Engineer. Most of my day-to-day work involves Kubernetes, cloud platforms, automation, and the systems that keep production environments running.
I like learning mostly because I find it entertaining. I’m naturally drawn to subjects where there is always another layer to understand, especially mathematics, Linux, security, and cryptography. Mathematics gives me a space for abstraction; Linux makes it possible to look beneath the surface of a computer; and security forces you to understand systems deeply enough to see where their assumptions break.
Cryptography is probably where many of those interests meet. It combines mathematics with practical systems, and I find that transition from abstract ideas to real-world mechanisms especially interesting. That is also part of why I identify with many privacy ideas, open systems.
I have a strong preference for simple systems. I dislike unnecessary complexity, poor documentation, and abstractions that make things harder to understand than they need to be. For me, simplicity usually means removing what is not necessary rather than adding another layer to manage the previous ones. I also have a strong preference for open source, because of its philosophy.
I don’t consider any of these interests particularly profound. They are simply things I enjoy thinking about. There is far more I don’t know than I do. Most of the time, I’m just following questions, trying things, changing my mind, and learning as I go.
This site contains some of my work: articles, notes, experiments, projects, and ideas worth remembering.
Complexity is inevitable, simplicity is intentional.
How I Think About Systems↗
My approach to software has been shaped by three traditions: Unix, Python, and OpenBSD. Unix values small tools that do one thing well and compose with others. Python favors clarity, readability, and explicit behavior. OpenBSD treats correctness, secure defaults, and continuous review as foundations rather than additional features. Together, they shape how I build systems: keep components narrow, make behavior understandable, and treat complexity as a cost.
Systems are easier to trust when their behavior is easier to understand.
About the blog↗
This site is where I preserve my ideas, document my experiments, and record what I learn.
The site is organized around three kinds of work:
- Articles for ideas that deserve a more complete treatment.
- Notes for smaller technical findings, references, and things worth remembering.
- Projects for the systems and tools that grow out of both.
The goal is not to publish constantly, but to keep a useful record of knowledge that can survive beyond a terminal session, a forgotten bookmark, or a note buried somewhere on disk.
- Some entries are complete. Others are fragments.
- The distinction does not matter much.
- Useful things instead of useless ones.
Thanks for spending some of your time here. I’m grateful for the chance to share a few ideas, questions, and things I’ve learned with you.
Disclaimer↗
Everything published here reflects my understanding at the time of writing. It is not meant to be definitive, and my views may change as I continue learning.
The content is shared for educational purposes and provided as is, without warranty. Examples, experiments, and technical notes may be incomplete, outdated, or unsuitable for production.
Read critically, question the assumptions, and use your own judgment. Test and adapt anything technical before relying on it in systems that matter.
Credits↗
This website is based on Lipi Astro theme.