Reliability and platform engineering

Clear systems. Confident teams.

I am a Site Reliability Engineer and software developer. I build automation, observability, and cloud platforms around one simple idea: reduce uncertainty so teams can focus on delivering value.

Explore my workReticulum contact
  • SRE and software engineering
  • Zaragoza · remote
  • Open to roles and collaboration

01 / Areas of work

Reliability grounded in practice.

My work brings together product awareness, operational judgement, and care for detail: understand the context, remove friction, and leave a more maintainable foundation.

01

Observable systems

Instrumentation and useful signals that help teams detect, understand, and prioritise issues quickly.

Turn technical data into actionable context for operations and development.

ObservabilitySREPython

02

Platforms that scale

Delivery and runtime environments that can evolve without manual steps or isolated knowledge.

Apply infrastructure as code, delivery standards, and automation that make change easier.

KubernetesTerraformCI/CD

03

Cloud with judgement

Experience across infrastructure, integration, and cost optimisation in varied cloud environments.

Balance availability, security, cost, and maintainability in every technical decision.

CloudFinOpsIntegration

02 / Lab

Systems explained through use.

Each lab shows a bounded part of a system I use: resilient communication, observability, and home automation. It explains what information is exposed, what you can explore, and what is deliberately protected.

Active

Checking status

Home monitoring and automation

Indoor temperature, humidity, and air quality as an aggregate home reading. Check the current state of my home while preserving privacy.

Protected data

Presence, cameras, locks, devices, and rooms are not published.
Home AssistantPrivacy

Live

Service observability

Aggregated CPU and memory use from my personal server services, queried through Prometheus. Compare both resources, select services, and inspect a specific time range.

Services

Live

Checking radio

Meshtastic

Aggregate status for a Meshtastic gateway and its public MediumFast channel. Inspect activity, radio use, and the latest visible message without exposing the private network.

Last 5 public activities

There is no visible public activity yet.

Send to MediumFast

Public sending will be available after anti-abuse verification is configured.

Protected data

Only the five most recent public messages are shown; node IDs, locations, SNR, RSSI, keys, and other channels are not published.
MeshtasticMediumFast

Active

Checking Reticulum

Reticulum

A self-hosted Reticulum contact point for receiving messages from compatible clients. The guided journey shows how a test is prepared, encrypted, and confirmed before it is sent.

ReticulumFastAPI

Reticulum address

Address available once the node is published

Received messages

  • No messages have been recorded yet.

The five most recent messages are shown as plain text. The relay's public TCP connections identify configured servers, not the route for a specific message.

Reticulum TCP connections

  • Node status is unavailable.

Names identify configured TCP connections. The LXMF address does not belong to one specific node: any client with Reticulum connectivity can discover it. This state does not guarantee a route or delivery.

Reticulum journey

The temporary identity is created only when this test is sent. The browser never receives private keys or connects directly to Reticulum.

  1. Temporary sourceWaiting
  2. Reticulum destinationWaiting
  3. EncryptionWaiting
  4. ConfirmationWaiting

Temporary source

Created when the test is sent

David's destination

Address available once the node is published

Node selected for this test

Waiting for route selection

Telegram notice

Telegram not configuredWhen Reticulum receives the message, it can send a private Telegram notification.

03 / GitHub

Code to explore.

Public repositories that accompany the selected work.

Updated Oct 2026

lab-inverse-proxy

Shell / 0 stars / 0 forks

Private laboratory HTTP edge: Nginx and Cloudflare Tunnel configuration for Signal Relay.

github-config

Updated Oct 2026

ender3-v3-se-klipper-with-display

C / 0 stars / 0 forks

Modified klipper for ender3-v3 se with stock display support. https://jpcurti.github.io/ender3-v3-se-klipper-with-display/#/

forkgithub-config

Updated Oct 2026

homeassistant

Shell / 0 stars / 0 forks

-

github-config

Updated Oct 2026

challenge-sre

HCL / 1 stars / 0 forks

SRE challenge

github-config

Updated Oct 2026

Blink

C / 0 stars / 0 forks

-

forkgithub-config

Updated Oct 2026

dotclaude

Python / 0 stars / 0 forks

Personal Claude Code configuration repo

github-config

Updated Jul 2021

destaben

Repository / 1 stars / 0 forks

Config files for my GitHub profile.

configgithub-config

04 / Notes

Notes from systems work.

Short notes on systems, operations, and architecture decisions.

05 / Experience

Experience across software, cloud, and operations.

  1. Apr 2021 - present

    Site Reliability Engineer

    adidas

    Service reliability, automation, and orchestration.

  2. May 2020 - Apr 2021

    Cloud Engineer

    NTT

    Cloud infrastructure, cost optimisation, and integration.

  3. Jan 2019 - Apr 2020

    Senior DevOps Engineer

    dareCode

    Automation, containers, and delivery platforms.

  4. Apr 2018 - Jan 2019

    Software Developer

    NSC Network Solutions Control

    Web development, Docker administration, and systems maintenance.

  5. Jul 2017 - Feb 2018

    Systems Integrator

    Orbe

    Security, network, telephony, and Linux and Windows systems integration.

  6. Mar 2012 - Jun 2017

    Project Designer

    A&T Ingeniería

    Telecommunications, systems, software development, and KNX integration projects.

06 / Contact

A good conversation can start with a difficult problem.

I am interested in SRE, platform engineering, and software roles where reliability is a shared responsibility. I also welcome thoughtful conversations about observability, infrastructure as code, and distributed systems.

Professional network
GitHubLinkedIn

I reply personally. For an initial note, a little context about the challenge and the team is enough.

Email David