The latest

Exploring micro-frontends: why, when & how (and why I'm doing it anyway)

Exploring micro-frontends: why, when & how (and why I'm doing it anyway)

By Carl Eubanks“A path is whatever you make of it—as long as it gets you where you want to go.” — Carl Eubanks, 2025 Step back and see the big picture I always start with why. Call it a ritual: three deep breaths, zoom the camera out, and ask whether the work in ...
I WAS BOREDTECHNICALLY
Building a notification orchestrator: a decision log

Building a notification orchestrator: a decision log

By Carl EubanksThis isn’t a copy‑paste tutorial. It’s a behind‑the‑scenes look at why I chose a specific shape—hexagonal micro‑orchestrator on SNS → SQS—for a cross‑channel notification pipeline, and the trade‑offs I wrestled with along the way. Problem Statement ...
ENGINEERINGSYSTEM DESIGN
The pigeon coop & the back room: A wiseguy's guide to not screwing up the message

The pigeon coop & the back room: A wiseguy's guide to not screwing up the message

By Carl EubanksI like to write stories to better explain problems I have or concepts I want to share. I still want the message to be clear, concise, and easy to digest, so I’ll give you a glossary to refer back to when reading the story if it it doesn’t click the f...
AWSAWS SNS
Design bit.ly

Design bit.ly

By Carl EubanksFor each portion, I’ll regurgitate the feedback I received. Each system design interview is different, so it’s interesting to see how hellointerview has tailored their AI feedback system. Requirements Functional requirements Users should be able to ...
SYSTEM DESIGNTECHNICALLY
Caching: The bikini bottom marathon

Caching: The bikini bottom marathon

By Carl EubanksWhat is caching? Caching is the practice of storing something in a location from which it can be quickly retrieved, thereby speeding up future accesses. It's not always permanent--it's more of a short-term memory for whatever you might need really so...
TECHNICALLYCACHING