Notes of a Technosaur
Or: An ode to self-awareness, from one quality bottleneck to another. You leave your kid at daycare every morning. A stranger with a certificate keeps your most precious thing alive while you work, and you're fine with it. You even pay them for it. Then you drive to
Or: the SDLC doesn't fail at the stages. It fails at the handoffs. The stories below are composites. Names, products, and companies have been removed, blended, and shuffled across two decades of shipping software. If you think one of them is about your company — that's
Or: What Twenty Years of Experience Is Actually Worth When the Machine Learned It in Twenty Seconds Last month, a junior engineer shipped a feature in one afternoon. Not a toy. A real feature. Async job orchestration, retries with backoff, idempotency keys, decent tests. The kind of thing that would
Smells of code, facts, numbers, and dreams. It was a routine dependency update. You know the kind. Lock file refresh, a few minor versions bumping, the sort of thing that takes twenty minutes and earns you exactly zero praise because nothing visibly changed. You do it anyway because unpinned dependencies
If you haven’t watched Stranger Things, stop reading this and go watch it. I’ll wait. Back? Good. For the rest of us: Hawkins, Indiana looks like a perfectly normal American town. Diners, bicycles, bad haircuts. Everything where it should be. Except underneath it — literally underneath
Your distributed system has logs. Thousands of them. And it’s still lying to you. On trace IDs, silent failures, and the contract that fixes it.
Or: How I Learned to Stop Worrying and Embrace Probabilistic Done There was a rhythm to it. A customer needed something. We’d sit down, think about it for a bit, maybe squeeze a refactor or a dependency update alongside — the kind of housekeeping you can only do
Or: How I Learned to Stop Worrying and Become a Very Expensive Prompt Engineer The Hype Arrives at Your Door I resisted longer than most. While half of LinkedIn was busy posting “10 prompts that made me 10x more productive”, I was doing the sensible thing: ignoring them
Or: How I Learned to Stop Worrying and Actually Read the Documentation There’s a special kind of developer. You’ve met them. They discover MongoDB, read the words “flexible schema” on the landing page, feel a warm rush of freedom in their chest, and immediately
Or: How I Learned to Stop Worrying and Accept That Someone Will Always Shit in the Traces It was minus twenty-two degrees somewhere north of Rovaniemi. The kind of cold that doesn’t argue with you. The kind of dark that makes you question your life choices and career
Cache invalidation strategies with real numbers. When Redis saves money vs. $12k/month overhead. Practical guide to caching without the hype.
Or: How I Learned to Stop Worrying and Love the Retry-After Header If you've been building systems that rely on external APIs for more than a week, you've already felt it. That cold sweat when production breaks at 3 AM because Microsoft decided to throttle your
Or: Why Your Production System is a Black Box and Everyone is Pretending That’s Fine Remember that scene in The Matrix where Neo sees the code flowing down the screens and suddenly everything makes sense? That’s what proper observability feels like. Without it, you’re
This article presents publicly verifiable information about Kerna Health's leadership and funding history, followed by a clearly attributed account of non-payment based on the author's own correspondence with company representatives. No allegations regarding intent or misconduct are made beyond the documented facts. 1. Andreas Typaldos —
Every architect’s favorite interview question: “Should we use REST or gRPC?” Wrong question. It’s like asking Neo if he should take the red pill or the blue pill before asking what the Matrix even is. The right question: Do your services even need to