I build and operate infrastructure, automate the work around it, and turn one-off fixes into repeatable processes. For nine years, I've designed and run a production platform of 100+ containerized services behind a hardened edge. I'm on call for every outage and responsible for Docker, reverse proxies, TLS, monitoring I wrote, backups, and recovery when something goes wrong. By day, I'm a Systems & Infrastructure Specialist automating multi-site environments in Python, Bash, and PowerShell. B.S. Computer Science.
I studied Computer Science at Medgar Evers College because I wanted to understand how things work all the way down. I've spent my career since then keeping them working for the people who depend on them. These days I'm a Systems & Infrastructure Specialist running Tier 1–3 support and systems administration across school systems throughout New York City. There, "it's not working" can mean anything from a dead laptop to a network problem that stops a whole classroom cold.
I've grown through that work as a break-fix technician, an account manager over five school systems across 20+ sites, and now a specialist. The constant has been range. One hour I'm working in Active Directory or the Google Admin and Meraki dashboards. The next, I'm writing a Python, Bash, or PowerShell script to eliminate a job nobody wants to do by hand, or drafting an SOP so the fix sticks. I'm as comfortable walking a non-technical teacher through a problem as I am building the infrastructure underneath it.
On my own time, and as a self-employed Linux systems administrator since 2016, I design and run B.Ross, a self-hosted media and cloud platform that I operate end to end. It's in the Projects section below. I use Docker, reverse proxies, virtualization, databases, and API automation on real infrastructure for which I'm personally responsible. It's the same toolkit I bring to a job. I've also taught Computer Science with Google's CS Institute.
I bring nine years of end-to-end production environment ownership, including reliability, observability, security, recovery, and capacity. I am accountable for the systems I operate and for restoring service when they fail.
Grouped by where it belongs in the lifecycle. Everything here is in production on infrastructure I run, not a checklist padded to look full.
About a decade of keeping people and systems running, from the help desk to the server room.
Foundations in algorithms, systems, and software: the groundwork for everything I build today.
Everything below runs in production. It has real users and uptime I'm accountable for, and I've had to dig it out of real failures. I built it, deployed it, and still run it.
A multi-service, containerized platform behind one hardened edge. I own every layer: host provisioning, container orchestration, reverse-proxy routing, automated TLS renewal, intrusion prevention, dynamic DNS, backups, and incident recovery.
Problem: hold dozens of real-time transcodes at once on consumer hardware, behind a residential uplink, without causing buffering or saturating my upstream.
What I own: a multi-backend streaming tier with hardware-accelerated transcoding, session load distributed across backends, bandwidth shaping, usage telemetry, and capacity planning against a hardware ceiling I can't just raise.
Outcome: used AI-assisted analysis to reverse engineer software behavior and workflows, then turn those findings into working tools and integrations.
What I built: a private AI development stack across Windows and WSL2, a C# service-control app, MCP integrations, and guarded agent workflows for software analysis, implementation, and review.
Problem: give tenants isolated, remotely managed compute and file storage on shared hardware.
What I own: VM provisioning and isolation, the storage layout, centralized remote management, and new tenant setup.
Problem: running the platform solo leaves me with recurring chores that drift if I ignore them: a rotating IP, DNS chasing it, databases too slow on disk, and media metadata that's wrong out of the box.
What I own: the automation that handles those chores. Databases run from a RAM disk, with tmpfs bind-mounted over the container and a nightly backup that pauses the service only for a sub-second RAM-to-RAM copy. The remaining automation covers IP tracking, DNS reconciliation, fail2ban self-whitelisting, batch metadata edits, and registrar and media-server automation.
I build, operate, and recover infrastructure with hands-on ownership of the systems behind the service.