Foundations
Developer tools begin at the workbench
I started with command-line tools, automation, and a Linux desktop I kept rebuilding by hand. That practice shaped a lasting focus: developer experience is part of the product, not an afterthought.
Digital Nest builder profile
Ulises Jeremias
Solutions Architect @ NaNLABSopen-source builder
I build developer systems that reduce friction and keep the developer in control: portable agent tooling, reproducible Linux desktops, V scientific computing, and scaffolding that starts projects in a working state.
La Plata, Buenos Aires, Argentina
Different domains, connected by one principle: make every layer easier to work with.
From the workstation outward
The systems I build
The projects move across environments, languages, applications, and workflows. The common thread is to make these layers work together and leave the person in control.
Since 2019
Give a language a working ecosystem
I started VSL, the V Scientific Library, in 2019 and still lead it. I maintain VTL for tensors and autograd, built setup-v for CI and RxV for reactive streams, and contribute to the V compiler.
Since 2020
Compose applications from parts
Create Awesome Node App began in 2020 as a way to combine a template with extensions instead of copying starters. Python, V, and Rust siblings now share that model; Recoil DevTools remains maintained for apps that still use Recoil.
HorneroConfig → Hornero OS
Make the working environment reproducible
HorneroConfig grew from its X11 roots into a Hyprland and Quickshell desktop managed with chezmoi. Generic parts of that configuration informed Hornero OS, an early-stage Arch-based desktop OS that is not installable yet.
Now
Carry the systems model into agentic work
Agent Toolkit makes skills, agents, and loops portable across coding assistants. Agentic Workstation provisions the machine; Agentic Harness keeps workspace context between sessions.
How I contribute
Roles and provenance
Employment, open-source maintenance, and community work are shown as separate responsibilities.
Work
- Solutions ArchitectNaNLABS (opens in new tab)
Client work stays private and is not shown on this site.
Open source
- V Ecosystem Maintainervlang — VSL, VTL, setup-v (opens in new tab)
- AUR MaintainerArch User Repository (opens in new tab)
- Open-Source MaintainerDigital Nest projects (opens in new tab)
Roles are linked to their public organizations and repositories.
Community
- Community HostDigital Nest Discord (opens in new tab)
Community work is open to anyone and separate from my employer.
Project ownership is explicit throughout the site: work I own, work I maintain within organizations such as vlang, and upstream contributions are labelled differently. Open Source links to the evidence.
What is active across the portfolio
Current focus
The design rules behind the work
What I care about
Less friction
A tool earns its place when it removes a step people repeat, not when it adds a feature.
Developer control
Automation should serve the person using it. Provenance, configuration, and exits stay visible.
Composable pieces
Small parts with clear boundaries outlive the next assistant, framework, or machine.
Reproducible by default
Environments are declared, versioned, and rebuilt — never assembled by hand twice.
Work in public
Decisions, ADRs, and history live in the repositories, where anyone can check them.
Open-source support
Help the work continue
The projects are free and open source. Support can fund integrations, infrastructure credits, or Linux hardware for testing. Sponsorship is disclosed and never buys a technical recommendation.