Alberto Vargas

My conviction about automation formed early. At the start of my career, supporting hundreds of retail store locations, I noticed something about the mistakes in computerized work: they were rarely the computer's. They were mine, small human slips in repetitive point-and-click tasks. One of my earliest automations proved the point, taking store onboarding from one or two hours down to about fifteen minutes. That became a principle I have carried ever since: if a task can be done by pointing and clicking, a computer can do it faster, more consistently, and without the human error.

Two decades later, that principle is my profession. The platform matters less than the outcome: I learn new toolsets fast, partner with the SMEs who own a process, and hand back automation that removes the manual work entirely. That has meant disaster-recovery testing, data center migrations, server lifecycle, patching and compliance, and OS deployment, across Windows, Linux, VMware, and everything that orchestrates them.

There is a deeper outcome underneath the automation: independence. Organizations get boxed in when their ability to operate is welded to a single vendor's product and seat count, the dynamic playing out right now with Broadcom and VMware. I design automation that hands that independence back, extending and integrating the tools a team already owns so that scale comes from architecture rather than procurement. At UCSD Health I stood up Ansible Automation Platform on roughly 200 licenses, where an earlier proposal to license all 1,500 virtual machines had been rejected, and kept the same reach by extending AAP through Azure DevOps and on-prem agents on top of the SCCM and Satellite investments already in place. Doing more with less is not a slogan for me, it is a design constraint that keeps organizations free to modernize on their own terms.

I also carry deep expertise where it counts. More than a decade inside SCCM/MECM taught me the console, but also what happens behind it, the parts you only learn by running into them in production. That depth is what let me build the patch-compliance tooling a global Windows fleet's operations team leaned on, and it is what I reach for when the out-of-the-box path runs out.

That Windows depth goes all the way down. PowerShell has been my primary instrument for well over a decade, to the point of being hired as the PowerShell subject-matter expert for Vanguard's Windows ecosystem, and I have hit just about every sharp edge it has, from CredSSP and double-hop authentication to the delegation and permissioning gotchas that quietly break remote automation. When a native tool or REST API does not exist, I do not stop there: I reach for P/Invoke and a careful read of the Microsoft documentation on how a given Windows DLL actually behaves. I have wrapped robocopy inside custom ASP.NET web applications to run scheduled application-share migrations, and built private web front ends in both ASP.NET and Python when a job called for one.

How I build matters as much as what I build. Every automation ships with documentation and diagrams pitched to the audience that will actually read them, whether operators, engineers, or leadership, and never left as tribal knowledge. I build custom integrations where none exist yet, and I document them so whoever inherits the work can hit the ground running, with or without me. I would rather share what I know and solve problems alongside a team than hoard knowledge and work in a silo, which in my experience pays far better dividends. I plan and iterate in the open on work boards like Azure Boards, lean on proven patterns instead of reinventing them, and keep transparency at the center of every design. CI/CD is not an afterthought: my automations, and the platforms that run them, are versioned, peer-reviewed, and rebuilt from code rather than hand-tuned in a console.

By day I automate enterprise infrastructure; by night I run a small homelab, a Docker Swarm cluster with HashiCorp Vault for secrets and a Home Assistant setup I write my own microservices against, where I try new tools and patterns before they ever matter in production. That instinct does not clock out: the same automation quietly smooths the logistics of a busy household, so the time it saves goes to the people who matter most.

Twenty years in, I have not met an automation problem I could not get to, on Windows or Linux, on Azure, AWS, or Google Cloud. If I have not done a thing yet, the drive to learn it is exactly what has kept this work engaging for two decades, and that has not dimmed.