PART 18:

“Someone does something the same way enough times that it becomes the right way. Then someone else comes along and tries to understand why it’s right.” Patricia looked at the shelf with the notebooks. They were down to eye level now. He’d moved them sometime in the second week after the G9 and hadn’t moved them back. She’d noticed them on her first visit and hadn’t asked.

Now she said, “Can I look at one?” He took down the third notebook, not the first, which still felt too personal, but the third, which covered a period of James Walker’s career when he’d been working on increasingly complex systems and the entries were richer and more analytical than the early ones. Patricia sat at the bench and read slowly, turning pages with the careful attention she brought to documents she was actually studying rather than skimming.

Ethan worked on a component at the other end of the bench and let her read. After 20 minutes, she closed the notebook and looked at the cover for a moment. “He was extraordinary,” she said. “I know,” Ethan said. “Not just technically, the way he explains things, the way he builds an explanation from the ground up every time, even when he’s covering something he’s clearly covered before.

” She tapped the cover lightly. “He wrote as though he was teaching someone, even when he was just recording for himself.” “He always said that if you can’t explain it to someone who doesn’t know it, you don’t actually know it,” Ethan said. “Writing it down was how he checked.” “We need that voice in the curriculum,” Patricia said.

“Not copied, but the principle. The way it builds. Every concept earned before the next one is introduced.” “I’ve been trying to write some of that,” Ethan said. He hadn’t told her this. He’d started doing it 2 weeks earlier at the kitchen table after Sophie went to sleep, taking entries from the notebooks and attempting to translate them into something more accessible, more structured, less dependent on prior knowledge.

It was harder than he’d expected. His father’s prose was deceptively dense. It looked simple and was not. Patricia looked at him. “Show me.” He opened a drawer under the bench, the one he used for personal paperwork, not tools, and took out a folder. Eight pages, handwritten, because he thought better on paper than on a screen, and because the act of writing by hand slowed him down to a useful pace.

Patricia read it standing up, leaning against the bench, not bothering with the stool. When she was done, she put it in the folder and looked at him. “This is good,” she said. “It’s rough, but the bones are right.” “I know it’s rough,” he said. “I’m going to introduce you to someone,” she said. “Her name is Yolanda Chen.

She’s a curriculum designer who’s worked on technical education programs for 15 years. She’s the person I mentioned earlier, the one who’s good at designing for people who’ve been told the field isn’t for them.” She paused. “She’s also not easy to work with.” “What does that mean?” “It means she has strong opinions, and she’ll push back on things you think are settled.

She’s not difficult to be around. She’s just not going to let things through that she doesn’t think are right.” Ethan considered this. “That sounds like a useful quality in someone building a curriculum.” “It is,” Patricia said. “It’s just good to know about before you’re in a room with her.” Yolanda Chen arrived at the foundation office 2 weeks later and immediately moved a chair so that she could see both the whiteboard and the door simultaneously, which established something about how she operated before she’d said a word.

She was in her early 40s with reading glasses pushed up on her head, as though she’d forgotten them there. And she had the particular focused energy of someone who had more going on in her mind than was visible on her face. She’d read Ethan’s eight pages before the meeting. Patricia had sent them in advance.

And she opened with a question that cut directly to the problem he’d been wrestling with since he’d started writing. “You’re writing for the version of yourself that already knows why this matters,” she said, “not for the version that doesn’t yet.” Ethan sat back slightly. “Explain.”  “This line here.

” She’d printed the pages and they were marked in pencil, extensive marks, which would have been alarming if she’d looked anything other than analytical about it. She read aloud. “The question is not what the system is doing wrong, but what the system is trying to do and why it can’t.” “That’s correct.

It’s also meaningless to someone who’s never thought about a system as having a goal.” “How do you build it so it isn’t?” he said. “You build a prior experience first. Before you introduce the concept, you give the student an experience that makes the concept feel like the answer to a question they already have.” She put the pages down.

“What’s the first thing your father ever had you do?” “The first time he actually involved you in a repair.” Ethan thought back. “He had me hold a flashlight.” “For how long?” “Long time, weeks probably.” “Different jobs.” “He never explained what he was looking at, just hold the flashlight here, move it there, hold it steady.

” “And what did that do?” He was quiet for a moment. “It made me curious. I wanted to know what I was lighting up.” Yolanda pointed at him. “That’s lesson one, not a concept, an experience that creates the need for the concept.” She leaned forward. “We designed the first week of this program so that every student leaves on Friday wanting to understand something they didn’t understand on Monday.

👉 [Tap here for the Next Part ] 👈