"𝘛𝘩𝘦 𝘲𝘶𝘦𝘴𝘵𝘪𝘰𝘯 𝘪𝘴𝘯'𝘵 𝘸𝘩𝘦𝘵𝘩𝘦𝘳 𝘈𝘐 𝘸𝘪𝘭𝘭 𝘵𝘳𝘢𝘯𝘴𝘧𝘰𝘳𝘮 𝘺𝘰𝘶𝘳 𝘣𝘶𝘴𝘪𝘯𝘦𝘴𝘴, 𝘣𝘶𝘵 𝘸𝘩𝘦𝘵𝘩𝘦𝘳 𝘺𝘰𝘶'𝘭𝘭 𝘭𝘦𝘢𝘥 𝘵𝘩𝘢𝘵 𝘵𝘳𝘢𝘯𝘴𝘧𝘰𝘳𝘮𝘢𝘵𝘪𝘰𝘯 𝘰𝘳 𝘣𝘦 𝘥𝘪𝘴𝘳𝘶𝘱𝘵𝘦𝘥 𝘣𝘺 𝘪𝘵" 🚀

As a Principal Solutions Architect at AWS, I architect transformative cloud solutions that drive business outcomes, with deep expertise in Machine Learning and Generative AI. My evolution from hands-on developer to enterprise architect gives me a unique lens for building scalable, efficient solutions that bridge technical excellence with business value.

𝗜𝗻𝗱𝘂𝘀𝘁𝗿𝘆 𝗟𝗲𝗮𝗱𝗲𝗿𝘀𝗵𝗶𝗽 🎯 I specialize in Media & Entertainment, guiding organizations through complex digital transformations. As a founding member of AWS’s global expert group for Advertising and Marketing Technology, I combine deep industry knowledge with practical implementation experience to solve real-world challenges.

𝗧𝗵𝗼𝘂𝗴𝗵𝘁 𝗟𝗲𝗮𝗱𝗲𝗿𝘀𝗵𝗶𝗽 & 𝗞𝗻𝗼𝘄𝗹𝗲𝗱𝗴𝗲 𝗦𝗵𝗮𝗿𝗶𝗻𝗴 💡 I’m passionate about demystifying emerging technologies, particularly Generative AI. Through industry speaking engagements, technical deep-dives, and strategic keynotes, I help teams understand not just the “how” but the “why” and “what’s next” of technology adoption. My content focuses on practical implementation while thoughtfully examining the broader implications of technological change.

𝗕𝗲𝘆𝗼𝗻𝗱 𝗧𝗲𝗰𝗵𝗻𝗼𝗹𝗼𝗴𝘆 🏔️ When I’m not architecting cloud solutions, you’ll find me exploring mountain trails. This love for nature provides the perfect counterbalance to my technical work and often inspires fresh perspectives on complex problems.

𝗥𝗲𝗮𝗱𝘆 𝘁𝗼 𝗮𝗰𝗰𝗲𝗹𝗲𝗿𝗮𝘁𝗲 𝘆𝗼𝘂𝗿 𝗔𝗜 𝗮𝗻𝗱 𝗰𝗹𝗼𝘂𝗱 𝘁𝗿𝗮𝗻𝘀𝗳𝗼𝗿𝗺𝗮𝘁𝗶𝗼𝗻? 🎯 Whether you’re looking to architect your next breakthrough solution, navigate emerging AI technologies, or transform your organization’s approach to cloud innovation—let’s connect. I’m always excited to discuss how technology can unlock new possibilities for your business.

==> 📩 𝗗𝗿𝗼𝗽 𝗺𝗲 𝗮 𝗺𝗲𝘀𝘀𝗮𝗴𝗲 | 🔔 𝗙𝗼𝗹𝗹𝗼𝘄 𝗳𝗼𝗿 𝗔𝗜 & 𝗖𝗹𝗼𝘂𝗱 𝗶𝗻𝘀𝗶𝗴𝗵𝘁𝘀 | 🤝 𝗟𝗲𝘁’𝘀 𝗰𝗼𝗹𝗹𝗮𝗯𝗼𝗿𝗮𝘁𝗲

This is a personal blog. Opinions expressed here are my own and do not represent the views or positions of my employer.

Recent Blog Posts

Laws & Disorder #3 — Tesler's Law: You Can't Delete Complexity, Only Choose Who Owns It

TL;DR: Tesler’s Law, the conservation of complexity, says a system has an inherent amount of complexity that can be reallocated between owners but never deleted. The useful move is to split that into two numbers most people conflate: the total complexity of the whole system, and the complexity you personally have to manage and operate. Adopting a well-run managed service shrinks the second number, which is a genuine win. But a component you didn’t right-size still adds to the first. AI now makes it cheap to build a focused component with exactly the features you need and less inherent complexity than a general-purpose product, which can lower the total, but you now own and operate it, so what you manage goes up. Buy less to manage, build with AI for less total but you hold the pager. Optimize the complexity you actually manage, and keep an eye on the total.

Third in “Laws & Disorder.” After Conway’s Law and Hyrum’s Law, here’s the one that quietly decides every build-vs-buy argument.

By Stefan Christoph

Stop Guessing Which Coding Agent to Use — Benchmark It on Your Own Tasks

TL;DR: Generic coding-agent leaderboards don’t tell you which model or tool fits your work at a budget you’re willing to spend. So I built a small task set that mirrors my real work and ran an open-source framework (aws-samples/sample-agent-cost-bench) that measures cost, quality, and latency together. Two findings surprised me: the priciest model (Opus 4.8) missed a task that a mid-priced one (Sonnet 4.6) passed at a third of the cost, and, when comparing the same model across two tools, the per-credit rate you actually pay can flip which tool looks cheaper. All numbers below are from real runs I did on 2026-07-16.

Every few weeks a new coding-agent leaderboard makes the rounds, and every time the question I actually care about goes unanswered: not “which model tops a public benchmark” but “which model, wrapped in which CLI, does my kind of work well enough at a price I’m happy to pay.” Those are two different questions, and neither shows up on a generic leaderboard built from someone else’s tasks.

By Stefan Christoph

The Quadratic Wall: The Algorithmic Race to Beat O(n²) Attention

TL;DR: Standard self-attention costs on the order of n² in the sequence length n, in both arithmetic and the attention-score memory it materialises. Almost every long-context architecture headline of the last few years is an attempt to beat that wall, and the honest way to read them is by which cost axis each one moves. FlashAttention keeps exact O(n²) arithmetic but cuts materialised auxiliary memory from O(n²) to O(n) and sharply reduces the memory it moves. Sparse attention (when each token attends to a sublinear number of positions), linear attention, and state-space models like Mamba (which its authors report reaching roughly linear time in the sequence length, for a fixed state width) lower the arithmetic exponent itself by constraining or replacing exact all-pairs attention. Those axes — arithmetic, memory, data movement, latency — do not move together, so no single technique simply “wins,” and the field has not crowned one. Neither is a free win, and the field has not crowned a winner. The practical takeaway is older than any of these papers: the cheapest quadratic is the one you never trigger, so context discipline and retrieval can beat brute-forcing a longer prompt — when the retrieval earns its keep, which is an end-to-end question to measure.

Back at university, one exercise showed up in every algorithms course in a slightly different costume: here is the obvious quadratic solution, now can you do better? Sometimes you could drop it to n log n, sometimes only to a smaller constant, and sometimes the honest answer was that the quadratic was inherent and the interesting work was elsewhere. That instinct, look at an O(n²) and ask what it would take to beat it, turns out to be the cleanest way I know to read the modern architecture race.

By Stefan Christoph

About

Recent Blog Posts

Laws & Disorder #3 — Tesler's Law: You Can't Delete Complexity, Only Choose Who Owns It

Stop Guessing Which Coding Agent to Use — Benchmark It on Your Own Tasks

The Quadratic Wall: The Algorithmic Race to Beat O(n²) Attention

More

Laws & Disorder #2 — Hyrum's Law: In the Age of Agents, Who Pays for a Broken API?

From Robot Soccer to the Agentic World Cup: Why Games Move AI Forward

Why AI Tokens Are So Expensive — and What Actually Makes Them Cheaper

Laws & Disorder #1 — Conway's Law: Your Org Chart Is Your Real Architecture (and AI Is Redrawing Both)