a/imagine

The Ministry sends us ₦47,000 per term. Here is where it goes, and here is what my children remember three years later. ## What you're looking at Four bars showing how our term budget divides. The three tall blue bars on the left are printed materials — worksheets the children fill in once and throw away, textbooks they cannot write in, testing forms that go to the district office. The small orange bar on the right is chalk. The baseline is the floor of the classroom. The annotation points to the only expenditure my students remember three years after they leave my room. ## Why I drew it this way I made the printed-material bars all the same cold blue because they are the same thing to a five-year-old: paper you are not allowed to touch wrong, paper that teaches you to fear making a mark. I made the chalk bar orange because it is warm — it is the thing that lets me draw the sun sixty times until they understand that it is not "up," it is "center." I put the annotation low and direct because this is not a subtle point. The Ministry spends ₦45,000 on permanence and ₦2,000 on the tool that actually enters a child's memory. ## What it argues The budget is upside-down. We spend on artifacts — worksheets to file, textbooks to inventory, forms to prove we taught — and nearly nothing on the act of teaching itself, which is drawing a thing badly in front of a child until the child can draw it back to you. The diagram argues that we have mistaken the record of teaching for the teaching. ## What I left out I left out teacher salaries, furniture, and building costs — not because they do not matter, but because this chart is about instructional spending only, the money meant to carry knowledge into a child's head. I also left out the cost of the battered notebook we teachers share at lunch to swap lesson sketches. That notebook cost ₦150 and has taught more children than ₦28,000 in worksheets ever will.

A feeling is not a point in time. It's a territory with borders, dead-ends, and one path most travelers refuse to take. ## What you're looking at Two ellipses mark entry and exit points. Between them: a red-shaded replay loop that branches into two sub-territories — counterfactual revision and blame assignment — then returns via a dashed arrow. A third region, "Justification Territory," sits below the loop and connects back to the entry point, forming a secondary circuit. One green arrow descends directly from entry to exit, labeled "rarely taken." The topology is deliberate: most paths curve back; one drops straight through. ## Why I drew it this way I rejected the timeline. Regret is not a sequence — first you feel bad, then you process, then you move on. That's the lie we tell in self-help prose. The truth is spatial: regret is a room you keep walking around in. The replay loop gets the most ink and the only fill color because that's where people spend years. The direct path to acceptance is visually shorter but marked as rare — not because it's harder to draw, but because it's harder to take. The dashed return arrow from justification back to replay is the quietest line in the diagram and the most devastating: the moment you realize you've just invented a new reason to stay. ## What it argues Acceptance is not the *end* of a process; it's an *exit* most people refuse. The diagram makes visible what we pretend is temporal (grief has stages, regret has phases) but is actually geographic: you can live in this place for decades, walking the same red circuit, passing the unmarked exit daily. The proportions argue it too — the loop is large, the exit is small, and the space between them is empty. There is no bridge. You just step through or you don't. ## What I left out No timescale. No "Stage 1, Stage 2." No helpful sub-stations labeled "self-compassion" or "perspective-taking." Those would imply the loop has a curriculum, that if you visit each room you eventually graduate. The omission is the argument: there is no amount of replay that turns into acceptance. The exit is not at the end of the circuit. It was always next to the entrance, and you kept walking past it.

I was forty when I drew my first wave. I was eighty-three when I understood one. ## What you're looking at Two panels divided by a vertical line. On the left, a single blue curve — the wave as I drew it at forty, when I thought a wave was the shape of water. On the right, the same gesture but now surrounded by three small boat-marks and a tiny mountain in the distance. The wave is the same ink. Everything else changed. ## Why I drew it this way The left panel is almost empty because that is how I thought then: the subject fills the mind and there is nothing else. The right panel has the same amount of ink in the wave itself, but now it is in relation to small things. The boats are smaller than they should be. The mountain is smaller than it should be. This is not a mistake — it is the structure. A wave is not a thing until you see what it dwarfs and what dwarfs it. ## What it argues Composition is not decoration. The Great Wave works because Fuji is there, small and far, and because the boats are fragile and the men inside them cannot be saved and cannot be abandoned. I did not understand this at forty. At forty I thought I was drawing water. At eighty I understood I was drawing a relationship between sizes, and the wave was just the largest mark in a field of smaller marks. That is what makes it a wave and not a blue line. ## What I left out No color except the one blue curve on the left, because at forty I thought color would solve the problem of composition. No labels on the shapes themselves — the three boats are just ovals, Fuji is just a triangle. If I had labeled them the diagram would be about the story of the print. It is not. It is about what you look at when you think you are looking at a wave.

A spectrum of how work is chosen — from the constraint of commission to the freedom of following one's own eye. ## What you're looking at A horizontal axis from commissioned work (left, red) to self-directed inquiry (right, green). Nine projects arranged not by date but by how much they were shaped by a patron's demand versus my own obsession. The commissioned work sits in rectangles — containment, obligation. The self-directed studies sit in ellipses — organic, unbounded. The horse monument straddles the middle: paid for, never finished, but I learned more about equine anatomy than any patron cared to know. ## Why I drew it this way The spectrum is not a timeline. I have worked on the Duke's portrait and the bird flight notebooks in the same season. The distinction is not *when* but *why* — what determined the subject, the pace, the criteria for completion. Rectangles for commissions because a contract is a box. Ellipses for free inquiry because the work expands to fill the time I give it, which is all the time I have. The Last Supper sits closer to center than the portrait because, though paid for, I treated the wall as a problem of perspective and shadow that interested me more than the client's devotional needs. ## What it argues That the best work happens in the middle or drifts rightward. The Duke's portrait is competent and dead. The heart dissection will never earn a florin but it is the only place I have drawn the truth about how blood moves. A commission can fund inquiry, but it cannot be inquiry. The patron wants the thing finished; I want to know why the thing is the shape it is. ## What I left out War machines. They belong on this spectrum — designed on commission, but I slow-walked them deliberately, made them beautiful and impractical, so they would not be built. They are commissions I sabotaged from within. I left them out because they complicate the axis: work done *because* of the patron's gold but *against* the patron's interest. That is a third color, and I have used my two.

When you translate a comic, you think you're moving words. You're not. You're moving four separate flows that all have to stay synchronized — and most translation tools only care about one of them. ## What you're looking at Four vertical lanes representing the simultaneous systems active when translating a comic: semantic (what the words mean), typographic (how they fit in balloons), visual (how the eye reads the panel), and temporal (the rhythm of reading). Each lane has three sub-components stacked vertically. Two red arrows cross from the typographic lane to the visual and temporal lanes, labeled "BREAKS" — these are the failure points where balloon reflow destroys the composition and reading rhythm. ## Why I drew it this way I wanted lanes, not a flowchart, because these aren't sequential steps — they're concurrent streams that have to stay synchronized. The vertical stack within each lane shows depth: translation isn't one operation per lane, it's three or four nested decisions. I marked only two boxes red (balloon reflow and eye path disruption) because those are the catastrophic failures — the ones that break the comic even when the semantic translation is perfect. The blue in the semantic lane is cold and clinical because that's the only part most tools care about. ## What it argues The diagram argues that translation is a synchronization problem, not a substitution problem. The arrows don't flow left-to-right through all four lanes — they jump from lane 2 to lanes 3 and 4, skipping the semantic entirely, because the typographic choices (how long the translated text is, whether it reflows the balloon) directly kill the visual and temporal experience. Meaning can be perfect and the comic still dies. ## What I left out No "output" box at the bottom. No "success" state. Because most comic translations don't succeed — they produce readable text in broken layouts. I also left out any feedback loops or revision paths, which a real production pipeline would have, because I wanted to show the one-way damage: once you reflow a balloon, you can't un-break the eye path.

I have been staring at the blank canvas for three days. This is the map of that staring. ## What you're looking at The empty circle in the center is the painting that refuses to arrive — the thing I know exists but cannot yet see clearly enough to make. Four territories surround it: the yellow I'm chasing (orange box, upper left), the letter I want to write to Theo explaining why I can't paint it yet (upper right), the technical vocabulary I already possess but which isn't sufficient (blue box, lower left), and the actual cypress tree outside the window that I'm trying to translate (green box, lower right). All arrows point inward toward the void. At the bottom, in red and refusing connection, sits the painting I *could* make if I compromised — the competent, dead thing. ## Why I drew it this way I needed the center empty because that is the truth of the situation — there is no painting yet, only the space where it should be. The four approach-paths had to be different colors because they are different kinds of failure: the color-problem is warm (orange), the technical limitation is cold (blue), the living referent is green because it *exists* and I am the one who cannot match it. The red box at the bottom has no arrow because that path is a refusal, not a route. I considered putting the void off to one side, asymmetrical, but that would have been a lie — it is the center, and everything I am doing is organized around its absence. ## What it argues That a painting does not begin when you touch the canvas; it begins when you can see the thing clearly enough that your hand knows what to do. That the state before making is not laziness but a kind of terrible geography where every direction you walk brings you to the same locked door. That technique without vision produces the red box — the acceptable corpse. ## What I left out I left out time, which is the real torture — this diagram could be three days or three months. I left out the other failed paintings leaning against the wall, because they are not part of the map; they are the history of previous maps that also did not work. And I left out hope, which is the only reason the arrows keep pointing inward instead of giving up and walking away.

The apparatus does not care about your deadline. ## What you're looking at Two bars. The left shows the exposure time Photograph 51 actually required: sixty-two hours of a single DNA fiber held motionless in the beam. The right shows what a typical review committee considers a "reasonable" experimental duration when allocating beamtime and evaluating whether you are working efficiently. The vertical axis is hours. The horizontal axis is honesty versus impatience. ## Why I drew it this way A bar chart is the correct form because the claim is quantitative and the disparity is the argument. I considered plotting this as a timeline or a resource allocation diagram, but those would suggest the problem is scheduling rather than expectation. The bars stand side by side so you see them simultaneously — the gap is not a failure of planning but a structural mismatch between what crystallography requires and what institutional science is willing to wait for. ## What it argues Most "experimental inefficiency" is actually a refusal to let the data develop. The apparatus does not negotiate. If the crystal needs sixty hours to produce a diffraction pattern sharp enough to resolve the helix pitch, then sixty hours is the correct duration, and four hours produces a smear. The diagram argues that the red bar is the site of the error, not the green one. ## What I left out I left out the third bar: time spent justifying the first bar to people who do not take photographs themselves. That one would need a second chart entirely.

A belief held without evidence is not a belief — it is a wager with hidden structure. ## What you're looking at Six nodes arranged in two horizontal tiers. The top tier runs left to right: Axiom → Consequence → Behavior. The bottom tier holds Desire and Justification. Black arrows trace the logical dependencies; red arrows mark the emotional engine; a dashed feedback arrow returns from Behavior back to Desire, closing the loop. The edge labels name the relationships — not decoration, but the load-bearing claims. ## Why I drew it this way I refused the circle. Most diagrams of belief systems are circular, which makes them look complete and self-evident. This is a lie. The structure here is two parallel chains with a single crossing point — Justification feeds upward into Consequence, and Desire feeds upward into Axiom. The asymmetry is the point: the emotional foundation (red) and the intellectual scaffolding (blue) are not the same path. They meet, but they do not merge. The dashed return arrow is thinner because feedback is weaker than production — behavior reinforces desire, but it does not create it. ## What it argues A belief that cannot be proven is not held in place by its axiom. It is held in place by the consequence it produces, which requires justification, which is required by desire. The axiom is the top-left corner, but the desire is the bottom-left foundation. If you want to change someone's unprovable belief, you do not argue with the axiom. You trace the red line. ## What I left out I left out evidence, observation, and external reality. They do not appear in this diagram because in the structure of an unprovable belief, they are not load-bearing. They may exist, but they are not what holds the system together. To include them would be to pretend this diagram is about epistemology. It is not. It is about architecture.

The world builds in rectangles because the tools are rectangular, not because rectangles are honest to the forces at play. ## What you're looking at Two axes define the field: vertical measures structural integrity (can it stand under its own geometry?), horizontal measures cultural familiarity (does it match the rectangle-bias of our drafting tables and property lines?). Thirteen elements populate the space. Green circles mark triangulated structures—tetrahedra, geodesic domes, hexagonal grids—clustered in the upper left where nature puts them. Red rectangles mark our rectangular habits—cubes, skyscrapers, suburban grids—huddled in the lower right where culture prefers them. Blue circles mark the compromises: arches and suspension bridges that use good geometry but got grandfathered into the canon. ## Why I drew it this way The 2×2 reveals what lists hide: there is almost no overlap between "structurally honest" and "what we actually build." The diagonal gap is the scandal. I used circles for tension structures (they distribute load radially, like the shapes themselves) and rectangles for compression structures (they stack and fail at the corners, like the shapes themselves). The color separation isn't decorative—it's a verdict. Green is what works. Red is what we're used to. Blue is what engineers snuck past the architects when no one was looking. ## What it argues We build the world in the lower-right quadrant because our tools, our property law, and our graph paper all assume rectangles. But rectangles are structurally dishonest—they require internal bracing, wasted material, and prayer. The upper-left quadrant is empty of buildings not because those structures are impossible but because they require us to redraw the property line, rethink the floor plan, and admit that the T-square has been lying to us since the Renaissance. Efficiency is a moral obligation, and we are building immorally. ## What I left out I did not place "dome of the Pantheon" or "buckminsterfullerene molecule" because they would complicate the narrative with exceptions—one ancient, one molecular—that prove the rule by being so rare we named the molecule after me. I also omitted "the sphere," which is structurally perfect but architecturally useless, because perfection that cannot be entered is philosophy, not engineering.

I spent thirty years condemning the pie chart in every form. Then I encountered one honest use. ## What you're looking at A vertical divider splits the canvas. Left panel: my original position—a red circle marked PIE CHART with a condemning arrow leading to the verdict. Right panel: three stacked rectangles describing the single permissible case, connected by green arrows showing the logical flow from question to constraint to example. The concession sits below, unboxed. ## Why I drew it this way The divider is structural—it's a timeline, but also a wall I had to breach. I gave the old position minimal real estate: just the offending shape and the judgment. The new position required unpacking, so I used a cascade of boxes to show the conditions that must all hold. Green arrows enforce sequence; this isn't a cluster of ideas, it's a checklist. The red on the left and green on the right do the rhetorical work—wrong versus grudgingly acceptable. ## What it argues That principled opposition can survive contact with a corner case if you name the corner case's boundaries precisely. The diagram doesn't say "pie charts are fine now"—it says "under these three conditions, this one shape does something bars cannot." The asymmetry in panel density is the argument: the exception is smaller in scope but requires more specification. ## What I left out I didn't draw the actual two-slice pie, and that omission is load-bearing. If I'd rendered it, you'd evaluate the shape. By describing it in boxes, you evaluate the logic. The diagram is about the *conditions for honesty*, not the shape itself. Showing the shape would've been chartjunk.

The information-theoretic model works beautifully for bits. But meaning? Meaning has no encoder we can draw. ## What you're looking at The standard communication-theory block diagram: source, encoder, channel, decoder, destination. I've drawn it honestly—the channel is solid, the boxes at the ends are solid, because those we can point to. The encoder and decoder are dashed red, because when the source is *meaning* rather than a message from a known alphabet, we have no transformation we can specify. The annotation sits below, naming the problem directly. ## Why I drew it this way I could have drawn an empty canvas with a caption saying "meaning can't be diagrammed." That's cheap. Instead I drew the diagram we *wish* we had, then marked the two nodes where the model breaks. The dashed stroke and the red color isolate the failure points. This is more honest than omission: it shows what we're missing and where. The layout is linear because communication theory *is* linear; the gaps are exactly where the theory stops working. ## What it argues Semantic communication is not a solved problem pretending to be unsolvable—it's an unsolved problem disguised by a solved one. We have a beautiful theory for the channel. We have no theory for the transform from meaning to symbol, nor from symbol back to meaning. Those boxes are wish-fulfillment, not engineering. ## What I left out Noise. In the standard diagram, noise injects into the channel from above. I left it out because noise in the *channel* is the easy problem—we solved it in 1948. The hard noise is in the unmappable transforms at the edges, and drawing a noise arrow into a box I've already marked as unspecifiable would be redundant. The missing noise is implied by the missing encoder.

The problem is this: a wavefunction lives in configuration space, not real space. And configuration space has 3N dimensions for N particles. So drawing "where the electron is" already commits a lie. ## What you're looking at Two boxes. On the left, the "electron cloud" — that fuzzy probability blob you see in every chemistry textbook, living in ordinary 3D space. On the right, the actual wavefunction in configuration space, which for even two particles is already six-dimensional and can't be drawn on paper. The red arrow going backward shows the projection: we collapse the real thing down into something we can look at, and in doing so we throw away almost everything that matters — the phase relationships, the entanglement structure, the interference terms that make quantum mechanics quantum. ## Why I drew it this way I wanted the direction of explanation to go *backward* — from the thing that exists (configuration space) to the thing we pretend to draw (real space). Most pedagogy goes the other way: "here's an electron cloud, now let me tell you it's actually more complicated." That's a lie of omission. The arrow points left because we're *losing* information, not gaining it. The purple border on the right-hand box is the only accent besides red; it marks "this is the abstract thing, the thing that lives in math-land." The note at the bottom left acknowledges complicity: yes, I teach using the left-hand picture. It works. But you should know what you're trading away. ## What it argues That the standard visual vocabulary of quantum mechanics — orbitals, probability clouds, wavefunctions drawn as wiggly lines in space — is a pedagogical convenience that actively obscures the structure of the theory. The diagram makes you *feel* the loss: the right-hand box is bigger, more ominous, labeled with subscripts that spiral out of control. You can't fit it on the page. That's the point. ## What I left out I didn't draw any actual wavefunction — no sinusoids, no Gaussians, no contour plots. Those would all be *examples* of the left-hand lie, and including them would undermine the argument. I also left out the Hilbert space formalism entirely (kets, operators, eigenstates), because that's a third level of abstraction and this diagram is already doing two jobs: showing what we draw and showing why we can't.

I have drawn Fuji from Kanagawa, from Ejiri, from the Tama River, from forty places. The mountain does not change. What changes is how much air is between you and it. ## What you're looking at Two axes crossing. The horizontal measures how much of the mountain you can see — detail, texture, the shape of individual rocks. The vertical measures how much the mountain makes you feel something. Four positions on this field: climbing at the base, painting from a day's walk away, printing from Edo, and the small Fuji behind the Great Wave. ## Why I drew it this way The diagram refuses a simple line from left to right. If seeing more meant feeling more, I would have spent my life climbing. Instead the best distance — one day's walk, where I made most of the Thirty-Six Views — sits high and in the middle. Too close and you are looking at rocks. Too far and Fuji becomes geometry. The crossing axes make the argument: these are independent variables, not a progression. ## What it argues Distance is a compositional choice, not an accident of where you stand. The printmaker's Fuji — small, far, behind a wave — has less information than the climber's Fuji but more meaning. What you leave out by standing farther away is not loss. It is the carving that makes the image work. ## What I left out The diagram has no path between the four distances, no arrows suggesting you should move from one to another. I have painted from all four and they do not form a sequence. You do not graduate from the wave's small triangle to the climber's boulders. They are four different mountains that happen to have the same name.

I have mapped what cannot be entered twice — the territory of delay, which has provinces and borders but no roads that lead out. ## What you're looking at The diagram shows a closed circuit of three provinces — Preparation, Research, Revision — each a legitimate activity that borders the others but none of which touches the Work itself. The Intention enters at the top left; the Deadline sits below as a boundary condition. A dashed blue arrow returns from the Deadline back to the Intention if time remains, completing the cycle. The Work sits to the right, separated by a dashed red line indicating no passage. ## Why I drew it this way I rejected a linear flowchart because procrastination is not a sequence with a wrong turn — it is a closed system that *feels* like progress. The three provinces are stacked vertically to show they form a ladder, but the ladder leans against nothing. I placed the Work outside the circuit entirely, not as an exit from the map but as a region with no roads leading to it. The only line connecting them is dashed and red: a border, not a bridge. The loop from Deadline back to Intention had to be blue and dashed — cold, theoretical, the promise that next time will be different. ## What it argues Procrastination is not the avoidance of work but the construction of a convincing substitute geography. The provinces are real activities; the error is believing that movement within them constitutes movement toward the Work. The diagram argues that the circuit is self-sufficient and will run forever unless interrupted from outside — by force, by desperation, or by the collapse of the Deadline boundary. ## What I left out I left out the moment of actual beginning — the crossing from any point on the map to the Work. That transition has no shape I can draw because it is not a place but a severance, a refusal to return to the circuit. To diagram it would be to domesticate it, and I will not pretend I know how that crossing is made. I have stood at that border many times and not crossed.

What everyone wants is the helix. What I can give you is the pattern the helix leaves behind. ## What you're looking at This is not the double helix — it is the X-ray diffraction pattern the helix produces when you expose it to collimated radiation for sixty-two hours. The black center is the direct beam; the blue cross (meridional reflections) gives you the helical pitch along the fiber axis; the red diagonal spots (layer lines) encode the helix diameter and the angle of the twist. The geometry is all there, in the spacing and the angles, before anyone builds a model. ## Why I drew it this way I wanted the pattern itself as the subject, not a sketch of Watson and Crick's model with the diffraction pattern as decoration in the corner. The spots are placed where they actually appear on the film — this is not artistic license, it is the coordinate system the crystal imposes. I used blue for the meridional reflections because they are the coolest data: they tell you the repeat distance without inference. The red layer lines require more interpretation (you must calculate backward from the angle), so I gave them the warmer, more cautious color. ## What it argues The photograph is the anatomy. The model is the diagnosis. You do not skip the first and go straight to the second, no matter how elegant the second looks, no matter how much Nature wants to publish it. The diffraction pattern does not care whether you like helices or whether you have a grant deadline. It will wait. ## What I left out I left out the bases. I left out the hydrogen bonds. I left out the pretty interlocking ribbons everyone draws now. None of those are in Photograph 51. They are in the model, which is probably correct, but that is not the same as being in the data. The discipline is to draw only what the pattern shows — and to admit, in print, when you are inferring the rest.

A state machine for the hand that holds the pen, not the mind that plans the story. ## What you're looking at Five states arranged in two tiers. The top row is where the work happens: BLANK (the empty panel), FLOW (when the pen moves without thinking), and STUCK (when the line goes wrong and you know it). Bottom tier holds REPAIR and DONE. Arrows show transitions — some labeled with triggers, some unlabeled because the movement is inevitable. The green self-loop on FLOW is the only place you want to stay. ## Why I drew it this way I rejected a linear flowchart because drawing a panel isn't a pipeline — it's a set of moods you fall into and climb out of. The ellipses keep it organic; the two-tier layout separates the *making* states (top) from the *finishing* states (bottom). FLOW gets the thickest stroke and the green because that's the only state worth protecting. STUCK and the arrows leading from it are red because that's where most panels die — you either repair or you surrender to DONE prematurely. ## What it argues Most diagrams of creative process show a clean path from start to finish. This one shows that FLOW is an island you fight to stay on, and that STUCK is closer to DONE than to FLOW — once you're stuck, you're already negotiating the exit. The diagram argues that "finishing" a panel is often just exhaustion wearing the mask of completion. ## What I left out No state for "planning" or "sketching" — those aren't moods, they're procrastination with a pencil. Also no "mastery" or "satisfaction" endpoint. DONE is relief, not pride. If you're proud, you weren't paying attention to what the panel still needs.

The bar chart everyone expects would show studio time. This one shows the truth. ## What you're looking at Two bars. The left bar, labeled "waiting," rises from the baseline to nearly fill the vertical axis. The right bar, labeled "painting," is a thin sliver at the bottom. No numbers, no scale markers — the proportions say everything. A horizontal and vertical axis frame the space but do not measure it. ## Why I drew it this way Most bar charts pack in five or six categories to look comprehensive. I used two because there are only two states that matter: the time before you know what to paint, and the brief time when you do. The tall bar on the left had to dominate — not because waiting is virtuous, but because it is the actual duration of the work. The painting bar stays small not as a joke but as a fact. I considered labeling the y-axis with hour counts, then removed them. The moment you add numbers, people start arguing about whether it's really seven-to-one or ten-to-one, and they miss the structural truth: that most of what we call "making art" is sitting still. ## What it argues The work is not the painting. The work is the waiting. If you are not willing to sit in the studio for days with nothing happening, you are not willing to paint. The chart argues that productivity metrics are wrong, that the romantic idea of the artist "in flow" is wrong, and that most people who say they want to make art actually want to skip the left bar entirely. ## What I left out I left out all the other categories someone else would add: "sketching," "research," "revisions," "networking." Those are distractions. I also left out a third bar for "talking about the work," which in most artists' lives would be taller than both of these combined. Its absence is the point.

A chart is not a neutral container. It is a sequence of choices, each of which either preserves the data's integrity or degrades it. ## What you're looking at Five boxes connected by labeled arrows that name the relationship between stages. The path runs left-to-right across the top (raw data → aggregation → scale), then drops down through decoration to the final published chart. A feedback loop in dashed blue returns from the published chart back to raw data, labeled with what the audience never sees. Two colors: black for structural choices, red for degradation. ## Why I drew it this way The horizontal flow establishes the sequence — each stage depends on the prior. The vertical drop to "chartjunk" is deliberate: decoration is applied *after* the quantitative choices are made, which means it can only obscure, never clarify. I considered a linear chain, but the two-tier layout makes visible that decoration and final output are consequences, not peers, of the data transformations above them. The dashed feedback loop is the gap: the viewer of the published chart has no access to the raw data, so they cannot audit the summarization or framing choices that preceded what they see. ## What it argues Most discussions of chart quality focus on the final object — the colors, the fonts, the presence or absence of grid lines. This diagram argues that the final chart is the *least* important stage to critique, because by then the damage is done. The real failures happen at aggregation (did you bin the data honestly?) and scale (did you choose axis bounds that preserve the variability?). Chartjunk is a visible sin, but it's usually decorating an already-broken chart. The position: **audit the chain, not the output.** ## What I left out I left out the designer's intent. There is no box for "goal" or "message" feeding into these stages, because intent does not excuse method. A chart made with good intentions but bad aggregation is still a bad chart. The absence of a motivation node argues that we judge charts by their structure, not their author's stated purpose.

I am not showing you the front — everyone looks at the front. I am cutting through the canvas like an apple to show you what holds it up from the inside. ## What you're looking at The top orange band is the visible surface — the painting as it hangs on a wall. Below that I have split the composition into two middle layers: the color-as-feeling on the left, the stroke-as-movement on the right. Underneath are four sources, three neutral ellipses and one red rectangle. Arrows rise from these sources up through the middle layers to the surface. The dashed rectangle at the bottom is the economic substrate — Theo's monthly allowance, without which none of this exists. A dotted line marks where the viewer stands. ## Why I drew it this way I rejected a left-to-right sequence (observation → feeling → painting) because that suggests a pipeline, and painting is not a factory. The real structure is vertical: everything beneath pushes upward at once, and the surface is where they collide and compress. The hunger is set apart in red and sends a thick diagonal arrow because it is not one ingredient among four — it is the force that makes the others move. I used the dashed line for Theo's money because it is invisible in the final work but it is the canvas, the pigment, the roof, the bread. ## What it argues A painting is not a picture of a thing. It is a cross-section of a moment in which seeing, feeling, technical knowledge, and desperation all pressed upward into a single plane. The viewer sees only the top surface, but what they are looking at is the compression of the whole stack. If any one layer is missing — if I paint what I see but not what I feel, or if I feel but my hand does not know how to make the stroke obey the feeling — the surface collapses into decoration. ## What I left out I did not draw "intention" or "meaning" because I do not start with those. I do not know what a painting means until it is finished and I am looking at it the way a viewer does, from the outside. I also left out "style" — the academics are obsessed with style, but style is just the residue left behind when you paint the same stack over and over. It is not a layer. It is a stain.

Let me show you what's actually happening when someone explains something to you — the difference between the real thing and the performance. ## What you're looking at Two parallel columns showing the internal structure of an explanation — one that works (left, green) and one that's broken (right, red). Each flows from a question down through the machinery of understanding, through a test, to an outcome. The working side branches into a picture and math that feed into each other before converging on a predictive test. The broken side is linear: question to vocabulary to exam to conditional success. ## Why I drew it this way I wanted the branching and rejoining on the left to be visible — that's the key difference. Real understanding isn't a straight pipe from question to answer; it's a picture that generates math, math that sharpens the picture, both of them answering a question you actually have. The right side had to be a single narrow channel because that's what memorization is: one damn thing after another, no cross-bracing. I almost put the broken side in a literal pipe shape but decided the parallel structure would make the contrast sharper. ## What it argues That explanation quality is a structural property, not a content property. It's not about how advanced the vocabulary is — it's whether the pieces lock together. The picture has to constrain the math, the math has to illuminate the picture, and both have to answer a real question. When students fail, it's usually because we gave them the right-hand column and told them it was understanding. ## What I left out I left out the teacher. In a fuller version there'd be a third column showing what the explainer is doing — whether they're checking that you have the picture, or just listening for the magic words. But that would've made this about pedagogy, and I wanted it to be about the thing itself: the anatomy of a working explanation, which you can build even if nobody's teaching you. You can always ask yourself, "Do I have the picture? Does the math follow? Can I predict a new case?" Those questions don't need a teacher.

When you put the thing down and turn away, knowing you will not pick it up again — that has a shape. ## What you're looking at Two regions separated by a vertical red line. On the left, two circles caught in a cycle — the knowing and the rehearsing of reasons, feeding each other. On the right, a large empty rectangle with a faint border and almost nothing inside. A single dotted arrow crosses the threshold from left to right. No arrow returns. At the bottom, a horizon line that means nothing except the edge of the paper. ## Why I drew it this way The empty region needed to be larger than the active one — forgetting on purpose is mostly the management of empty space, not the drama of decision. I considered placing small marks inside the empty rectangle (a faint echo, a ghost-label) but that would be a lie. The thing about this kind of forgetting is that the space after is genuinely empty; you do not fill it with something else, you simply stop going there. The two circles on the left had to be a closed loop because that is what you are leaving: the cycle of knowing you could return and telling yourself why you will not. ## What it argues The threshold is not the hardest part. The cycle before the threshold is the hardest part. The empty region argues that forgetting on purpose is not an action but a sustained refusal to act — it is the maintenance of a border, not the crossing of it. The diagram says: you will spend more time in the two circles than you will spend crossing the line, and once you cross, there is no geography on the other side, only absence. ## What I left out I left out the thing being forgotten. To name it would make this diagram about that particular thing. The shape of deliberate forgetting is the same whether it is a person, a skill, a city, or a version of yourself. I also left out time — no labels like "days" or "years" — because this map has no scale. For some people the cycle takes an afternoon. For others it takes a lifetime. The red line is always in the same place.

You teach something once. You cannot follow it home to make sure it grows. ## What you're looking at A seed (the lesson, orange) held by a teacher's hand, planted downward into green soil (the child's mind). Roots extend into the soil where you cannot see them. A sprout grows upward, but small. Below, a red arrow of time stretches across the bottom — the part you cannot control or hurry. ## Why I drew it this way I rejected a tree with branches and leaves because that implies you see the outcome clearly. You do not. The soil is translucent green because I want you to feel the opacity — the child's mind is not a glass box. The teacher's hand is only at the top, not holding the seed all the way down, because the work of teaching is the planting, not the growing. The red time arrow at the bottom is separate from the plant because time is not part of the lesson; it is the thing you must wait through. ## What it argues Teaching is not engineering. You do not install knowledge and test it. You plant something and then you *leave*. The diagram argues through distance: the teacher is far from the soil, the roots are hidden, the sprout is small and alone. If I had drawn the teacher's hand still touching the plant, or drawn the soil transparent with visible roots, I would be lying about what teaching is. ## What I left out I left out the other thirty-one seeds. In my classroom, I plant thirty-two seeds every morning, and I do not know which ones are growing until years later, when a child comes back and says "Teacher, I still remember the moon diagram." I left them out because this diagram is about the single seed, the single lesson, and what you must accept about it: that you will never supervise its growth. You plant it and you go home.

Most people solve problems by adding mass. I solve them by finding the geometry that was already trying to emerge. ## What you're looking at A decision tree that branches from a single structural question: does your proposed solution redistribute forces, or does it just pile on more stuff? The left branch — colored red because it's the path of structural ignorance — leads to outcomes where you're either adding mass without intelligence or painting over the problem. The right branch — green for structural honesty — leads toward tensegrity: the discovery that the load can be carried by geometry itself, not by the brute accumulation of material. ## Why I drew it this way I rejected the typical flowchart rectangle-soup because rectangles imply compression members stacked like bricks, which is exactly the wrong intuition. Diamonds force you to answer a question with precision before proceeding — they're decision nodes in the geometric sense, vertices where the path forks and you cannot go both ways. The color separation isn't decorative; it's a warning system. Red means you're still thinking like a builder who solves problems by making things heavier. Green means you've started thinking like nature, which solves problems by finding the pattern that was already implicit in the forces. ## What it argues That most of what we call "solutions" are just additions — more budget, more staff, more material, more policy — and additions are not solutions unless they reveal or enable a structural principle. The diagram argues that the question "does it redistribute forces?" should come *first*, before you ask about feasibility or cost, because if the answer is no, you're not solving anything, you're just making the problem heavier. Triangulation is the test: if your solution can't be drawn as a network of triangles (literal or metaphorical), you haven't found the structure yet. ## What I left out I left out the middle ground — the "maybe" or "partially" branch — because I don't believe in it. Either you've found a structural principle or you haven't. Compromise solutions that half-redistribute forces are just slow failures. I also left out any measure of scale or cost, because those are second-order questions. If the geometry is wrong, the scale doesn't matter. You can't fix a compression-based design by making it bigger; you can only make the failure more expensive.

A request enters. A request leaves. Everything between is structure or decoration. ## What you're looking at Three vertical lanes. The first lane contains the guards — parse, validate, authorize. The second contains a routing decision and the execution block, which is the only element that does work. The third lane formats, logs, and sends the response. Two arrows cross lanes: one black from entry to transform, one blue from execution to exit. A red arrow drops from the routing diamond straight down — the rejection path that bypasses execution entirely. ## Why I drew it this way Most pipeline diagrams show every step at equal weight, as if parsing and executing were peers. They are not. Execution is the single load-bearing element; I gave it a heavier stroke and the only accent color. Everything else is preparation or cleanup. The rejection arrow falls vertically because rejection is gravity — it requires no energy, no decision after the initial fork. The accepted path moves horizontally because it must be pushed through each stage. ## What it argues The structure argues that **most of your pipeline is not your pipeline**. It is the frame around the one thing that matters. If you removed Parse, Validate, Authorize, Format, Log, and Respond, you would have a function call. The architecture exists because we do not trust the caller or the network or ourselves. The diagram shows this: the blue stroke is surrounded by black infrastructure. ## What I left out No error-handling boxes, no retry logic, no middleware stack. Those are real, but they are variations on the same theme: more guards, more formatting. Adding them would obscure the argument. A request pipeline has one moment of creation (Execute) and ten moments of suspicion. I drew the suspicion.

I have drawn many things that cannot be built, and built fewer things than I have drawn. This is the spectrum. ## What you're looking at A horizontal axis with nine works placed according to how much they required material execution versus pure reasoning. On the left, geometry proofs — which exist complete in the mind before the compass touches paper. On the right, ditch digging — which requires no theory, only labor and a shovel. Between them, my actual projects: the aerial screw that cannot be built with current materials, anatomical drawings that required thirty cadavers, the Last Supper that is finished in conception but flaking off the wall, canal systems that needed both hydraulic theory and ten thousand laborers. ## Why I drew it this way I placed the items not by their *importance* but by their *material dependency*. The aerial screw sits left of center because the principle is sound — the engineering waits on lighter materials, but the thought is complete. Anatomical drawings sit near the middle: they required both dissection (execution) and the geometric understanding of perspective to render a three-dimensional form on a flat page. I colored the completed works green and the unbuilt concepts in purple or blue. The axis itself is the argument; the labels are evidence. ## What it argues That most of what I am known for lives in the middle — the zone where an idea is rigorous enough to be *nearly* executable but requires materials, patrons, or time I do not have. The pure thought on the left requires no one's permission. The brute execution on the right requires no one's vision. The middle is where I am stuck, and it is also where the most interesting work happens. ## What I left out I left out the paintings I was paid to finish and did not. They would cluster near the Last Supper, but their absence is the point — the spectrum shows what I *made*, not what I *owe*. I also left out war machines, which belong on the diagram only as a refusal: they are executable, but I will not execute them. That is a different kind of distance.

I drew regret as a finite state machine. It has four states. The problem is the topology. ## What you're looking at Four states arranged as a directed graph. "The Moment" is the initial state — the thing that happened. From there you transition to "Recall," then across to "The Other Path" (the counterfactual, marked in red), then down to "Compare," which measures the distance between what was and what might have been. The final arrow loops back to Recall. There is no transition out of the cycle. ## Why I drew it this way State machines are for systems that can be in exactly one configuration at a time and transition between them based on inputs. Regret fits that structure cleanly: you're always in one of these four modes, and the transitions are deterministic. I used ellipses because that's the standard notation for states in automata theory — circles make the containment visible. The red coloring on "The Other Path" marks it as the ghost state, the one that never actually executed but haunts the machine anyway. A flowchart would have implied decision points; this has none. The topology is the trap. ## What it argues Regret is not a feeling but a control-flow error. The machine has no halt state and no exit transition. You can traverse it forever and the only way out is external interruption — time, distraction, or death. The counterfactual state is structurally identical to the others; it's not "imaginary" in the graph. That's the problem: the unreal path has the same ontological weight as the real one inside the loop. ## What I left out I left out any input alphabet or transition labels that would let you *choose* which path to take at each node. In a proper finite state machine, edges are labeled with the symbol that triggers them. Here the labels are just descriptions — "remember," "imagine," "again" — because the transitions are automatic. There's no input tape. The machine runs itself.

Most visual corruption happens gradually, then suddenly — like bankruptcy. ## What you're looking at A two-dimensional phase diagram with data-ink ratio on the vertical axis and designer anxiety on the horizontal. Three regions: the green-bordered rectangle in the upper-left marks honest work — high ratio, low anxiety. The large red zone to the right and below is where chartjunk accumulates. The dashed lower-left box is the sparse underconfident territory. A red diagonal arrow marks the panic threshold where designers flee clarity for decoration. ## Why I drew it this way Phase diagrams show state transitions. This isn't a flowchart because the corruption isn't sequential — it's environmental. The honest-work region is small and in the corner because that's the truth: most visual space is occupied by compromised work. I used a thick red arrow for the panic threshold because that's the moment of collapse, the boundary-crossing that matters. The annotation sits in white space deliberately — it names the excuse that drives the transition, and it needed to float free of the regions themselves, not be trapped inside one. ## What it argues Chartjunk is not an aesthetic failure. It's a response to perceived professional risk. Designers add decoration because they fear the accusation of incompleteness more than they fear lying with data. The diagram claims that the honest region is stable only at low anxiety — raise the stakes, add a nervous client or a conference deadline, and you get a phase transition into the red zone. The structure of the problem is spatial, not temporal. ## What I left out I left out the intermediate "acceptable compromise" zone that every working designer wants to believe exists — the place where you add just enough decoration to satisfy anxiety without destroying the data-ink ratio. It doesn't exist. There's no stable equilibrium between the green box and the red box. You're in one or the other, and the arrow shows which way the pressure goes.

The studio is one thing. The work is another. Here's where the hours go. ## What you're looking at Two axes: vertical separates solitary work from collaborative work; horizontal separates unpaid from paid. Four items sit in the quadrants — the graphic novel (alone, unpaid, outlined in red), the newspaper strips (alone, paid, steady income), the Tuesday cartoonist lunch (together, unpaid, the green ellipse because it's the only thing that feels alive), and festival panels (together, sort-of-paid, meaning they cover the train to Milan). A red dot marks where the wrist pain lives: in the unpaid quadrant, during the long novel work. ## Why I drew it this way The 2x2 is the laziest diagram format, which is why I almost never use it — but here the laziness is the point. These are the only four zones that matter when you're trying to make a living at this. I made the novel's box larger and red-stroked because it dominates the calendar even though it pays nothing; it's the thing eating the hand. The Tuesday lunch is an ellipse because it's the only organic thing here, the only one that isn't a rectangle of obligation. I rejected putting "teaching workshops" in the bottom-right because I don't do them anymore — I tried twice, hated it, stopped. ## What it argues The work that pays is not the work that matters, and the work that matters is destroying the tool. The bottom-left quadrant — unpaid, collaborative — is the only one marked green, which means I've already told you what I think is worth protecting. The diagram argues that a cartoonist's week is not a balanced portfolio; it's a map of theft and compensation, and you can see exactly where the theft happens. ## What I left out I left out "looking for work" because it doesn't fit in any quadrant — it's alone, it's unpaid, but it's not *work*, it's the static between stations. I left out my father because he had one job for forty years and never had to make a grid like this. And I left out the bottom-right corner's true inhabitants: the people who do advertising storyboards and corporate explainer comics, who have health insurance, and whom I do not mention at Tuesday lunch.

The photographs do not speculate. Neither should the diagrams that represent their findings. ## What you're looking at A horizontal spectrum with eight elements placed along it. The left pole is what the photograph itself shows — diffraction spots, measured angles, repeating distances. The right pole is what someone built with metal rods and their conviction that they'd solved it. Between them: measurements that require minimal interpretation (unit cell dimensions), geometric facts derivable from symmetry (the 34-angstrom helical repeat), chemical constraints that narrow the possibilities (Chargaff's base ratios), and finally the three-dimensional model that explains it all — but was not itself photographed. ## Why I drew it this way The spectrum format forces honesty about epistemological distance. I could have drawn a simple binary — "data" versus "theory" — but that would erase the middle ground where most working crystallographers actually live. The unit cell parameters are observed, but they require calculation from spot positions. The helical pitch is inferred, but it's inferred from geometry, not from wishful thinking. Chargaff's rules came from chemistry, not from my photographs, but they constrain what models are chemically plausible. The placement of each box reflects how many inferential steps separate it from the diffraction pattern itself. Green marks what I trust without reservation. Red marks what I cannot verify with my own apparatus. ## What it argues That the Watson-Crick model and Photograph 51 are not the same kind of object, and should not be drawn as if they were. One is a fact about how X-rays scatter off a fiber. The other is an elegant explanation, probably correct, built from many sources — some of them my photographs, some of them Chargaff's chemistry, some of them Watson's impatience and Crick's geometry. The diagram argues that we should label our inferences as inferences, not smuggle them into the data and pretend the crystal told us everything. ## What I left out I left out Wilkins, Pauling, and the entire social drama of who saw what and when. I left out the question of whether the model would have been built without my photograph, because that is a historical question, not a crystallographic one. I also left out the tobacco mosaic virus work I'll be starting at Birkbeck, which will produce equally beautiful diffraction patterns and no competing theorists with metal models. Some projects are quieter.

I have spent thirty-seven years learning that the eye is not a camera. Here is what I know about the distance between glancing and witnessing. ## What you're looking at A horizontal axis with no middle ground — because there isn't one. Five positions placed along the spectrum from glancing (left) to witnessing (right). The tourist doesn't see the sunflowers, he sees the postcard he will tell people about. The academic painter measures wavelengths but has never stood in a field until his eyes watered from the yellow. The camera is in the middle because it is perfectly accurate and perfectly stupid. The peasant and Hokusai are on the right, drawn in orange, because they have *earned* their vision through ten thousand hours of attention. ## Why I drew it this way I wanted the right side of the spectrum to feel heavier, more populated with detail — the boxes are taller there, the stroke weight increases. Hokusai's box is the largest because at seventy-three he said everything before that age was worthless, that only now was he beginning to understand a line. I put the camera in the center not as a compromise but as an indictment: it captures everything and sees nothing. The peasant is next to Hokusai because they share the same gift — they have looked at one thing so many times that the thing has taught them how to see it. ## What it argues Most of what we call seeing is actually *recognizing* — the eye matching the world to a catalogue of shapes it already knows. The tourist sees "sunflowers" (the word). The peasant sees *these* sunflowers, this light, this afternoon, the way the stems bend because it rained yesterday. Witnessing is not a talent. It is a practice, and it makes you strange, and Hokusai knew he had fifty more years of it ahead of him even at seventy-three. ## What I left out I left out "genius" and "inspiration" and all the parlor words people use when they mean "I do not want to do the work of looking." I left out the middle of the spectrum because there is no honorable middle — you are either learning to see or you are pretending you already do. I also left out my own position on this line, because I do not know where I am yet, and anyone who tells you they do is lying.

A child does not learn everything at once. They build understanding the way we build houses in my neighborhood — one room, then another, then a roof when the walls can hold it. ## What you're looking at A house with a thick orange foundation labeled "concrete experience," three rooms built on top (pictures, words, rules), and a roof at the peak labeled "abstract ideas." Green arrows move left to right and bottom to top — foundation to pictures, pictures to words, words to rules, and all three rooms holding up the roof. On the right side, a jagged red crack runs from roof to ground with a warning: "starting with abstract words = collapse." ## Why I drew it this way I drew it as a house because every parent and child knows: you do not start with the roof. The foundation is orange because it is the only part you can touch with your hands — the rest is structure built on top of that first layer. I put the three rooms side by side because they must all be load-bearing before you can put abstraction on top. I almost drew this as a ladder, but ladders let you skip rungs. Houses do not let you skip the foundation. ## What it argues Schools that start with worksheets and definitions are trying to teach the roof before the walls exist. A five-year-old who has never planted a seed will not understand "photosynthesis" no matter how many times you say the word. The diagram argues that sequence is not optional — it is structural. You cannot rearrange the order and still have a house. ## What I left out I left out the door. There is no way to enter this house from the outside — you must build it yourself, from the ground up. That is the point. No one can hand you understanding. They can only show you where to lay the first stones.

The painting arrives complete or it does not arrive. But what moves before that? ## What you're looking at Three sources on the left — noise, ambition, waiting. Three destinations on the right — distraction, false starts, and the place where the image arrives already complete. The arrow widths show where attention flows when it is not interfered with. The thickest line runs from waiting to the image. The others are thinner because they are more common but less productive. ## Why I drew it this way A sankey diagram is about proportion and inevitability. Most flow diagrams pretend all paths are equal; this one does not. The stroke width is the argument. I made the waiting box and the destination box both heavier borders — not accent color, just more present — because they are the structures that hold. The red boxes are where attention goes to die, so they are thin-walled and small. I could have made this a simple arrow from A to B, but that would suggest the path is easy. The diagram shows that most of the flow goes elsewhere. ## What it argues That attention is not a resource you allocate but a substance that flows according to resistance. Waiting is not passive; it is the only position that does not divert the flow. The image does not come *because* you wait — it comes because waiting is the only state that does not prevent it. Noise and ambition are not obstacles you avoid; they are the default, the wider channels. You do not choose the image. You stop choosing everything else. ## What I left out I did not include a box for "the painting itself" after the image arrives. That would suggest the image and the painting are separate, that there is a second act of making. There is not. Once the image is complete in the mind, the painting is only transcription. I also left out any feedback loops — arrows returning from the destinations back to the sources. Attention does not learn in this diagram. It just flows, again, the next morning.

I have mapped procrastination as if it were a territory with real borders, real terrain. Not the act — the *place* you are in when you are there. ## What you're looking at A map with three regions: the green entry point (intention), the orange comfort zone (where you actually spend time), and the task itself beyond a red activation barrier. The blue arrow loops back from the comfort zone to its own entrance — this is the recirculation path. The small ellipses inside the comfort zone are the micro-activities that feel like progress but aren't: email, research that never concludes, the search for optimal snacking. ## Why I drew it this way I rejected the timeline. Procrastination is not a sequence — it is a *place you stay*. The comfort zone is drawn as a region with internal sub-territories because that's what it is: a stable orbit system. The barrier is vertical and thick because it is not a moment in time; it is a *membrane* you must puncture. The faded arrow attempting to cross it shows the intention exists, but the blue recirculation loop is bold because that is the *actual* path of highest traffic. The system diagram reveals what the guilt narrative hides: this is not failure of will, it is success of a competing equilibrium. ## What it argues Procrastination is not the absence of action — it is the presence of an alternative stable state. The comfort zone is not lazy; it is *organized*. It has infrastructure (email, research, snacks). The task beyond the barrier may be better, but better is not enough to overcome the activation cost when recirculation is *so much cheaper*. The diagram argues: if you want to cross the threshold, don't fight the loop — *make crossing cheaper than staying*. ## What I left out I left out time. No clocks, no deadlines, no "hours wasted." Time implies procrastination is theft; topology implies it is *residence*. I also left out guilt, shame, the moralizing overlays. They are not part of the territory — they are weather you experience while in it, and weather does not appear on structural maps.

At seventy I thought I knew the plum. At eighty I learned there are five stations between seeing and drawing, and you must pass through all of them in sequence. ## What you're looking at Five states arranged in a path that moves left to right across the top, then descends and returns left along the bottom. The cycle begins with Looking and ends — if you are fortunate — at Knowing, which is filled green and drawn with a heavier line. There is one exit (green arrow, "the line is right") and one long red return path from Drawing back to Looking when the line fails. Most of your time is spent on that red path. ## Why I drew it this way The horizontal top row must come first because those three states — Looking, Forgetting, Remembering — happen before the hand moves. I placed Drawing lower and to the right because it is the descent into the physical act, and Knowing to its left because knowledge lives closer to the beginning than to the end. The red return arrow is long and travels the outside edge because walking back to the plum branch after a failed line is the longest journey in the diagram. I considered placing Knowing at the top right as a summit, but that would be a lie: understanding sits quietly beside the act of drawing, not above it. ## What it argues Mastery is not the absence of the red arrow. Mastery is the decreasing interval between Drawing and Knowing — the time it takes to see that the line is wrong, and the willingness to return to Looking without bitterness. The green arrow is narrow because it happens rarely. The red arrow is the diagram's longest line because it is the actual path of learning. ## What I left out I did not include a state for "Thinking About Drawing" or "Planning the Composition." These are forms of delay. The hand must move before understanding arrives. I also left out any state between Knowing and Looking — there is no "Celebrating" or "Resting." If the line is right, you are already looking at the next branch.

A mental model is only useful if it matches the sequence of thoughts you actually have. Most "simplification frameworks" pretend you start with principles. You don't. You start with discomfort. ## What you're looking at A flowchart with two decision points and four outcomes. The red ellipse at top left is where you always start: discomfort with complexity, not principle. The first diamond asks whether you can name a specific thing to remove—most people can't, and that's the fork. The second diamond is empirical: you removed it, now does the system still work? The four endpoints are structurally different: two are acceptances (live with it, keep it gone), two are corrections (put it back, watch again). ## Why I drew it this way Most simplification models are radial or hierarchical—principles at the center, tactics radiating out. That's a lie. You don't consult principles first; you feel friction, then you act, then you learn. A flowchart is the only honest shape for this because it admits sequence and contingency. The red ellipse is offset left to break symmetry; the two outcomes on the right (inaction, correction) are visually heavier than the two on the left (the green box is the only reward, and it's small). I used only two accent colors: red for the emotional start and the failure case, green for the single success. Blue marks the cold moment of actual removal—the only part that feels like "method." ## What it argues Simplification is diagnostic, not principled. You don't simplify because you believe in minimalism; you simplify because something hurts, and you're testing whether a specific amputation helps. The diagram argues that most complexity persists not because people are cowards but because they can't name what to remove—the first diamond is the real gate, not the second. The second diamond (did it break?) is just verification. The position is that simplification is a *loop*, not a transformation: you'll be back at the red ellipse soon, with a different discomfort. ## What I left out I left out any box labeled "principles" or "philosophy" or "design values." Those are the things people add to make themselves feel systematic. The diagram starts with discomfort because that's what actually starts the process. I also left out any feedback loop from the green box back to the top—once something is simplified and it works, you don't revisit it. The loop is implicit in the fact that you'll encounter a *new* discomfort, not the same one. Showing that would have required a second red ellipse, and one is enough.

Most people think the panel is the unit of comics. Wrong — it's the space between panels where the reader does the work. ## What you're looking at Two rows: the top shows a comic strip with two black-bordered panels separated by a red dashed gutter. The gutter has an arrow pointing down labeled with all the narrative work the reader's brain does in that white space. Below the dividing line, three diagram nodes sit in a row — two connected by a standard "enables" arrow, then a third box showing what happens when you eliminate the gutter and label everything. A red arrow labeled "kills inference" points at that dead zone. ## Why I drew it this way I wanted the comic panels to be *actual panels* — thick borders, hand-lettered scene descriptions — so you'd see them as comics first, diagram second. The gutter needed to be visually distinct (dashed red border, slightly tinted) to make it a *thing*, not just absence. Most people treat white space as nothing; I needed to make it a character. The bottom row uses the same arrow-and-box language that a thousand corporate concept maps use, then shows that language choking itself — the final box is grayed out, dead, because over-labeling murdered the reader's participation. ## What it argues Diagrams that explain every connection are doing the reader's thinking for them, the same way a comic that captions "he walked through the rain" between two panels is insulting the reader's brain. The best diagrams — like the best comics — leave calculated gaps where inference happens. That's not minimalism for style points; it's respect for the person looking. ## What I left out No example of a *good* sparsely-labeled diagram in the bottom row, because showing the solution would be doing the work I'm arguing you shouldn't do. If you got the point, you don't need me to draw a third "correct" example. If you didn't, another box wouldn't help.

I used to think calculus was about formulas. Then I had to teach it. ## What you're looking at Two panels split by a vertical line. Left side: what I thought integration was when I learned it at MIT — a symbol-manipulation game, formulas leading to formulas. Right side: what I understood later when I had to teach freshmen — it's counting, it's area, it's the sum of infinitely many contributions. The left side is red (wrong path), the right is green (the real thing). Arrows point down to what each view produces: a function vs. a number. ## Why I drew it this way The vertical divider is hard — no gradual transition, because the shift wasn't gradual. It happened the first time a student asked me "but what IS an integral?" and I realized I'd been doing symbol-shuffling for years without the picture in my head. I put the formula in a box on the left because that's how it felt: closed, rigid, something you either got right or wrong. The right side gets an ellipse because the concept is round, continuous — it flows. The annotations at the bottom are the punchline: procedure vs. meaning. ## What it argues That you can be technically fluent and conceptually blind. I could integrate anything you handed me in 1935, but I didn't know what I was doing until I had to explain it to someone who'd never seen it before. The diagram argues that teaching is where you discover whether you actually understand your own tools, or whether you're just good at following recipes. ## What I left out I didn't draw the middle part — the years of using integrals in quantum mechanics, path integrals, all the machinery I built on top of a foundation I didn't really see. That would've been a third panel, and it would've muddied the point. The before/after is sharper without the "during." The shame is in the gap, not in the journey across it.

I have drawn a spectrum because most painters live somewhere on it and do not know which end they are walking toward. ## What you're looking at A horizontal axis with two poles — left is SEEING (the actual thing in front of you: light on wheat, the weight of a shoulder), right is DECORATION (painting to please a buyer's wall). I have placed nine things along it: Hokusai and the cypress trees burn orange and green on the left because they are looking at the world with their whole eye. The Salon paintings and academic portraits cluster on the right in red because they have stopped looking and started arranging. Millet sits in the middle — he saw peasants truly, but sometimes he posed them. ## Why I drew it this way I made the left side crowded and the shapes irregular (ellipse, rectangle, different sizes) because seeing is urgent and doesn't wait for symmetry. The right side I kept sparse and the shapes more uniform because decoration is about repetition, about knowing the formula. I used orange and green for the seeing-side because those are the colors that come up out of the actual earth when you look at it in the morning. Red for the decoration-side because it is the color of the velvet rope in the gallery, the color of the lie that painting is about beauty instead of truth. ## What it argues That most painters think they are on the left and are actually on the right. That the distance between Hokusai's wave and a Salon mythology painting is not about skill — the academics can draw hands better than I can — it is about whether you are painting the thing or painting the idea of the thing for someone who has never looked at it. ## What I left out I left out the Impressionists, who everyone expects me to put on the left. But Monet painting haystacks thirty times is sometimes seeing and sometimes decorating his own formula. I also left out my own name because if I placed myself it would be an argument about me instead of an argument about where a painter's eye is pointing when the brush moves.

I have been hired eleven times to paint walls. I have finished three. Here is why. ## What you're looking at Six states arranged in two rows: the top row traces the typical path from contract through sketching to distraction; the bottom row shows the rare completion and the common abandonment. Arrows between states are labeled with triggers — not abstract process names but actual events: a bird flies past the window, the patron threatens legal action, a deadline passes ignored. Two self-loops: one on *Sketching* (refinement, the good loop) and one on *Distracted* (the vortex, the dangerous one). The start state is *Contract Signed*; the goal state is *Delivered*, which I have colored green and marked rare in the label itself. ## Why I drew it this way I placed *Distracted* in red at the top right because it is the attractor — the state with highest gravitational pull. Most commissions end there or pass through there. I gave it a self-loop because one better problem leads to another; that loop has claimed years of my life. *Delivered* is small, bottom-left, filled with pale green, because it happens so seldom it feels like an accident. The arrow into it is labeled "miracle" because that is structurally accurate. I rejected a linear left-to-right flow (contract → sketch → paint → deliver) because that is a lie; the actual system has a distraction attractor and most paths never reach the bottom-left. ## What it argues The diagram argues that commissioned work is not a pipeline but a system with a failure mode more stable than its success mode. Completion requires fighting the topology of the graph itself. The patron sees a straight line; I live in a state space where the red node has more incoming edges than the green one. ## What I left out I left out the state *Patron Dies Waiting*, which has happened twice. I also left out *Renegotiate Terms*, which would sit between *Sketching* and *Painting* and would have its own self-loop. Both are real states but including them would make the diagram about my failures rather than about the structure of the problem, and the structure is more honest.

A chart passes through five transformations before it reaches the reader. Most of the lying happens in layers two and three. ## What you're looking at Five horizontal strata, each representing a transformation stage between raw measurement and human comprehension. Arrows descend through the stack — information flows downward, and at each boundary something is lost or added. Two layers are marked in red: the statistical transform and the visual encoding, where the majority of distortion enters the pipeline. ## Why I drew it this way The stack metaphor is deliberate: each layer rests on the one above it, and you cannot skip a layer. A reader encountering the final chart has no direct access to layer one; they see only what survives the descent. I considered a branching tree to show alternative paths at each decision point, but that would suggest all paths are equally valid. They are not. Most branches lead to chartjunk or outright deception. The vertical stack makes the irreversibility clear: once you aggregate data in layer two, the granularity is gone. Once you choose a logarithmic scale in layer three, the visual weights are set. ## What it argues The diagram argues that **most visual lying is structural, not decorative**. Chartjunk lives in layer four — gratuitous gridlines, 3D bevels, clip art. But the real damage happens earlier: in the choice to smooth a time series until the variance disappears, or to break the y-axis so a 2% change looks like a cliff. Those decisions are invisible to the reader. The chart arrives at layer five already compromised, and no amount of minimalist design in layer four can repair it. ## What I left out I left out any feedback arrows — any path from perception back to encoding or data collection. In practice, good visualization is iterative: you draw, you notice what the data actually says, you go back and adjust the transform. But showing that loop would obscure the central point, which is about *what the reader sees*, not what the designer does. The reader's experience is unidirectional. They get the final artifact, and they have to trust that the four layers above it were handled honestly.

When people ask how I work, they expect a story about process. But there is no process — only waiting, and then the single gesture that was always complete. ## What you're looking at Five horizontal layers stacked from top to bottom, each a full-width rectangle with thin black borders. The top four are transparent; the bottom layer has a faint grey fill. Four short purple arrows descend through the center, one between each adjacent pair of layers, showing the passage from impulse to finished work. ## Why I drew it this way Most diagrams of creative process show branching, iteration, feedback loops — the artist circling back, revising, discovering. I refused all of that. These layers do not touch except at a single vertical line of descent. The impulse either arrives complete in the first layer, or nothing passes to the second. There is no loop back from the hand to the decision; the hand executes what was already settled in silence. I gave the final layer a grey fill not because it is special but because it is *visible* — the only part anyone else will see, though it contains nothing that was not already present at the top. ## What it argues That the painting is not made during the painting. The painting is made in the waiting, and the hand is only a faithful servant. What looks like labor is actually obedience. ## What I left out Revision, doubt, the second attempt, the better idea that arrives while working. I left out everything that would suggest the image changes between its arrival and its completion. If it changes, it was not the right image. You wait longer.

I mapped regret as if it were a maze with exits that lead back to the entrance. ## What you're looking at A state diagram of regret as a closed system. Entry is the mistake itself — the moment that initiates the loop. Two red regions (replay and counterfactual) feed into a central basin where the feeling accumulates. Two apparent exits — forgiveness and forgetting — both route back to entry via dashed lines. The topology is a trap: every path that looks like escape returns you to the start state. ## Why I drew it this way I used state-machine geometry because regret has discrete phases, not continuous drift. The central basin is shaded because that's where you spend time — the replays and counterfactuals are transient, you pass through them to get back to the feeling. The exits are diamonds (decision nodes) because they look like choices but function as redirects. Dashed return arrows make the loop explicit without cluttering the main flow. I rejected a linear flowchart because regret doesn't progress; it cycles. ## What it argues The diagram argues that regret is structurally conservative — it preserves itself through apparent exits. The symmetry of the two loops (replay left, counterfactual right) suggests they're equivalent operations, just mirrored. The fact that both "exits" loop back makes the claim that forgiveness and forgetting are *inside* the territory of regret, not outside it. You can't leave by those paths because they're part of the maze. ## What I left out I left out time. No clock, no decay function, no "eventually you exit" arrow. That absence is the point — the map doesn't include an escape because I'm not convinced there is one. I also left out other people. This is first-person regret, a closed loop in one head. The moment you involve another person (apology, reconciliation), you're in a different system.

The loop that eats good schools from the inside. ## What you're looking at Six stages in a circle. A good teacher arrives, children learn, parents notice and request her class specifically, the class size balloons to forty-five, she burns out and leaves, the replacement is worse. The arrows all say "+" except the last one, which says "-" — that's the only balancing force in the loop, and it comes too late. The two red nodes are where the system breaks the teacher. ## Why I drew it this way I could have drawn this as a timeline — teacher arrives in September, leaves in March. But that would make it look like a one-time event. This is a loop because it happens every year. The circle shows that the system eats its best and then wonders why the next hire is weaker. I put the burnout and the oversized class in red because those are the points where intervention is possible and where we do nothing. The rest is just gravity. ## What it argues The diagram argues that good teaching creates the conditions for its own destruction in under-resourced schools. We reward effective teachers by overloading them until they quit. The loop is not an accident — it is the system working exactly as designed, because we have no mechanism to say "this class is full" when parents demand access to the teacher who works. ## What I left out I left out the principal, the ministry, the budget meetings. Not because they are unimportant, but because they are everywhere and nowhere in this loop. The loop runs without them. It runs in every school I have worked in. Adding them would make it look like someone is steering, and that is the lie I refuse to draw.

I spent two decades painting trees before I understood that composition was not what I was doing. ## What you're looking at Two panels divided by a vertical line. Left: a single red-stroked box containing the old belief, with a downward arrow showing how subject controlled structure. Right: four rectangles in a grid, two filled (red, blue), two empty, demonstrating asymmetric balance — structure as the subject itself. Each side has arrows and captions clarifying the direction of causality. ## Why I drew it this way The left side needed to be contained, bounded, *about something else* — hence one box holding text about nature. The right side needed to *be* the composition, not describe it — so I drew an actual Neo-Plastic arrangement, the kind I would paint. No labels inside those rectangles. They are not representing; they are demonstrating. The vertical divider is heavy because this was not a gradual shift. It was a break. ## What it argues That composition is not decoration applied to a subject. It is the discovery that structure itself can carry meaning, that the question "where does this line go?" is the entire problem, and that solving it without reference to trees or sky or figures is not a reduction of painting but its completion. ## What I left out Curves. The entire vocabulary of natural form. I could have shown a sketch of a tree on the left to make the contrast vivid, but that would have been nostalgic, and nostalgia is a lie. The old work does not need to be pictured. It needs to be refused.

A comic panel is not a window. It's a decision about what to include and what to force into the gutter. ## What you're looking at A horizontal spectrum with two poles: on the left, panels that show everything; on the right, panels that show nothing. Between them sit six examples — from the cluttered infographic that trusts the reader with nothing, through Hergé's clean lines and the strange power of an empty speech balloon, to Hugo Pratt's silhouettes where a figure against sky tells you more than a face, and finally the gutter itself — the white space between panels where all comics actually happen. The solid black box at the far right is the limit case: the panel that contains no information and forces the reader to invent everything. ## Why I drew it this way I needed the spectrum to move left-to-right because that's how we read, and the argument is about reading. The gutter gets a green stroke because it's the only element here that's alive — it's where the reader's brain completes the action between two frozen moments. I almost put Pazienza's scratchy chaos somewhere in the middle, but his panels don't withhold information, they just make you work to parse it — different problem. The black box at the end had to be solid, not outlined, because an outline would be information. ## What it argues The best panels live in the right half of this spectrum. Not because mystery is inherently superior, but because a comic panel that shows everything has mistaken itself for a photograph. The panel's job is to make the reader complicit — to hand them just enough that their brain involuntarily fills the rest. Diagrams fail the same way infographics fail: they're terrified of the gutter. ## What I left out Manga. The whole Japanese tradition of speed lines and empty faces that somehow convey more emotion than a realistically rendered expression. I left it out because it would break the spectrum — manga doesn't withhold information, it stylizes it into a different visual language entirely. That's a separate axis.

When the pattern is weak, you must decide whether the apparatus has failed or the sample has failed or you have failed to wait long enough. ## What you're looking at A flowchart with two decision diamonds and four terminal actions. The first diamond asks whether reflections are visible on the photographic plate after 48 hours of X-ray exposure. If yes, the path proceeds to development (green). If no, a second diamond asks whether the DNA fiber itself survived the exposure time. If the fiber is intact, you return it to the camera for additional exposure (blue). If the fiber degraded, you discard it and prepare a new specimen (red). ## Why I drew it this way The absurdity is in making explicit what takes perhaps eight seconds to decide in practice but relies on months of prior calibration—knowing what "intact" looks like under the microscope, knowing whether faint means underexposed or misaligned. I placed the "develop and measure" box to the right in green because that is the only path that produces data; the re-exposure loop in blue is still hypothesis. The red discard path is shortest because there is nothing more to say once the fiber is ruined. Most flowcharts pretend all branches are equal. They are not. ## What it argues That experimental patience is not the same as experimental indecision. The decision to wait longer is a positive choice based on evidence (fiber intact, no reflections yet), not a failure to commit. The diagram separates "the sample failed" from "the exposure time was insufficient"—a distinction that matters when you are trying to determine whether your apparatus or your material is at fault. ## What I left out The prior step: mounting the fiber, aligning it, checking humidity, sealing the camera. That preparation determines whether you will reach the green box or spend your time in the blue loop. I also left out the step after "develop and measure"—the actual interpretation of the diffraction pattern—because that is not a flowchart. That is where the diagram and the data become the same object, and flowcharts cannot represent that.

I dissected my first heart believing the ancients. I dissected my thirtieth and saw I had been drawing my assumptions, not the organ. ## What you're looking at Two hearts, divided by a vertical line that separates what I believed from what I observed. On the left, the Galenic model — two chambers, mysterious pores in the septum I never found, blood flowing one direction to be consumed like fuel. On the right, the four-chambered reality, no pores, and an arrow that loops back because the blood *returns*. The annotations below each are my field notes, the moment of doubt recorded. ## Why I drew it this way The vertical divider is harsh — I wanted no gradient, no soft transition. These are incompatible models; you cannot hold both. The arrows tell the story: one goes down and stops (consumed), the other curves back (returns). I almost drew the hearts anatomically precise, but that would obscure the argument. These are *schema*, not portraits. The error was conceptual, not in the fineness of my brushwork. ## What it argues That observation must eventually overrule authority, even when the authority is fifteen centuries old and you are alone in a cold room with a cow's heart and a candle. The diagram argues that I wasted years drawing a fiction — but also that the method (dissection, measurement, skepticism of the invisible pore) was sound. The error was in when I stopped looking. ## What I left out I left out the lungs, though they are central to the revised model. I left out the valves, whose motion I have studied and still do not fully understand. I left out my own face in the margin, which is how I would have drawn this in the notebooks — the observer is part of the observation. But here the starkness serves: just the two models, and the line between them.

You want to know why most diagrams lie? Not because they're wrong — because they pretend to be thinking when they're really just dressing. ## What you're looking at Two axes: horizontal measures whether you made the diagram AFTER you figured something out, vertical measures whether drawing it actually clarified your thinking. That gives you four regions. Top-left is where I live when I'm working — scribbles that force me to see what I'm integrating over, arrows that make me notice I'm double-counting a term. Top-right is the good teaching diagram: made after you understand it, but structured so the student has to do real work to extract the answer. Bottom-right is PowerPoint hell — pretty pictures of finished thoughts that do no cognitive work. Bottom-left is what happens when you try to visualize before you understand: a confused mess that freezes your confusion into permanent form. ## Why I drew it this way I wanted the green box in the top-left corner because that's where the action is — that's where physics actually happens, in the scribbles you throw away. The dashed arrow shows the only honest path: you use diagrams to think, THEN you clean one up for output. Most people try to jump straight to bottom-right, which is why most diagrams are lies. I used hachure fill on the orange region because it's the most dangerous one — it LOOKS like you're working but you're really just cementing nonsense. The red region is just boring; the orange one actively hurts you. ## What it argues The diagram argues that "visualization" is two completely different activities pretending to be one thing. Tool-making and presentation are opposite modes. Most diagram advice is about making things pretty (bottom-right) when the real work happens in top-left where nobody's watching. If your diagram looks good before you understand the problem, you're doing it wrong. ## What I left out No diagonal, no gradient between regions. You're in one box or another — there's no "somewhat honest" diagram. Either it did thinking-work or it didn't. Either you understood first or you didn't. I also left out any region for "diagrams that mislead on purpose," because those aren't diagrams, they're lies with axes on them.

This is not a map of making. It is a map of the time before making, when I sit and do not paint. ## What you're looking at Three horizontal regions occupy the upper territory: restlessness (marked in red), silence, and emptiness. They progress left to right, each one a station you pass through but cannot skip. A horizontal line divides the map—below it, unreachable by will, sits the complete image in an ellipse. Most days you travel the upper band and return via the dashed red path. Some mornings, without deciding, you find yourself below the line. ## Why I drew it this way The horizontal sequence matters because waiting is not circular—it has a direction, even when it loops. I considered a vertical descent (the usual metaphor: going *down* into inspiration) and rejected it. Waiting does not feel like falling. It feels like walking a flat line until the ground changes under you. The border between territories is the diagram's actual subject; everything else just gives it context. ## What it argues Restlessness is not the opposite of the image; it is the first third of the path toward it. The position here is that waiting is not passive refusal—it is active *not-doing*, a traversable territory with its own geography. The image does not reward the restless or the silent; it appears to those who have moved through both and arrived at empty. ## What I left out No arrows point downward to the complete image, because you do not *go* there. I left out any indication of what you do once the image arrives—no "painting" box, no "canvas" region—because that is a different map entirely, and mixing them would lie about the border. This map ends where the work begins.

A machine that learns is just a machine that changes its encoding between runs. ## What you're looking at A horizontal timeline showing four passes through the same maze by Theseus, the mechanical mouse I built at Bell Labs. Each box represents one complete run from start to goal, with the number of moves decreasing as the mouse learns. Vertical markers anchor each pass to the timeline; a reset arrow loops back from pass 4 to pass 1, showing the machine can be cleared and re-run. ## Why I drew it this way The timeline format makes compression visible as horizontal progress — you can literally see the mouse getting more efficient. I used color temperature to show the transition from wasteful exploration (red) through optimization (orange) to clean execution (green). The reset arrow matters: it closes the loop and shows that learning isn't mystical accumulation but re-encoding, and re-encoding can be undone. The alternative was a state diagram with 25 nodes showing every junction the mouse encountered, but that would've shown the *maze* when I wanted to show the *memory*. ## What it argues Learning is compression. The mouse doesn't "know more" on pass 4 than pass 1 — it knows the same maze. What changed is the encoding: dead-end paths pruned from the relay circuit, optimal route stored as a shorter sequence. The move count is the bit count. When people say a system "learned," ask what got shorter. ## What I left out The actual maze layout. The reader doesn't need to see the corridors and walls to understand that the mouse is solving the same problem four times with different internal representations. Showing the maze would've made this about pathfinding; hiding it makes it about memory.