Jesús Erro
Menu

Chronological journey

From 8-bit curiosity to company-scale systems.

A programmer’s evolution across changing technologies, from early experimentation to decades of responsibility in real business environments.

The continuing thread

Curiosity became practice; practice became depth.

The tools changed, but the underlying work remained connected: understand a system, model its information, make it useful, and keep learning enough to evolve it. That continuity supports meaningful contribution inside substantial, long-lived company environments.

  1. 1986 · The origin

    A warm 1980s home-computing desk with an 8-bit computer, CRT, programming notes, magazines, an isometric sketch, and basketball statistics.

    ZX Spectrum, BASIC, and learning by typing.

    Programming began as discovery: entering BASIC by hand, changing it, breaking it, and learning why it worked. There was no search engine waiting with an answer—progress came from attention, persistence, and other people’s clues.

    • MicroHobby, MicroManía, books, and classmates’ older brothers opened doors into a technical world that otherwise had few signposts.
    • The isometric world of La Abadía del Crimen and Tai-Pan showed how much atmosphere and structure could emerge from severe constraints.
    • An early basketball statistics sheet became a personal tool: a small but formative example of using code to organize something meaningful.
    • ZX Spectrum
    • BASIC
    • Self-taught
    • Typed-in code
    • MicroHobby
    • Micromanía
    • Isometric games
    • Basketball statistics

  2. 1990s–early 2000s · Expansion

    A 1990s personal computer transitioning into connected web application and database diagrams.

    From personal exploration to connected applications.

    The years between home-computing experiments and full-time professional development broadened the focus: from learning individual tools to understanding applications, interfaces, data, and the web as connected parts of a system.

    • This period is intentionally kept high-level: the durable thread is growing technical literacy and a gradual move toward production software.
    • Curiosity widened from what a single program could do to how software could organize information and support real processes.
    • PC era
    • Web development
    • Databases
    • Applications
    • Continuous learning

  3. 2006–2024 · 18.5 years

    A layered business-software system evolving from older operational modules into modern connected applications.

    Business-critical software at Centraldereservas.com.

    A long professional period building and evolving the systems behind real travel operations. The work crossed several generations of the web stack while preserving continuity in reservations and internal business processes.

    • The domain included reservations, case management, invoicing, payments, expenses, tasks, mailing, debt management, and internal operations.
    • Responsibility meant understanding how software decisions affected daily work, financial flows, and long-lived operational knowledge.
    • The stack evolved from PHP, MySQL, Zend Framework, ExtJS, jQuery, HTML, CSS, and SASS toward React, TypeScript, and Vite.
    • PHP
    • MySQL
    • Zend Framework
    • ExtJS
    • jQuery
    • HTML & CSS
    • SASS
    • React
    • TypeScript
    • Vite
    • Business systems

  4. 2025–2026 · Present direction

    An architectural data flow connecting ingestion, storage, orchestration, observability, and analytical outputs.

    Data platforms, observability, and agent-assisted systems.

    The current stage connects long experience in operational software with PostgreSQL data platforms, ETL, automation, architecture, and workflows designed for both people and software agents.

    • At IXATU, this work includes a PostgreSQL data platform for the energy sector and browser-based billing automation with Playwright.
    • The emphasis is not only on building features, but on making systems observable, documented, and controllable in operation.

    1. Apr 2026

      Runtime and operational control

      Profiling, runtime inspection, and repeatable operational workflows brought execution behaviour into view.

    2. Nov 2025

      Data lake and observability

      Object storage and telemetry connected MinIO, OpenTelemetry, Grafana, Loki, and Prometheus.

    3. Oct 2025

      Containerized architecture

      Docker-based services made system boundaries, dependencies, and local operation more explicit.

    4. Sep 2025

      Project architecture and build

      Modular project structures and build workflows established a maintainable base for continued development.

    5. Jul 2025

      Transformation and modeling

      Data modeling, dbt-inspired transformation, and medallion ideas clarified how raw information becomes useful data.

    6. Jun 2025

      Monitoring and data quality

      Quality checks and measurable pipelines shifted attention from successful execution to trustworthy outcomes.

    • PostgreSQL
    • FastAPI
    • Dagster
    • ETL
    • MinIO
    • OpenTelemetry
    • Grafana
    • Loki
    • Prometheus
    • AI workflows