behez0n@infra:~$ cat /etc/profile.d/behez0n.conf

NAME        = "Tomás Peña"
ROLE        = "Systems Administrator"
FOCUS       = "Infrastructure / Automation / Operations"
ENVIRONMENT = "Production"
LOCATION    = "Argentina"

STATUS      = "Operational"

Observe → Understand → Automate → Document → Improve

I work with production infrastructure, focusing on reliability, troubleshooting, automation and operational improvement.

My day-to-day work revolves around systems that need to stay available, observable and recoverable.

Infrastructure
├── Linux & Windows Server
├── Virtualization
│   ├── Proxmox VE
│   └── VMware
├── Networking
│   ├── TCP/IP
│   ├── Routing
│   ├── DNS
│   └── HTTP/S
├── Storage & Backup
├── Docker
├── cPanel / WHM
├── Monitoring
├── Incident Response
└── Automation

Most of my current infrastructure projects live in private repositories while they are developed, validated and used internally.

Some of the areas I'm currently working on:

behez0n@infra:~/projects$ ls -lah

drwx------  infrastructure-automation/
drwx------  incident-management/
drwx------  monitoring-lab/
drwx------  sysadmin-toolkit/
drwx------  infrastructure-docs/

# Private repositories.
# Public and sanitized versions will gradually appear here.

Some projects are kept private because they contain production-specific architecture, integrations or operational information.

When possible, reusable components, sanitized labs and generic implementations will be published independently.

Infrastructure is the main focus, but not everything needs to run in a datacenter.

I also build:

Discord bots
Gaming tools
API integrations
Small automation projects
Things that probably didn't need automating