In 4 months, we moved our core platform from a legacy setup to a cloud-native architecture with less operational friction.
Available · Q3 engagements
~/ Software systems that outlastscale withship faster thansurvive the next quarter.
Field notes and hands-on consulting. Mostly TypeScript, AWS, and the organizational shapes around them.
Latest Posts and Notes
View All PostsMatch code-architecture weight to each runtime's init-amortization ratio: lean functional handlers on single-purpose Lambda, moderate structure on a Lambdalith, and full OOP/DI/hexagonal only where a long-lived runtime amortizes the init. Keep one delivery-agnostic core across all of them.
A small, complete URL shortener on AWS Lambda and DynamoDB, built with Effect and SST v4, showing schema-at-the-boundary, layers, and tagged-error mapping in code small enough to hold in your head.
How to slice AWS Lambda functions for HTTP APIs and events: default to single-purpose, treat the single-domain Lambdalith as an earned exception, and use the platform forces that decide it.
Selected Outcomes
With a focused AWS and serverless redesign, we reduced annual infrastructure spend by around $200K.
How I Can Help
Focused support for architecture and delivery decisions.
Architecture Review
I turn your current setup into a clear, practical technical direction.
Sharper technical decisions
Technical Advisory
Short, practical guidance for product and engineering teams.
Fast and focused feedback