About Me

I’m a cloud and infrastructure engineer with 12+ years in mortgage and financial services. I started in Service Desk and Tier 2, and that early experience shaped how I design infrastructure today, with an emphasis on reliability, observability, and incident response. I care about building visibility that engineers actually rely on during outages, not dashboards that only look good when systems are healthy.

Developers focus on delivering features. My focus is on helping them deliver responsibly, in ways that work not just in development, but for the Operations teams who support those systems in production.

My strongest areas are Microsoft infrastructure and observability. I’ve built end to end monitoring for loan application workflows, supported large data migrations, and worked with teams to reduce cloud waste through right sizing and decommissioning.

Most of my infrastructure work spans Azure and AWS, often alongside hybrid and on prem environments. I grew up in the Microsoft stack with Windows, IIS, .NET, monoliths, and Azure, where stability often depended on caution and change avoidance. Later, I learned to appreciate AWS, Linux, cloud native architectures, containers, and infrastructure as code in environments where frequent deployments were normal, including during business hours.

I’m a strong proponent of work life balance and believe resilient, well designed infrastructure is key to keeping teams healthy. That requires systems that surface problems quickly, limit blast radius, and recover safely. Strong health checks, fast feedback loops, blue green deployments, and easy rollback turn change into a routine operation rather than a risk.

Outside of work, I enjoy spending time with family, staying active, and traveling. I like trips that are full and hands on, with experiences that involve effort, movement, and a sense of adventure. That has included an overnight cave expedition in Vietnam, as well as motorbiking and scuba diving in Thailand.

I’m learning to play guitar and enjoy the steady, imperfect process of building a new skill. LCD Soundsystem and The Strokes are frequent go-tos. When it comes to staying active, I tend to dabble and explore, from tennis to jiu jitsu and wrestling, and more recently, pickleball.

Skills & focus

Currently upskilling

Skills I’m actively investing in right now (and using on this site):

AI Agents
Orchestration patterns, tool routing, guardrails, and agentic workflows.
Example: paddle shop + automation workflows
Terraform
IaC patterns, remote state, environments, and CI-driven deploys.
Example: SWA infra + deployment pipelines
Azure Static Web Apps
Multi-app deployments, subdomains, Functions API, and CDN edge behavior.
Example: main site + playground deployed independently

Core strengths

Microsoft infrastructure

  • Windows Server, IIS, .NET (Framework + Core)
  • Active Directory (operations, hygiene, troubleshooting)
  • PowerShell automation (5.1 + 7)

Cloud & platform

  • Azure (core services, identity/RBAC, networking fundamentals)
  • AWS (working knowledge; learned on cloud-native teams)
  • Hybrid/on-prem integration patterns

Observability

  • Monitoring design for workflows & business-impact views
  • Pragmatic alerting: reduce noise, improve actionability
  • OpenTelemetry concepts (signals, context propagation, OTLP)

Operations mindset

  • Incident response & troubleshooting
  • Cost awareness (right-sizing & decommissioning)
  • Build visibility that helps during outages

Observability viewpoints

Tools come and go. I care about signal quality, correlation, and helping humans reason about production under stress.

My take

  • AppDynamics is strong for business impact in legacy/monolithic systems, but it rewards intentional instrumentation — not “monitor everything.”
  • Datadog is the closest you’ll get to a true single pane of glass with excellent correlation, but you need cultural readiness to manage cost.
  • LogicMonitor works well in MSP-style environments where you need to onboard diverse infrastructure quickly (agentless).
  • New Relic deserves mention for its generous free tier (you’re being monitored on it now).

OpenTelemetry

I see OpenTelemetry as a force for good. Standardization around OTLP, schemas, and semantics is a net positive, and it’s a great way to keep instrumentation portable and consistent across teams.

That said, portability is overrated. Observability is foremost a data problem; a top-tier presentation layer that helps humans reason about systems matters more than avoiding vendor lock-in.

At the end of the day, our role in IT is to keep applications running reliably.