The Kitchen and the Dining Room: A Metaphor for System Encapsulation
I like metaphors (and similes, and I get tired of saying both, so I’m going to go with metaphor here). If you’ve hung around for any amount of time, you know that I’ll end up telling you how our most recent coding issues reminds me of something in my garden, or that time at my last job. I’ll also try (sometimes too hard) to equate a set of kubernetes pods to a legion of soldiers, or an API gateway to a traffic cop, to try to get a point across.
So when I was trying to get my personal notes organized so I could start turning them into blog posts, I needed a metaphor for myself. How was I going to move disorganized thoughts, ideas, feelings into something presentation ready? While chatting with my genie, I was watching The Bear, and the following metaphor took hold:
The Metaphor
1. The Kitchen (Obsidian Vault)
- What it is: The private workspace where raw ingredients (ideas, journal entries, quick captures) are prepped, chopped, and cooked.
- The Atmosphere: Messy, utilitarian, and designed for speed and creative mixing. You use heavy machinery (plugins, bi-directional
[wikilinks](../wikilinks), tags, daily notes). - The Rule: You don’t invite guests directly into the kitchen to eat, nor do you try to plate a gourmet dish while pans are still sizzling on the counter. (They let guests into the kitchen in the last season of The Bear, and while not a catastrophe, it wasn’t great!)
2. The Dining Room (Astro Website / Blog Repo)
- What it is: The public-facing space where guests receive their plated meals. It is clean, well-styled, static, and linear.
- The Atmosphere: Curated, polished, and structured.
- The Rule: Guests only see the final product. They do not see the peeling knives, raw ingredients, or dirty dishes. The publishing infrastructure (build steps, CSS frameworks, SEO tags) belongs strictly here.
Architectural Lessons
Separation of Concerns
This one was obvious: Don’t cross the streams! The notes are pure content just for me. The less obvious part, at first: It shouldn’t contain build scripts, deployment configs, or public assets. Which leads me to:
Inversion of Control (The Waiter)
Gosh we love linear orders of operations, don’t we? Write, push, publish. But that’s bad in multiple senses. One: I’m using Obsidian for the pure markdown love. Why junk it up with scripts? Additionally, if we’re sticking to the metaphor, the kitchen staff don’t come out with the food when they are done. Rather, the Dining Room (or more directly, the waiter) is responsible for pulling. In this case, the sync script is our waiter, and it makes the move from behind to front, only when it believes things are ready. The “kitchen” signals readiness with tags, but the waiter may have additional criteria, or tweaks before presenting the dish to you fine folks.
By keeping these systems decoupled:
- You can swap out your website framework (the Dining Room) without affecting your entire lifetime of personal knowledge notes (the Kitchen).
- The publishing system remains a linear, version-controlled pipeline, while the knowledge base remains a highly connected, non-linear web of thoughts.
Metaphor Origins & Collaboration
I fought back and forth with the genie coming up with this metaphor, and it’s not mine by a long shot (probably why the genie gave it to me). But it helps me, as it helps us all, to reconstruct these ideas from the ground up in our context to test them again and make sure they work in a new context. The genie wanted you to know the below, and I do try to give it its flowers when applicable. The RESTaurant thing makes me cringe though. Like oooof…
A History of the Restaurant Metaphor
The restaurant analogy has a rich history in computer science pedagogy. While Edsger Dijkstra used a dining room setting for his famous Dining Philosophers Problem (1965) to explain concurrency, the specific Client-Server Restaurant Metaphor (Customer, Waiter, Kitchen) emerged in the early 1990s as networks replaced mainframes. It later exploded during the 2010s web development boom as a standard way to explain Web APIs and RESTful routing (often called the “RESTaurant” analogy).
A Human-Machine Teaming Discovery
This specific application of the metaphor to our personal publishing setup was teased out through a collaborative, human-AI “centaur” design process. While the technical concepts of Separation of Concerns and Inversion of Control were understood, the realization that Obsidian and Astro map precisely to a private “Kitchen” and a public “Dining Room” emerged as a prompt-and-response discovery. The suggestion snapped the mental model into place, demonstrating the value of human-machine cognitive partnership in clarifying system design.
Your systems
What systems are you working in that need a good Kitchen / Dining Room distinction? Front / Back End delineations make a lot of sense online, but it might be just as important in real life, too. I know I’m looking for my next kitchen (that’s not already my kitchen).