Argentina · SysAdmin & Backend Developer
I build backend services and keep production infrastructure understandable, observable and recoverable. My day-to-day connects application code to Linux, Kubernetes, networking, CI/CD and the systems behind real production work.
Current role
Production SysAdmin
Backend
Node · TS · Python
Cloud
AWS · Azure · vCD
Focus
Production reliability
Selected operational case studies — what was happening, what I did, and what each one demonstrates.
Production details are anonymized to protect internal systems and customer environments. Public-safe wording, no internal identifiers.
A production deployment pipeline used a reusable GitHub Actions workflow to standardise releases. Releases had been working, then began failing before any job ran.
impact
Deployment workflow restored. Failure mode documented so the next contract drift is diagnosed in minutes instead of trial-and-error against the pipeline.
Three production Elasticsearch nodes in Azure needed to be sized for an upcoming high-traffic event. The cluster fed search and analytics paths the event would amplify.
impact
Cluster prepared and validated for the event window with a documented rollback path. Sizing decisions captured for future event-readiness work.
A production Kubernetes cluster running in Azure (AKS). A Zabbix alert reported pods of an application component down. CrashLoopBackOff was active.
impact
Component restored to a healthy ready state. Diagnostic path documented for future incidents of the same shape.
Synthetic stream — but the shape is honest: this is what production looks like once you've earned the right to read it calmly.
My work connects backend development with infrastructure operations: service design, automation, observability, networking, and incident response.
module_01
Authentication, role-based access, business logic, and the observability hooks needed to understand what the service is actually doing under production pressure.
module_02
Linux, Kubernetes clusters, Helm charts, CI/CD pipelines and cloud environments — kept in a shape where deployments and incidents both have a clear procedure.
module_03
Network, system, runtime, application. Logs, metrics, packet path, NAT, VPN, workers, cronjobs — read together instead of one at a time.
Most production problems live between layers. Here's the picture I carry around — the surface where backend, systems, networking, and observability stop being separate jobs.
L1 · Networking
step 01/04L2 · Systems
step 02/04L3 · Backend
step 03/04L4 · Observability
step 04/04An interactive snapshot of the technical world I operate inside. Click any module — or use ↑↓ / j k — to inspect the typical operational use.
module
typical use
Web application development, REST and GraphQL APIs, background workers, third-party integrations and service-to-service communication.
Backend Runtime · 1/5
The shell I live in, grouped by domain. Real commands from real production work — Kubernetes, Linux, networking, CI/CD, Docker, Terraform, debugging.
kubectl get pods -A -o wideKuberneteskubectl describe pod <pod> -n <ns>Kuberneteskubectl logs -f <pod> --tail=200Kuberneteskubectl get events -n <namespace> --sort-by=.lastTimestampKuberneteskubectl rollout status deployment/<name> -n <namespace>Kuberneteskubectl get configmap app-config -o yamlKuberneteshelm template ./chart -f values.yamlKuberneteshelm upgrade --install <release> ./chart -n <ns>KubernetesPersonal and freelance work — backend services, infrastructure ownership, automation. Each entry includes problem, stack and operational impact.
case_study/001
Personal server dashboard built to monitor and manage my homelab environment from a clean web interface.
impact
The dashboard centralizes operational visibility and common management actions, making the server environment easier to monitor, search, reorder, and control from the browser.
case_study/002
Discord bot for authorized network diagnostics, service discovery, and security analysis using NMAP and external threat intelligence APIs.
impact
ShadowScan packages scan modes, threat intelligence, rate limiting, validation, audit logging, and administrative controls into a modular diagnostics bot.
case_study/003
REST API for an e-commerce platform with authentication, role-based access control, product catalog, orders, and media upload.
impact
The API provides a modular NestJS backend with authentication, role-based access, database utilities, stock validation, Swagger documentation, and Cloudinary uploads.