About Eodos

Eodos is my personal engineering notebook.

I started this blog in Spain in February 2009, when I was a teenager learning how to program. In its early years, I wrote in Spanish about GNU/Linux, open-source software, programming exercises, technical drawing, and the projects I was building while studying Industrial Engineering in Málaga.

Later, the blog became a place to document my undergraduate thesis: a connected irrigation system built with technologies including Raspberry Pi, Android, sensors, and embedded hardware. Those articles—and the earlier posts that preceded them—remain available in the Spanish archive.

Today, I live in the United States and work as a software engineer. I have revived Eodos as an English-language publication focused on the systems and engineering problems I am exploring now.

What I write about

My current interests include:

  • Agentic workflows and personal agent runtimes
  • AI-assisted software development
  • Developer tools and infrastructure
  • Software reliability and observability
  • Automation with clear boundaries and human oversight
  • Lessons from building and operating real systems

I am particularly interested in what happens when language models become part of a larger engineering system: tools, state, permissions, logs, scheduled work, verification, and failure recovery.

The model may be the most visible component, but it is rarely the entire product.

The archive

Most of the older articles are written in Spanish and reflect what I was learning at the time. Some are beginner programming exercises; others document university projects, software experiments, and technologies that may now be obsolete.

I have chosen to preserve them rather than rewrite or remove them. Together, they provide a record of how my interests and engineering experience have evolved since I first began learning to code.

You can explore them in the Spanish Archive.

How I write

I use modern tools—including AI—to help with research, outlining, editing, and exploring alternative explanations. The technical opinions, conclusions, and final published content remain my responsibility.

My goal is not to publish as much as possible. It is to document useful ideas, explain what I have learned, and make the reasoning behind the work visible.

Contact

You can reach me at eodos0 [at] gmail [dot] com.

Unless otherwise stated, the opinions expressed here are my own.