I got into this from the bottom up — curiosity about how a machine actually works. That turned into a shell in C, then a PAM module in Rust, then benchmarking what the kernel really does when you ask it to copy a file without touching userspace. It is the same curiosity that makes me run my own servers rather than rent someone else’s abstraction.
Science is the reason for all of it. Reproducing an antimatter analysis with CMS taught me that a result nobody else can re-run is not a result — and the scientific-computing work I do now exists to make sure the pipeline behind such a result still runs on someone else’s machine, a year from now.
I am not interested in code that merely works. I care about the architecture underneath: clear boundaries, least privilege, encrypted at rest, no cloud when the device can do the job itself, and an audit trail for anything destructive. What I can open, I open — production systems stay private when a client’s security depends on it.
- Who is Dax Navarrete?
- Dax Navarrete (GitHub: daxrpm) is a Computer Science undergraduate at Escuela Politécnica Nacional in Quito, Ecuador, and an open-source developer working across Linux infrastructure, networking, security and scientific computing. He operates a seven-server Linux estate, keeps a physical-security platform running in production, and collaborates on the CMS experiment at CERN through EPN’s group, which he leads on the computer-science side.
- What does Dax Navarrete work on at CERN?
- Dax Navarrete contributes to the CMS collaboration at CERN through Escuela Politécnica Nacional, where he leads the computer-science group. With the Data Preservation and Open Access (DPOA) group he reproduced an antimatter-search analysis, working on reproducibility and data integrity. He now works with the BRIL group on scientific computing: deploying and benchmarking Apache Airflow pipelines across a three-server Linux environment and reporting the results back to CERN.
- What infrastructure does Dax Navarrete run?
- Dax Navarrete operates seven Linux servers spread across his own hardware, his university and a rented VPS, joined into a single private mesh network with Headscale. Behind it he self-hosts his own cloud and media services — Nextcloud, Immich and others — and three of the servers run scientific-computing pipelines for the CMS group. He wrote Fleet, an agentless console in Go, to operate all of them over SSH from one place.
- What programming languages does Dax Navarrete use?
- Rust and C for systems programming, Go for infrastructure tooling, Python for scientific computing and machine learning, and TypeScript for interfaces. Notable work includes dax-auth (a PAM face-authentication module for Linux, written from scratch in Rust), Fleet (an agentless Linux fleet console in Go) and Apogee (an orbital ascent simulator in TypeScript and Python).
- Is Dax Navarrete available for work?
- Yes — open to internships, research collaborations and open-source work in infrastructure and DevOps, scientific computing, security and networking, or systems programming. Remote or relocation, internationally. Reach him at dax@daxrpm.dev.