The Tinker had the new sourdough loaf cut in half before anyone could stop them — not to eat, but to read it. They held the cross-section up to the light, studying the crumb, counting the size and distribution of the holes, working backwards from the bread to the variables that had made it: the hydration, the proof time, the heat of the oven in the final ten minutes. The taste was almost secondary. What had caught them was the puzzle of why this loaf had opened up and the last one had stayed dense, and until they had traced the difference to its cause, the bread was less a meal than a result waiting to be explained. That is how a Tinker tends to arrive at the kitchen: not hungry, exactly, but curious about how the thing in front of them actually works.
A recipe is a system, and a system is the part they enjoy
For the Tinker, cooking becomes interesting at precisely the point it becomes mechanical. A recipe is not a set of instructions to be obeyed; it is a process to be understood, reverse-engineered, and improved. They want to know why the butter is cold, what the resting actually does, which step is load-bearing and which is superstition handed down without reason. Once they grasp the underlying logic of a dish, they stop following the recipe and start running the system, adjusting variables to see what moves — more salt in the pasta water, a longer sear, a different flour — treating their own kitchen as a small laboratory where every meal returns data. This is the same independent, analytical drive that runs through everything a Tinker does: the need to understand a thing from the inside rather than take it on trust. Food that comes with a working mechanism underneath holds them completely. Food that is merely decorative or ceremonial tends to lose them.
Eating itself ranks lower than understanding it
The order of priorities is worth being honest about. For a Tinker, the act of eating is often the least interesting part of food. The problem-solving of cooking can absorb them for hours; the meal it produces is consumed in minutes, frequently while reading or thinking about something else entirely. This is where the autonomy turns into neglect. Left alone and deep in a project, a Tinker will let their own feeding default to whatever is fast and requires no decisions — the same three meals on repeat, food treated as fuel for the mind rather than an event in its own right. Hunger gets logged as a mild inefficiency to be cleared, not a pleasure to be met. They can cook an elaborate, optimised dish to impress themselves with the method and then, on an ordinary Tuesday with no one watching, forget to eat until it is dark, because eating answered no question and so never reached the top of the queue.
The table is a system the Tinker keeps misreading
There is a deeper fault here, and it shows up where food stops being mechanical and becomes social. A shared meal is not really about the food; it is about the company, the slow talk, the wordless companionship of sitting together with no problem to solve. This is exactly the register a Tinker finds hardest. They will steer the conversation towards the technique, the sourcing, the optimisation — anything with a right answer — because the open, undirected warmth of the table offers nothing to figure out and therefore feels faintly purposeless to them. When someone across the table is upset and the meal goes quiet, the Tinker’s instinct is to fix the problem rather than simply share the silence, to answer a feeling with a practical suggestion and not understand why it did not land. The lone-wolf streak does the rest: under strain, they will quietly skip the shared meal altogether and eat alone at the bench, telling themselves it was about efficiency when it was really about withdrawal.
What the Tinker has not weighed is that the meal was never the inefficiency it looks like. The hour spent eating slowly with people you love produces no measurable output and solves no stated problem, and a Tinker is tempted to read that as time poorly spent. But the table is running a system after all — one with no schematic, where the value is precisely that nothing is being optimised and no one is being fixed. The thing being maintained there is the relationship itself, fed in a currency the Tinker has spent their life undervaluing because it cannot be reverse-engineered. A Tinker who can sit at that table without reaching for the puzzle, who can let a meal be company rather than a problem, has finally solved the one mechanism their method was always too quick to dismiss: that some systems are kept alive by being shared, not by being understood.
