I'm a systems and infrastructure administrator with professional experience in Microsoft 365, Active Directory, Exchange Online, VMware, networking, migrations, backup and recovery, and multi-site IT infrastructure.
Outside of work, I build and document infrastructure projects focused on Linux, virtualization, network security, automation, and DevOps. I use this GitHub as a technical portfolio to document what I build, the engineering decisions behind it, and what I learn along the way.
A security-focused infrastructure project exploring how to design and operate a homelab using principles I would expect from production infrastructure.
The project covers areas including network segmentation, privileged administration, virtualization, Linux infrastructure, recovery, validation, and infrastructure automation.
Focus: Proxmox VE · pfSense · Linux · Networking · Security · Infrastructure · DevOps
A documented Fedora hardening project for a workstation used to administer privileged infrastructure.
The project focuses on defense in depth, disk encryption, Secure Boot, SELinux, host firewalling, auditing, authentication hardening, runtime validation, and recovery planning.
Focus: Fedora · Linux · Bash · SELinux · LUKS · firewalld · Security Hardening
A collection of programming exercises and solutions used to strengthen the scripting and problem-solving skills I apply to systems administration and infrastructure automation.
Languages: Python · Go · Bash · YAML
I'm currently developing deeper hands-on experience with:
- Linux systems administration
- Infrastructure automation
- Network and infrastructure security
- Proxmox and virtualization
- pfSense and network segmentation
- Python and Bash
- Git and CI/CD
- Containers and Kubernetes
I believe good infrastructure engineering includes good documentation.
My public infrastructure repositories are intentionally sanitized before publication. Operational details such as credentials, internal addressing, sensitive hostnames, recovery information, and other security-sensitive configuration are excluded or generalized.
Where possible, I document not only what I built, but also:
- why I chose a particular design;
- alternatives and tradeoffs I considered;
- how I validated the implementation;
- problems encountered along the way;
- recovery considerations;
- what is implemented versus what is still being designed.