About 8bytes! The Software Restaurant

How This Started

I’ve been writing code for more than 20 years.

Starting back with freelancing, before joining the corporate trenches as a developer 18 years ago. Moved up to team lead, where my team built an online banking platform that operated across two markets. Eventually I got out of the trenches, changed paths to architecture and became an architect in an enterprise-grade Bancassurance Group - mapping cross-domain dependencies, sitting in merger meetings, and translating between business strategy and actual technical reality.

You know, the fun job of explaining to executives the benefits of building a private cloud and your own Kafka cluster.

The Turning Point

Some time ago, one of our most critical systems hit what I can only describe as the perfect storm.

Classic enterprise scenario: legacy system running core business operations. Everyone knew it needed a complete rewrite. The business agreed it was technical debt we couldn’t keep ignoring.

But budget? “Maybe next year. We are on a merger now, other priorities…”

Years of “other priorities.”

Then the Storm Hit

Software bug in an off-the-shelf component. Faulty HSM hardware. Thread starvation. Thundering herd. Load balancing issues. Database connection pool exhaustion. The kind of cascading failure where fixing one bottleneck just revealed the next one waiting to take you down.

We’re bleeding customers. Every minute costs money.

Explaining this to the CTO and IT board was challenging enough - and they’re technical people who understand thread pools and connection limits.

But then I had to explain it to the board of directors. And we needed approval for emergency infrastructure changes. Today.

I started with the technical reality:

“A bug in a third-party component triggered thread pool saturation, creating blocking I/O, which exhausted the connection pool, which caused the load balancer to...”

Thirty seconds in, I’d lost them. So I pivoted:

“Imagine a restaurant during dinner rush. Our waiters take orders from tables, bring the tickets to the kitchen, but instead of returning to the dining area to handle other tables, they just freeze at the pass - waiting for the chef to finish cooking the dish. Only after the dish is ready do the waiters ‘resume’, serve it, and continue with other tables. (thread-blocking I/O in our application)

Meanwhile, the chef is stuck because every pot is dirty and the dishwasher is backed up. (db connection pool saturation)

And here’s where it gets worse: customers keep flooding in - not just regular dinner crowd, but people hearing about the chaos and showing up to see what all the commotion is about. (thundering herd)

The host has no idea how many people are actually seated at each table. So he’s distributing guests based on... the color of their clothes. And because it’s evening, there are a lot of people wearing black suits. They all end up at table 11. (load balancing issues)

One stuck waiter. Frozen waiters at the pass. Overwhelmed chef. Backed-up dishwasher. Flood of curious customers. And everyone in black getting sent to the same overloaded table.

The whole restaurant halted!”

And They Got It!

I could see it in their faces - they were visualizing the comic restaurant scene we'd found ourselves in. The kind where you don't know whether to laugh or cry.

They got both the short-term firefighting and the long-term sustainable fixes.

The CEO leaned back: “I don't know about the rest of you, but I understood that. You promised it to be a bit techy, but you made it really digestible! Thanks for breakfast - I hadn't eaten yet, and now I'm full until dinner at least. Although my stomach hurts from all those failures."

Plan Approved. Budget Allocated. Fire Extinguished.

That’s when I learned: Complex technical disasters require simple human metaphors - not to dumb things down, but because a metaphor people can visualize is worth infinitely more than a technically perfect explanation nobody understands.

Why I Actually Care About This

I have a son with dyslexia. Traditional explanations bounce right off him. But when I draw things out, use metaphors, connect concepts to things he’s seen? It sticks. And now and then I hear from him something like: “Aaa, the exploding lasagna! Got it!”

If metaphors work for a kid struggling with reading AND a board of directors juggling merger priorities, they probably work for everyone.

People don’t remember technical explanations. They remember stories that connect to something they already know or can imagine. That’s what we call - mental model.

What 18 Years Actually Taught Me

I’ve shipped features that crashed in production. I’ve designed architectures that needed complete rewrites. I’ve debugged disasters at 3 AM during go-lives. I’ve sat in post-mortems explaining to very angry people why the banking system went down.

I’ve even mopped water off servers during a flood in the middle of a critical system migration (truly biblical story).

Because that’s enterprise architecture - sometimes you’re designing elegant distributed systems, and sometimes you’re literally holding a mop while the new banking platform deploys.

Those failures taught me more than any success.

When you’re mapping dependencies across merged enterprise systems, you see things fail in spectacular ways. Not because people are incompetent - but because complexity compounds, and nobody bothered to ensure everyone understood the actual risk.

That’s why every episode of 8bytes! comic includes “Famous Failures” - real crashes from Apple, Google and the like. Not to point fingers, but because we all build things that break, and learning from other people’s disasters is a hell of a lot cheaper than creating your own.

Quick wins look good on LinkedIn. Deep learning from catastrophic failures (and the occasional flood)? That’s what keeps your banking system running when it actually matters.

What This Newsletter Is

Tech concepts explained through restaurant chaos.

Every episode includes:

• Comic intro - Julia’s kitchen disasters

• Technical breakdown - how it actually works under the hood

• Famous failures - when Apple, Google, or Meta got it catastrophically wrong

• CEO-digestible menu - how to explain this to people who don’t code

Who This is For

• Developers trying to level up beyond “just writing code”

• Tech leads tired of blank stares when explaining architectural decisions

• Architects who need to sell complex solutions to non-technical stakeholders

• Anyone who’s ever thought ”I understand this perfectly - why can’t I explain it?”

If you’ve been in a meeting where your brilliant technical solution died because nobody understood why it mattered, this newsletter is for you.

How to ​Choose Your Table

​Regular Guest Access (Free)

Receive the regular “8 bytes” comic and high-level restaurant metaphor for complex technology topics to help you understand the concepts or use the idea to explain them to others.

The Sous-Chef (Paid)

♨ Deep Dives into the Recipe - Get detailed explanation of the episode topic.

♨ ”The CEO-digestible menu” - Metaphor ideas to help you explain technology to the business and sell architectural ideas to the CEO.

♨ “Big Failures” Sorbet - Examples for real-world production outages and software catastrophes related to the episode topic.

♨ Exclusive Community Access - Join the private chat to discuss the “spiciest” bugs and architectural challenges.

♨ Full Archive Access - Every dish we’ve ever cooked is waiting for you!

♨ Bonus Dessert - Downloadable high-resolution PDF comic episodes and printable content like stickers, cheat sheets, a funny “Seasonal Restaurant Menu” to hang in the office and more…

The Michelin Star Patron (Founding Member)

♨ All Sous-Chef Benefits

♨ Permanent Wall of Fame - Credits as a sponsor: a Cameo role in my comics or a dedicated mention of your name/company.

♨ Design the Menu - You have the power to suggest and vote on topics for future episodes. Your technical challenges move to the front of the kitchen!

♨ Partner Program - As a founding member, you are eligible for a special affiliate partnership. If you help bring new guests to the restaurant, we both share the success.

Illustration credits: Comic scenes conceptualized by 8bytes and rendered by Nano Banana.