This is a submission for the 2026 WeCoded Challenge: Echoes of Experience
It Was Never A Competition
My grandfather loved chess and mathematics. My mother wanted to be a librarian and became a programmer instead. I grew up loving books and ended up writing code. None of us discussed any of this with each other — it just happened, across three generations, quietly and without coordination. I only understood the pattern much later, looking backwards.
If you'd rather read the whole thing as one scrolling experience, the full version is here — same visuals, one page.
A factory, and what came after it
My grandparents spent their working lives in a factory. That was simply the reality of where and when they were born — it asked a certain kind of life from them, and they gave it. What they were quietly doing alongside that, though, was creating conditions they themselves never had. More room. More options. More space for the generation after them to make different choices.
My grandfather loved mathematics the way some people love music — for reasons that had nothing to do with usefulness or career. He played chess. He worked through problems he found interesting. None of this was a performance. It was just what he did in the hours that belonged to him, and he never suggested it shouldn't also belong to anyone else in the family.
The librarian who ended up writing code
My mother graduated in programming in the early 1980s. I want to be careful not to make this sound more heroic than it was — she wasn't charging barricades. She was a person who was good at thinking precisely, and the path in front of her happened to lead toward computers, and she took it.
What she actually wanted to be was a librarian. She has always been a reader in the deep, committed sense — the kind where books aren't entertainment but something closer to oxygen. She read constantly through her working life and still does. What I've come to understand is that the apparent gap between "librarian" and "programmer" is narrower than it looks. Both involve organising information into systems that hold meaning. Both reward a particular kind of patience with complexity. She wasn't moving away from something she loved when she went into programming — she was working in adjacent territory, with a different set of tools.
The part I didn't notice until later
I started loving books before I started writing code, and for a long time I thought of those as separate things — the reading life and the technical life. It took years to notice that what I was doing in both cases was the same: looking for the logic underneath the surface, trying to understand how a system worked by sitting with it long enough.
I became a programmer without making a decision about it. It felt like a natural extension of how I already thought, and nobody had suggested it should feel otherwise. The recognition came later — that my grandfather's quiet love of patterns had handed me something, that my mother's ease with both books and systems had shaped what felt natural to me, that what looked like my own independent path was also, in some sense, a continuation of theirs. Not because they planned it, but because they never installed the assumption that it couldn't be.
A pause
There's a particular kind of inheritance that doesn't announce itself. It isn't wisdom passed down in conversation or values explained at a dinner table. It's more like a disposition — a way of being curious, a comfort with difficulty, a sense that understanding how something works is worth the effort for its own sake. I absorbed this without knowing I was absorbing it, and the people who gave it to me didn't know they were giving it either.
What connected them
The interesting thing, when I look at all three of us, is that none of it was strategic. My grandparents weren't building a legacy. My mother wasn't making a point. I wasn't following in anyone's footsteps. We were all just doing what interested us, in the circumstances we had, with the time available to us.
What made that possible — what made it feel ordinary rather than remarkable — was the absence of a particular kind of friction. The assumption that certain kinds of thinking belong to certain kinds of people was simply never installed in my family. Not because they were especially enlightened, but because nobody had thought to put it there.
What I think equity actually looks like
I grew up in a house where the question of whether someone like me might be good at abstract thinking simply never came up. It wasn't answered in my favour — it was never asked at all. My grandfather handed me a chess problem. My mother went to work. I followed what I found interesting.
That absence of a question is worth something. It's worth noticing, and worth trying to replicate — not just through policy and pipelines, but in the smaller daily texture of how we talk to people, what we assume about them, and which questions we never think to ask.
How this was built
Everything here is vanilla HTML, CSS, and JavaScript — no framework, no build step, no dependencies beyond two Google Fonts. Each section is a standalone CodePen that works independently; the full piece also lives as a single scrolling page.
The design uses Unbounded at 900 weight for headlines and JetBrains Mono for body text, with a deliberately loud colour palette. The chess board and terminal are rendered in JavaScript. The book stack is the actual reading list. Illustrations are from Cosmos.so, credited inline.
For my mother, who read on her lunch break and never thought it was worth mentioning.
Top comments (0)