Who I am
I live in the Cleveland area with my wife and our two kids. Family comes first, and it shapes how I spend my time and what I share here. We married in 2012 after being friends since childhood. My wife works in the mental health field, and we enjoy photography and time together as a family.
My kids keep me grounded. My son trains in ATA Karate and earned his black belt. My daughter studies ballet and lyrical dance. Both are interested in technology and like to build and tinker. Most weeks, our time outside of work is a mix of practices, small projects, and whatever the week brings. When we can, we build things together.
I love learning and I follow topics across history, current events, and brand-new ideas. I am a big history buff. I also like to tinker and build, from quick weekend projects to deeper technical experiments. I make time for friends too, including an evening playing Uno.
I also enjoy classic games. I grew up on the SNES, Game Boy Color, and Sega Genesis, plus early Windows PC games like Duke Nukem 3D, Warcraft I and II, StarCraft, and Descent 1 through 3. Favorites include The Legend of Zelda: A Link to the Past and Pokémon Red, Blue, and Yellow.
That interest shows up in my workshop and home lab. I run a small 3D printing farm, a laser cutter, and a vinyl cutter. I also have a 42U server rack in my basement. I like systems that are easy to maintain, monitor, and automate.
Professionally, I serve as Chief Digital Officer (CDO). I lead cloud work in AWS, software engineering, and data security.
What I do
AWS and datacenter operations
Run hybrid environments, keep production stable, and design for repeatable recovery.
Infrastructure as code
Terraform and Ansible for consistent builds, change control, and reduced drift.
Delivery pipelines and internal tooling
CI/CD, job runners, and small utilities that remove manual steps and reduce errors.
Documentation and runbooks
Write procedures people can follow under pressure, and keep them current.
Reliability practices
Observability, incident response habits, and pragmatic on-call hygiene.
Roadmaps that ship
Translate priorities into an executable plan, with clear tradeoffs.
Work snapshot
What I focus on in day-to-day work, and what I push teams toward over time.
Keep operations boring
Reduce toil with automation, and treat repeat failures as product defects.
Make ownership visible
Clear escalation paths, fair rotations, and documented responsibility.
Ship repeatable infrastructure
Standard patterns, guardrails, and reviewable changes across AWS and datacenters.
Design for recovery
Backups, DR drills, and runbooks that hold up under pressure.
Measure what matters
Useful telemetry, signal-focused alerting, and fast feedback loops.
Raise the floor
Mentoring, automation, and documentation so the team does not depend on heroes.
-
20+ years
Experience across software, systems, networking, and operations, with a strong bias toward automation and clarity.
-
2001
Started building and hosting websites, and kept building systems that are meant to last.