Rosario, Santa Fe, Argentina
Backend Python Developer
What I build is running right now, on a server I administer myself.
My sites, right now
Status checked live when this page loaded.
I've worked in Python for over four years, mostly on the backend: data models, PostgreSQL, integrations and accounting systems that can't afford to fail.
Outside work I build my own products and take them all the way — which for me means all the way to the server. I bought a VPS, hardened it, and that's where my applications run, with backups I've tested by restoring them.
When something breaks I'd rather understand the cause than patch the symptom. It usually takes longer, and it's usually the only way it doesn't come back.
Spanish — Native
English — Professional · daily code, documentation and teamwork
Deployed on my server and running right now.
Self-hosted, open source personal finance manager.
The problem it solves
Small recurring expenses — coffee, delivery, the subscription nobody cancels — never show up as a problem on a bank statement. They're diluted across hundreds of uncategorized lines. At the end of the month the money is gone and there's no way to point at where.
Web catalogue for an artist, on its own domain.
The problem it solves
An artist showing work on social media depends on the algorithm and has no way to present an organised catalogue: by style, by medium, by size. Someone asking about a specific piece ends up scrolling through old posts.
Remote music co-production over Ableton Live.
Candles and home fragrance e-commerce.
I don't depend on a platform for my code to exist. I rent a server, hardened it, documented it, and that's where my applications run.
Two separate applications, on separate domains, sharing a single server. The only process listening on the internet is the reverse proxy; everything else talks over internal Docker networks that go nowhere else.
Edge — exposed to the internet
Caddy
The server's only open ports are 80, 443 and SSH. It issues and renews TLS certificates for both domains with no intervention.
Applications — shared network
caudal-web
gunicorn + Django. No published ports: Caddy reaches it by service name.
cuadrosjaci-web
Django REST Framework API. The frontend is static files served by the proxy.
Data — isolated networks, one per app
caudal-db
PostgreSQL. Verified it doesn't answer from the proxy's network: only its own application can reach it.
cuadrosjaci-db
PostgreSQL, on its own network. A compromised app can't reach the other one's database.
The only way into the server over the network is a cryptographic key. There's no password to guess.
Automatic daily backup, and the restore is actually tested instead of assumed.
Container and volume names are mandatory, because the server's maintenance discovers what to do from them.
Python Developer · Odoo
I translate complex accounting and tax requirements — including Argentine fiscal localisation — into technical solutions that scale.
Full Stack Developer (freelance)
Delivered web applications end to end with an international team, working in English with autonomous execution.
Python Developer
I bridged business and engineering: turning requirements into working software and explaining outcomes to non-technical stakeholders.
Full Stack Web Developer (freelance)
I owned the full cycle with the client: discovery, development, deployment and support.
Education
University Technical Degree in Programming
OOP, data structures, databases, networking and systems architecture.
No percentage bars: every technology says where I used it.
Things I found while solving real problems.
The dump runs every day and never fails. That says nothing about whether it works. How I built a check that does say it, and why it deliberately ignores some tables.
The library that blocks brute-force login attempts was installed, configured and running. It was also recording the wrong IP, which made it useless and, on top of that, dangerous.
You can have ufw enabled, set to deny-all, and a database exposed to the internet at the same time. The firewall will tell you everything is closed, and from its point of view that's true.
If you'd like to talk about a project, a role, or anything technical, get in touch.