who am i
i'm yuri cunha, a brazilian guy who takes computers, servers, systems and homelabs a bit too seriously. this site is where i keep projects, notes, experiments and the occasional thing i learned by breaking something first.
in one paragraph
i'm an Infrastructure & Platform Engineer who likes building and operating complete systems: from hardware, Linux and networking to storage, containers, services, databases, automation and the applications running on top. databases are an important part of my work, and a strong software-development background lets me follow a problem across the boundary between an application and the platform beneath it.
systems and infrastructure
i am happiest close to the moving parts. i like knowing where a process runs, how it starts, where its data lives, how machines communicate and how to recover when a service misbehaves.
my work and experiments regularly involve Linux servers, Docker and Compose, persistent storage, private networking, cloud and on-premises workloads, self-hosted services, scripts, CI, logging, monitoring and troubleshooting. the useful shape of it is simple: hardware → Linux → network → storage → containers → services → databases → automation → applications.
homelab and hardware
the homelab is not just a place to learn one database. it is a real, evolving environment where i build, operate, break, recover and document systems across physical machines and cloud nodes, x86 and ARM64, private networks and public entry points.
server and homelab hardware is one of the parts i enjoy most: evaluating CPUs, memory, ECC, storage, power use and capacity; understanding what each machine is good at; and giving workloads a sensible place to live. i care as much about the machine and its limits as the service running on it.
development and databases
development remains a practical part of how i work. i use Python, shell, Go, Node.js, TypeScript, SQL and web tooling for scripts, automation, APIs, internal services and integrations. that background is useful when a failure crosses layers and the answer is not simply “restart the container.”
PostgreSQL, pgvector, Redis, backup and restore, data migration, performance investigation and persistent services are all important parts of my experience. databases are one of the layers i work with deeply, not the whole label.
how i work
i prefer systems that are understandable, observable and recoverable. that usually means documentation close to the work, useful logs and metrics, tested backups, small automations for repetitive tasks and environments that can be reproduced without folklore.
i like tools that are simple enough to fix at three in the morning. understanding the mechanism under the tool matters more to me than memorizing a long list of commands.
direction
my formal education includes Database Technology at Estácio, and it continues to inform the way i think about stateful systems and data. professionally, the direction is clear: infrastructure and platforms, with systems engineering, Linux, networking, containers, automation, cloud, self-hosting and databases all connected rather than separated into job-title boxes.
outside tech
i also care about moving more, running farther and building habits that hold up over time. the same patience that helps with a stubborn service is useful outside a terminal too.