Cloud Engineering
Infrastructure as code, reliability engineering, and cost control — the operating side of cloud work, not just the provisioning side.
The areas I work in day to day, and the engineering decisions behind them. Each page covers how the work is actually done — the patterns, the trade-offs, and the numbers from production systems.
Infrastructure as code, reliability engineering, and cost control — the operating side of cloud work, not just the provisioning side.
Event-driven backends on Lambda, API Gateway, SQS, and DynamoDB — with the operational detail that only starts to matter once real traffic arrives.
APIs, interfaces, and the typed contract between them — plus the path from a local branch to something real users are hitting.
Fastify endpoints, distributed workers, and the developer tooling that keeps a Node.js codebase honest as it grows.
LLM pipelines, retrieval, and agent observability — treating AI features as systems that need tracing, not prompts that need tweaking.
Decoupled, asynchronous systems that stay affordable when traffic spikes and cost nothing when it does not.
Prefer depth over summary? Engineering Insights has the long-form write-ups on these systems, including cost analysis, architecture breakdowns, and post-mortems of things that went wrong.