The Other Side on Shane's Personal Blog

Chapter 1: The Weight of 3 AM

Mon, 10 Nov 2025 00:00:00 GMT

Chapter 1: The Weight of 3 AM

The cursor blinks. White against blue.

Google—Senior Software Engineer, Education Technology. The page has been open for forty-seven minutes.

David’s apartment is quiet in the way only 3 AM can be. No traffic. No footsteps from upstairs. His desk lamp creates a small circle of light. Everything beyond it remains in shadow: the unmade futon, the stack of unwashed dishes, the boxes he still hasn’t unpacked from six months ago.

The apartment smells like stale coffee and something else—the sour-sweet smell of stress sweat in unwashed clothes. When did he last do laundry? The radiator clanks. Too warm, then too cold. He can’t figure out how to adjust it.

His phone sits face-down beside the mousepad. Three missed calls from his mother. The screen has a crack he got two weeks ago. Dropped it rushing to a user test. Never fixed it. Costs $80. That’s almost three days of runway.

The job posting describes what he used to be: Strong background in full-stack development. Experience shipping products at scale. Passion for education technology.

He could write the cover letter in twenty minutes. He’s written it before—different companies, same paragraphs, same lies about passion.

His co-founder’s text is still on the screen, minimized but visible. The user feedback is tough but we can pivot. You’re brilliant at this. We’ll figure it out. Get some rest.

Genuinely meant. No sarcasm. Just support.

Somehow that makes it worse.

David closes his eyes. His neck aches. When did he last stand up? His lower back has that hollow feeling from too many hours in the chair. He should eat something. He made coffee around 2 PM. That was dinner, apparently.

When he opens them, the cursor is still blinking.

Yesterday they showed the prototype to twelve high school students. Three months of work. Eighty-hour weeks. Every algorithm optimized.

“It feels like another homework app.”

“I don’t really get what makes it different.”

Different. It was supposed to be different. It was supposed to understand how each kid learns instead of forcing them into standardized paths. It was supposed to—

He switches back to the job posting.

Competitive salary. Comprehensive benefits. Opportunity to work with world-class team.

Six years he worked with a world-class team. Nice people. Smart. They went to lunch together, complained about product managers, shipped features that didn’t matter. Then went home and did it again.

His checking account balance is $3,847. Rent is $1,600. Due in eleven days.

On the corner of his desk: a worn paperback. Steve Jobs by Walter Isaacson. The spine cracked in seven places, pages dog-eared, one passage underlined three times in blue ink.

He read it five years ago. It felt true then.

Now he’s the beginner. It doesn’t feel light.

The lamp flickers. Needs a new bulb.

David scrolls down to the “Apply Now” button. Green. Friendly. Inviting.

His finger hovers over the trackpad.

Outside, a car passes. Headlights sweep across the ceiling, briefly illuminating cracks in the plaster. The ceiling returns to darkness.

He moves the cursor away. Not closing the tab. Just hovering in the empty space beside it.

Neutral territory.

The memory arrives without warning.

It’s the way they do at 3 AM—not summoned, just suddenly there.

October 5, 2011. Sixteen years old.

The high school library smells like old carpet and anxiety. Fluorescent lights hum overhead. Everyone around him has their heads down, highlighters moving across textbooks in yellow and pink streaks. Three weeks until midterms. Class rank updates next month.

David is supposed to be studying for the physics exam. Instead, he’s on a borrowed laptop, reading the news.

Steve Jobs is dead.

He doesn’t know why he clicks the article. He’s heard of Jobs—everyone has. The iPhone guy. But it’s not like David owns Apple stock or camps outside stores for product launches.

Still, he clicks.

The article mentions the 2005 Stanford commencement speech. There’s a link. David has twelve minutes before the library closes. He plugs in his headphones and presses play.

Jobs’s voice is quieter than he expected. Not the salesman voice from keynotes. Something else. More tired. More real.

“…for the past 33 years, I have looked in the mirror every morning and asked myself: ‘If today were the last day of my life, would I want to do what I am about to do today?’ And whenever the answer has been ‘No’ for too many days in a row, I know I need to change something.”

David glances around the library. Everyone is still studying. Competing.

The boy next to him—Marcus, ranked third in their class—has his textbook angled so David can’t see his notes. Not that David was trying. But the assumption is there.

Earlier today, their physics teacher handed back exams. David got 98. Top score. Mr. Chen announced it to the class. “This is what excellence looks like,” he said, holding up David’s test.

Marcus got 94. David saw his face when the teacher said it. Something died in his eyes for just a moment.

David wanted to say something. That it didn’t matter. That four points meant nothing. But he knew it did matter. Because next month, when rankings update, those four points would be part of the calculation. And Marcus’s parents would ask why he wasn’t first. And Marcus would study harder, sleep less, pull further ahead of whoever was ranked fourth.

That’s how it works. Someone wins. Everyone else loses.

David looks down at his physics textbook now. He’s good at this. Top of the class. His parents are proud. The path is clear: ace the exams, get into the best university, major in computer science or engineering, land a job at a big tech company.

Stability. Safety. Success.

Jobs keeps talking.

*“Your time is limited, so don’t waste it living someone else’s life… Don’t let the noise of others’ opinions drown out your own inner voice.”

David rewinds ten seconds. Listens again.

Your own inner voice.

Does he have one? Or has he just been following the script—hitting his marks, clearing the hurdles, winning the race without asking where it leads?

The librarian announces five minutes until closing. Around him, students pack their bags with the efficient desperation of people who have three more hours of homework waiting at home.

David closes the laptop. Returns it to the desk. Walks out into the October evening.

The air is cool. The sky is that particular shade of orange-grey that happens right before full darkness. He stands on the steps for a moment, backpack heavy on his shoulders.

Something shifted in the library. Not dramatic. Not a lightning bolt.

Just a small, quiet yearning.

He thinks about Marcus’s face. The numb look when he got 94 instead of 98. Four points. David’s victory was Marcus’s defeat. That’s how the system works.

But Jobs’s voice—that tired, real voice—suggested something else. Not clearly. Not in words David can articulate. Just a feeling that the race everyone’s running might be heading somewhere he doesn’t want to go.

Don’t be trapped by dogma—which is living with the results of other people’s thinking.

He doesn’t know what it means. Can’t explain it. But the feeling is there, lodged somewhere between his ribs.

David starts walking home.

The world around him looks the same as it did an hour ago. But he’s carrying something now. A question that will follow him for the next decade:

If today were the last day of my life, would I want to do what I’m about to do today?

Sixteen years old.

The answer is already no.

The memory fades.

David is back at his desk. 4:17 AM. The job posting still open.

His hands are cold. The apartment is cold. He should turn on the heat, but that costs money.

He looks at the biography on his desk. Five years since he first read it. Ten years since he first heard that speech.

A decade of saying “next year.”

Next year, when he has more experience. Next year, when he knows more about business. Next year, when he has more money… Next year, when the risk feels smaller.

But risk doesn’t get smaller. It just gets heavier. Every promotion, every raise, every year of stability—another link in the chain.

Eight months ago, he was laid off. Lost the salary, the health insurance, the 401k match—not by choice, but by “market conditions” and “fiscal responsibility.”

He could never forget his mother’s voice on the phone that day: “How will you afford a house? How will you build a family? Your father and I didn’t sacrifice everything so you could lose everything.”

She wasn’t angry. She was terrified. For mom, he just lost his bright future.

Because she sees him suffering, living in that tiny apartment, all alone. She sees the difficulties—clear as anything. To her, he’s destroying his future for nothing. For her, he is gambling his future away. And maybe she’s right. Maybe this is unbearable.

Three missed calls on his phone. He knows what she’s thinking: He looks so tired. He used to have a good job, a future. Now what? How long can he keep this up? What if he’s forty and still trying? What are the chances of building a successful company from scratch? How could he compete with the giants?

She imagines him alone. No wife, no children, no grandchildren for her to hold. No stability to fall back on when his parents are gone. Just him and his ideas and the years slipping past. She sees the suffering.

David closes his eyes. What troubles him the most is that, deep down, he knows his mother is not wrong. According to latest statistics, ninety percent of startups end up with nothing. Years of hard work down the drain.

Just to make things worse, his mind keeps reminding him that his latest prototype is a complete failure. The users didn’t get it. His co-founder, Alex, is being kind and supportive, which somehow makes it worse. At least if Alex were angry, David could fight back. But there’s nothing to fight. Just the empty space where certainty used to be. Everything is even more unbearable all of a sudden.

He could click the button. Send the application. Interview in a few weeks. Offer letter in a month. Back to the life he knows.

His mother would go back to talk about family events again.

David stands up. His knees crack. He walks to the window.

The city sprawls below—lights scattered across the darkness like dropped coins. Somewhere out there, other people are awake. Sitting at desks, staring at screens, hovering between the life they have and the life they can’t quite reach.

He wonders if they’ll click.

Behind him, the laptop screen dims to save battery. The room gets darker.

When he turns back, his hands are steadier than they were an hour ago.

He sits down.

The job posting is still there. The green button. One click.

Three months of work—gone. The users didn’t get it. Eight months since the layoff, and what does he have to show for it? A failed prototype. A dwindling bank account. A mother who can’t sleep.

Friends from college have stopped asking how it’s going. He knows what they’re thinking. Eight months. If it were going to work, wouldn’t something have happened by now?

Maybe they’re right.

Maybe he’s just someone who couldn’t handle the corporate world and is pretending this is a choice instead of an escape. He sometimes wonders himself about his true intentions. Maybe he’s just not mature enough to face the daily grinding of a corporate employee. Maybe he should “Grow up!” as his dad told him, and get a real job.

Maybe the smart thing—the rational thing—is to admit it didn’t work and move on.

He could be back in an office in six weeks. Salary. Structure. Routine coffee breaks. Coworkers’ chitchat. A title to tell people at parties. Just be normal again. Just one click away from everything being normal again.

David’s hand moves to the trackpad.

But something stops him.

He could almost recite all the quotes from different entrepreneurs’ biographies about how they “weather the storm” during dark times with dedication and perseverance. Those words used to boil his blood, now feel almost irrelevant. But then again, no words can be powerful enough when every fiber of one’s being tells them to give up.

He thinks about the user interviews yesterday. Twelve kids. Most of them said the prototype felt like just another homework app. But there was just one odd duck—a girl, maybe fifteen—who said something different.

She was quiet most of the session. Didn’t raise her hand when they asked for feedback. But as she was leaving, she turned back: “I liked that it asked me what I’m curious about. No one’s ever asked me that before.”

It wasn’t enough though. Twelve users, one lukewarm positive. The investors wouldn’t touch it with a ten foot pole.

But she said no one’s ever asked.

Somehow David is reminded of Marcus. The numb look in his eyes over four points on a physics exam. The education system that sorted people like products, measured human beings against each other, to sort out “premium goods”, and eliminate the rest. Never bothered asking what are you interested in? What do you care about? How do you learn? But then again, cog in a machine doesn’t need to have a say.

He thinks about sixteen-year-old David, carrying that vague yearning home from the library. The feeling that the race everyone was running led somewhere he didn’t want to go.

Ten years later, he knows exactly where it leads. He lived it for six years. The promotions, the peer reviews, the performance improvement plans for people who didn’t clear the bar. Kind people, smart people, all running the same race. Competing when they could be creating. Extracting value when they could be building it.

He quit because he couldn’t breathe in that world.

But it’s not enough to quit. No. Someone needs to build something to tell that girl, and millions of others who said no one’s ever asked, that there IS another way.

But he failed. The prototype failed because it wasn’t good enough yet. His heart squeezes. The uncertainty is drowning him as his mind gives him a reality check. But the vision was right. No one should be forced into a standard part of the societal machine. He still believes in it. And the thought of it poked a tiny hole in the darkness.

“I still loved what I did. The turn of events at Apple had not changed that one bit. I had been rejected, but I was still in love. So I decided to start over.”

David moves the cursor to the browser tab.

And closes it.

Not just the job posting—the whole browser. Every tab. The application. The prototype. Alex’s encouraging messages. All of it.

The screen goes dark.

For a moment, he sees his own reflection in the black glass. Scruffy beard he hasn’t bothered to trim. Dull skin from sleep deprivation. Eyes rimmed red from staring at the screen day through night. Someone he barely recognizes.

Is he brave or just stubborn? Visionary or delusional? Determined or single-minded?

If he clicks that button, he’ll spend the rest of his life wondering. And sixteen-year-old David—the one who heard Jobs’s voice and felt that yearning—will never get an answer.

David opens a blank document.

He types: “Prototype #2 - What We Missed”

His fingers pause over the keyboard. He cannot tell if his heart is beating from fear or excitement.

Starting again means facing Alex tomorrow and saying: I know it failed, but I want to try again. It means another three months of eighty-hour weeks. Another round of user tests that might go exactly the same way. More savings burned. More missed calls from his mother. More friends who fear to ask.

It means choosing uncertainty over safety. Pain over comfort. The almost certain failure over guaranteed stability.

3 AM is when the walls close in and every choice feels impossible. When the performance ends and you’re alone with the question Jobs asked:

If today were the last day of my life, would I want to do what I’m about to do today?

David looks at the blank document. With all the uncertainties in his life, the answer to this question is strangely clear.

So he starts typing. With the same stubborn, unnameable yearning he felt on those library steps ten years ago.

You can’t connect the dots looking forward; you can only connect them looking backwards. You have to trust that the dots will somehow connect in your future.

As an atheist, he somehow starts to understand what faith feels like. He could swear reciting the same words thousands of times before have never given him this feeling like today. Strange how the darker your life is, the brighter faith seems to shine, David thinks to himself.

He doesn’t know if this will work. Doesn’t know if he’s building something real or just refusing to admit defeat. Doesn’t know if in six months he’ll be out of money and back in an office, this whole chapter of his life swept under the rug as “lessons learned.”

But he knows he’s not done yet.

The users said it felt like another homework app. That means they almost saw it. They were close enough to compare it to something familiar. That’s not complete failure—that’s a gap. “A gap is a bridge yet to be built.” David thinks to himself.

What did they not see? What didn’t he explain? What assumption did he make that they didn’t share?

His fingers move across the keyboard. Not writing code. Just thinking through the problem.

First light still an hour away, but the darkness is thinning.

David types until his neck aches and his eyes burn and the first birds start their morning calls.

He doesn’t have answers yet. Just better questions.

But that’s enough. For now, that’s enough.

Outside, the city begins to wake. The world continuing its rotation whether he’s ready or not.

David saves the document.

As the computer goes to sleep, the cursor blinks on the last line: Tomorrow: Start fresh. Ask different questions. Try again.

End of Chapter 1

Chapter 2: The Comfortable Cage

Mon, 10 Nov 2025 00:00:00 GMT

Chapter 2: The Comfortable Cage

Three years earlier.

The badge beeps. Green light. David walks through TechCorp’s glass doors for the thousandth time.

9:47 AM. Seventeen minutes late. No one cares. The engineering floor doesn’t start until ten—“flexible hours,” they call it.

He looks like everyone else here. Button-down untucked, dark circles from scrolling too late, jeans that cost more than a week of groceries used to. The elevator reflects him back: indistinguishable.

Seventh floor. Open-plan. Long wooden tables, expensive coffee, kombucha on tap. Sarah from DevOps waves. He waves back. Everyone is nice here.

His monitor wakes. Three Slack channels. Two calendar invites. A pull request waiting for review.

He wrote that code three days ago. Six hours of work. A feature that lets users customize dashboard widgets. The analytics say 2% of users will touch it. But a competitor has it, so they need it too.

David reviews. Approves. Merges.

Somewhere, a server updates. A feature no one needs joins millions of others.

Alex texts: Lunch today?

David tries Thursday. Alex is in Seattle. Next week, then. Both know it won’t happen.

Slack: “Great Q3 launch! Hit 97% OKRs!”

Nights and weekends for that. Pizza boxes. “Crunch time.” They shipped an onboarding flow nobody asked for, backend tweaks nobody noticed.

His mother asks about houses. Will look this weekend, he lies. This weekend: sleep, takeout, the novel he never starts.

Noon. Sprint planning. “Prioritize Q4 roadmap. Discuss technical debt.”

Technical debt—code built fast and broken, never fixed. Just pile more features on top. It works. Makes money. Stock goes up. Everyone gets bonuses.

Kevin pulls him into a conference room. “You’re getting promoted. Senior Engineer. 15% raise.”

David’s stomach tightens.

Fifteen percent. Down payment in eighteen months. Expensive coffee without guilt. Parents proud. And harder to leave.

“Thanks,” he says.

“You’ll interview junior engineers too. We’re scaling.”

David wonders if he’ll recognize himself in them. The ones who think shipping code will feel different than college. Who think “making an impact” means more than optimizing conversion rates.

Through the glass wall: eighty people at desks. Headphones. Pair-programming. Laughter from the kitchen.

Good people. Smart people. Building someone else’s vision for salary and benefits.

David opens his Notes app. Past grocery lists to a document from two years ago: “Ideas.”

Thirty-seven entries. Startup concepts. Problems nobody’s solving. The last one from six months ago.

He hasn’t added anything since.

Sprint planning in fifteen minutes. He closes the app. Straightens his shirt.

The city sprawls below. How many people calculating the exact dollar amount that would make them stay?

How many winning?

At his desk: Jira tickets. “Implement A/B test for button colors.” “Refactor authentication module.” “Add logging.”

Necessary. Reasonable. Uninspiring.

He accepts them all. Joins the planning call. Camera off. Says just enough: “Sounds good.” “I can take that.” “Two days seems reasonable.”

For six hours he writes code. Tests. Refactors. The world falls away.

This is why he became an engineer. Not the meetings. The craft. Making something work beautifully.

Even if the thing being built doesn’t matter.

October becomes November.

The promotion is official. David’s new title appears in his email signature: Senior Software Engineer. His salary increases by $18,000.

His mother calls. “Your aunt heard about your promotion. She’s very proud.”

David sits in his apartment—the nice one he moved to six months ago. Floor-to-ceiling windows. In-unit washer-dryer. The kitchen has granite countertops he’s never cooked on.

“That’s nice,” he says.

“You don’t sound excited.”

“I am. Just tired.”

“You’re always tired.” Her voice shifts. Concerned. “Are you taking care of yourself?”

He looks around. Takeout containers on the counter from the past three days. He meant to throw them out. The apartment smells faintly of old Thai food and recycled air. When did he last open a window?

“Yeah, Mom. I’m fine.”

They talk for seven more minutes. She tells him about his cousin’s wedding. His father’s new glasses. The neighbor’s dog that barks at 6 AM.

David says “uh-huh” at the right intervals. When they hang up, he can’t remember a single detail.

November becomes December.

Holiday party at TechCorp. Open bar, catered food, a DJ playing music nobody dances to.

David stands near the appetizer table with Sarah and two other engineers. They’re talking about the latest reorg. Who got promoted. Who didn’t. The politics of it.

“Did you hear Chen applied for Staff?” Sarah says. “Third time.”

“He’s not going to get it,” Tom says. “Not political enough.”

They talk about Chen like he’s not a real person. Just a piece in the game. David eats a spring roll. It’s good. He eats another.

Kevin—his manager—walks over. Slightly drunk. Friendly. “David! There’s my senior engineer. How’s the new salary treating you?”

“Good. Thanks again.”

“You earned it, man. That authentication refactor saved us three weeks. Leadership noticed.”

Leadership noticed. David wonders who “leadership” is. Faceless VPs who read metrics. Who care about quarterly numbers. Who laid off eighty people last year to hit profit targets.

“Glad to help,” David says.

Kevin leans closer. Whispers conspiratorially. “Between us—I’m pushing for you to interview lead engineer candidates next year. Get you into the hiring pipeline. Good for your career.”

His career. The ladder. The next rung.

David nods. Smiles. Says thank you.

Kevin claps him on the shoulder and wanders off.

Sarah rolls her eyes. “Lead engineer interviews. Great, more meetings.”

“At least the pay bump is good,” Tom says.

They talk about pay for ten more minutes. RSU vesting schedules. 401k matching. Health insurance deductibles.

David excuses himself. Goes to the bathroom. Stares at himself in the mirror.

He’s wearing the same button-down he wore to his college graduation. It fit better then. His face looks older. Not in a good way. Tired. The fluorescent lights make his skin look gray.

When did he last feel excited about anything?

The question arrives without warning. He can’t answer it.

David washes his hands. The soap smells like fake lavender. Returns to the party. Stays another hour because leaving early would be noticed.

Drives home at 9 PM. The city is decorated for Christmas. Lights strung across buildings. Inflatable Santas. Everywhere, the performance of joy.

December becomes January.

David’s calendar fills. Q1 planning. OKR setting. One-on-ones with Kevin. Tech talks he doesn’t care about. An all-hands where the CEO talks about “exciting growth opportunities” while the stock price declines.

On January 17th, a Tuesday, something shifts.

It’s not dramatic. No lightning bolt. Just a moment that cracks something.

David is in a conference room. Fourth floor. Windows overlooking the parking lot. There are seven people in the meeting. The topic: whether to deprecate a legacy API that three customers still use.

The product manager—Jen, nice enough—argues they should keep it. “Three customers is three customers. We can’t just abandon them.”

The engineering director—Michael, not nice—argues they should sunset it. “It’s costing us maintenance hours. Three customers don’t justify the overhead.”

They debate for thirty minutes. Data gets pulled up. Spreadsheets. Customer lifetime value calculations. Engineering hour costs.

David sits quietly. Listening. Watching.

At some point, Jen says: “But what about the users? Don’t we have a responsibility?”

Michael doesn’t even pause. “Our responsibility is to the bottom line. That’s how we stay in business.”

The room nods. It’s the right answer. The practical answer.

David feels something cold settle in his chest.

He thinks about the three customers. Real people somewhere. Using this API in their products. Trusting that it’ll keep working. Now about to be deprecated because the spreadsheet says they’re not worth it.

The meeting ends. They vote to sunset the API. Jen will send the deprecation notice. Engineering will archive the code. The three customers will get six months to migrate.

David walks back to his desk. Sits down. Opens the code for the API they just voted to kill.

It’s not elegant code. Written five years ago by someone who left the company. But it works. And someone is using it.

He closes the file.

Opens his Notes app. Scrolls to “Ideas.”

Thirty-seven entries. He hasn’t looked at this in—what? Four months? Five?

The last entry is from September. Six months ago. “Micro-learning platform - adaptive flashcards.”

He reads through them. Some are stupid. Some might be good. All of them gathering dust.

David closes the app.

Checks his email. Seventeen unread. He processes them mechanically. Yes. No. Will circle back. Looks good.

At 4:47 PM, his mother texts: Your cousin is pregnant. You’re going to be a… second cousin?

David types back: Great. Congratulations to her.

But he thinks: I’m 28. My cousin is building a family. Alex just proposed to his girlfriend. Sarah is buying a house.

And David is—what? Comfortable. Successful. Moving up the ladder.

To where?

He doesn’t add a thirty-eighth idea. Doesn’t delete the thirty-seven. Just closes the app.

The screen goes dark. His reflection stares back.

He looks tired.

January becomes February. February becomes March.

David’s calendar stays full. The meetings blur together. Planning. Retrospectives. Design reviews. Coffee chats with junior engineers who think working here is exciting.

He does his job well. Ships code. Reviews PRs. Participates in discussions. Says the right things.

But somewhere—quietly, invisibly—something is dying.

It’s the part of him that once believed this work mattered. That building software was building the future. That solving technical problems was changing the world.

Now he knows: most problems aren’t worth solving. Most features aren’t worth building. Most meetings aren’t worth having.

But the salary is good. The benefits are good. His mother is proud. His father is relieved.

So David stays.

The golden handcuffs, tightening one day at a time.

On March 15th, he goes to lunch with a college friend. Marcus—different Marcus than high school. They meet at a Thai place downtown.

Marcus works at a startup. Terrible pay, long hours, uncertainty. He complains about it for twenty minutes. The broken deployment pipeline. The founder who keeps changing direction. The runway down to four months.

“But,” Marcus says, fork hovering over his pad thai, “at least I care about what we’re building. You know? Like, it might fail. Probably will. But I’d rather fail at something I care about than succeed at something I don’t.”

He looks at David. “You get it, right?”

David chews slowly. Swallows. “Yeah.”

But he doesn’t get it anymore. Or he does, and that’s worse.

When lunch ends, Marcus pays for both of them. “You can get next time. I know you’re probably saving for a house or something.”

David doesn’t correct him.

Walks back to the office. The badge beeps. Green light. The elevator to the seventh floor.

At his desk, he opens his Notes app without meaning to. Muscle memory. The list of thirty-seven ideas.

He hovers over the ”+” button.

Thinks about Marcus. The startup that might fail. The certainty that failing matters if you care about what you’re failing at.

Thinks about the API they deprecated. The three customers who didn’t matter enough.

Thinks about sixteen-year-old David in a library. Hearing Jobs’s voice. Thinking there was another way to live.

He doesn’t add an idea.

Doesn’t delete them either.

Just closes the app. Returns to Jira. Picks up the next ticket.

At 7 PM he’s still at his desk. Most people have gone home. The office is quiet. Just the hum of climate control and distant keyboard clicks.

David saves his work. Closes his laptop. Stands up.

His lower back aches. How many hours did he sit today? Eight? Nine?

He walks to the window. The city sprawls below. March evening. Not quite spring. The light is fading.

Jobs’s voice echoes from ten years ago: Don’t let the noise of others’ opinions drown out your own inner voice.

David wonders if he still has an inner voice. Or if he traded it somewhere along the way. For salary. For security. For the look of relief on his father’s face when David said he got promoted.

He stands at the window for a long time.

The city below pulses with life. People heading home. To families. To partners. To lives that make sense.

David feels nothing about that. Not envy. Not contentment. Just—distance.

Like he’s watching through glass. Separate. Safe. Numb.

This is the cage. Not cruel. Just comfortable.

The kind you don’t notice until you’ve been inside it for years.

David picks up his laptop bag. Badges out. The badge beeps. Green light. A thousand times. Ten thousand.

How many more times will he hear that sound?

He doesn’t know.

But he knows he can’t stop. Not yet. The mortgage his parents want him to get. The wife they want him to find. The life they want him to build.

All requiring this. The steady paycheck. The career advancement. The responsible choice.

David drives home. Orders delivery. Thai food, ironically. Eats in front of his laptop.

The Notes app is closed. The thirty-seven ideas are sleeping.

Tomorrow he’ll wake up. Badge in. Do it again.

The comfortable cage.

Safe.

Shrinking.

Killing him slowly.

End of Chapter 2

Chapter 3: The Crack

Mon, 10 Nov 2025 00:00:00 GMT

Chapter 3: The Crack

April. One month before the layoff.

The feature request arrives on a Wednesday morning.

Subject: “Engagement Initiative Q2 - Push Notification Optimization”

David reads it at his desk. Coffee going cold. The office is bright with spring sunlight. Around him, engineers are settling into their morning routines. Headphones on. Screens glowing. The comfortable hum of productivity.

The email is from product leadership. Copied to all of engineering.

“Data shows users who receive push notifications engage 34% more frequently. We need to implement an optimized notification system that maximizes user return. Target: increase daily active users by 15% this quarter.”

Attached: a detailed spec. Notification triggers. Frequency caps (three per day minimum). Personalized messaging that adapts based on user behavior. A/B testing framework to find the “sweet spot” between engagement and annoyance.

David scrolls through the spec.

The notifications aren’t informative. They’re designed to create anxiety. “You have 3 unread updates!” when there are no meaningful updates. “Your friends are active now!” when friends aren’t actually waiting. “Don’t miss out on…” when there’s nothing to miss.

The spec includes a section called “Psychological Triggers.”

“Use FOMO (fear of missing out), social proof, and variable reward schedules to maximize click-through rates. Users should feel compelled to open the app even when they don’t consciously want to.”

Even when they don’t consciously want to.

David re-reads that line.

Sets his coffee down. Looks around the office.

Sarah is at her desk, working on the same email. She glances at David, rolls her eyes. “More engagement theater.”

“Yeah,” David says.

“At least it’s not another A/B test for button colors,” Tom says from across the desk cluster.

They laugh. The kind of laugh that acknowledges absurdity but accepts it. Just another feature request. Just another quarter. Just another metric to move.

David opens the technical requirements. It’s well-specified. Clear acceptance criteria. Estimated effort: two weeks. He’s the logical person to build it—he wrote most of the notification infrastructure.

He could knock this out in ten days. Maybe less.

His fingers hover over the keyboard. He should reply-all. “I can take this on. Let’s discuss in planning.”

That’s what a good senior engineer does. Takes ownership. Delivers.

Instead, David closes the email.

Opens his calendar. The notification optimization is probably getting added to tomorrow’s planning meeting. He should prepare. Maybe come with questions. Edge cases. Technical risks.

He opens the spec again. Reads the “Psychological Triggers” section.

“Variable reward schedules (intermittent reinforcement) are the most effective at creating habitual behavior. Users should receive meaningful notifications approximately 1 in 4 times, with the other 3 being low-value or false triggers. This creates a ‘slot machine’ effect where users compulsively check even when notifications are likely meaningless.”

The slot machine effect.

David thinks about his own phone. The way he checks it without meaning to. The little dopamine hit when there’s a red notification badge. The disappointment when it’s nothing. The way he checks again fifteen minutes later.

That’s engineered. By someone like him. At companies like this.

He’s never thought about it explicitly before. It was just… the job. Increase engagement. Optimize metrics. Make the numbers go up.

But seeing it written out—“even when they don’t consciously want to”—something shifts.

He closes the spec.

Opens his email. Starts typing a response. “I have concerns about the psychological impact of—”

Deletes it.

Types: “This feels manipulative. Are we comfortable—”

Deletes it.

Types: “What problem are we actually solving for users—”

Deletes it.

Closes the draft.

Sits staring at his blank screen.

Around him, the office continues. People working. Building features. Moving metrics. No one else seems disturbed.

Maybe David is overreacting. It’s just notifications. Everyone does it. Facebook, Twitter, Instagram, every app. It’s industry standard.

That’s worse, somehow. That it’s normal. Expected. Best practice.

Build systems that manipulate people into compulsive behavior. Measure success by addiction metrics. Call it “engagement.”

David’s chest feels tight.

He stands up. Walks to the bathroom. Not because he needs to. Just to move.

The bathroom is empty. White tile. Too-bright lights. David washes his hands. The water is too hot. He doesn’t adjust it.

Looks at himself in the mirror.

When he started here three years ago, he believed he was building the future. Making people’s lives better through technology. Solving real problems.

When did it become this? Figuring out how to manipulate people’s psychology to boost engagement metrics? Designing slot machines disguised as social networks?

And when did he stop noticing?

The answer is: gradually. One feature at a time. One compromise at a time. Each one small enough to ignore. Until you wake up one day and realize you’ve spent three years building a cage for other people.

While living in one yourself.

David dries his hands. The paper towel dispenser is automatic. It dispenses exactly twelve inches of paper. Optimized. Efficient. Someone probably A/B tested that.

He walks back to his desk.

The notification spec is still open on his screen. Waiting for him to reply. To take ownership. To build the slot machine.

David opens his Notes app. Scrolls to “Ideas.”

Thirty-seven entries.

Number 14: “Ethical social media - no dark patterns, no manipulation, just useful features.”

He wrote that two years ago. Back when he still noticed the darkness. Before he learned not to look.

David closes the app.

Opens the email draft again.

Types: “I don’t think I’m the right person for this project. Happy to help with technical review but would prefer not to be lead on implementation.”

His finger hovers over send.

This is small rebellion. Meaningless, probably. Someone else will build it. The feature will ship. Users will get manipulated. The metrics will go up.

But at least David won’t be the one who built it.

At least he can say he saw the line and didn’t cross it.

He hits send.

The email disappears from his draft folder. Appears in his sent folder. Out in the world now.

David takes a breath. Waits for the fear. The worry that he just made a career-limiting move. That Kevin will be disappointed. That this will come up in his performance review.

But what he feels instead is—lighter.

Like he’s been holding his breath for three years and finally exhaled.

It’s not enough. One email doesn’t fix anything. The feature will still get built. The system will keep running.

But it’s something.

A tiny crack in the comfortable numbness.

Kevin messages him twenty minutes later.

“Hey, saw your email about the notification project. Can we chat?”

David’s stomach tightens.

“Sure. Now?”

“Conference room 4B in 5?”

David closes his laptop. Walks to the conference room. Kevin is already there. Door open. Friendly smile.

“Hey,” Kevin says. “Close the door?”

David closes it. Sits down.

Kevin leans back. Casual. “So. The notification thing. You said you don’t want to lead it?”

“Yeah. I just… I don’t think I’m the right fit.”

“Can I ask why? You built most of the notification infrastructure. You’re the obvious choice.”

David chooses his words carefully. “I have some concerns about the approach. The psychological manipulation aspects. I’m not sure I’m comfortable implementing that.”

Kevin nods slowly. “I appreciate the honesty. But—and I want to be direct here—this is the job. Engagement optimization is what we do. It’s how we make money.”

“I understand.”

“Do you?” Kevin leans forward. Not aggressive. Concerned. “David, you’re a senior engineer now. That means taking on projects that move the needle. Even if they’re not… I don’t know, noble. They’re necessary.”

“Necessary for what?”

“For the company to survive. For us to keep the lights on. For you to keep getting paid.”

The words hang in the air.

Kevin continues. “Look, I get it. The spec is a little… explicit about the psychology stuff. That’s just how product talks. But the end result is users engaging more with the platform. That’s not evil. That’s what we’re here to do.”

“Even if users don’t consciously want to engage?”

Kevin pauses. “That’s editorializing. The data shows they come back. If they didn’t want to, they’d delete the app.”

“People don’t delete slot machines either. They just keep pulling the lever.”

Silence.

Kevin’s expression shifts. Harder now. “I’m going to level with you. This feels like you’re making a moral stance. Which is fine. But moral stances don’t ship product. And product is how we stay employed.”

“I know.”

“Do you? Because from where I sit, you’re turning down a high-priority project. That’s going to raise questions.”

David doesn’t respond.

Kevin sighs. “I like you, David. You’re technically strong. You deliver. But I need to know you’re on board with the company’s direction. Can you do that?”

The question is clear. Get on board or get out.

David thinks about his salary. His mother’s pride. The health insurance. The 401k. The nice apartment.

The thirty-seven ideas gathering dust.

The three customers who weren’t worth it.

Marcus saying he’d rather fail at something he cares about than succeed at something he doesn’t.

“I don’t know,” David says. Honestly. “I’m not sure I can.”

Kevin looks at him for a long moment.

“Okay,” he says finally. “I’ll assign it to someone else. But David—this is going to come up. In your review. In future planning. I can’t keep giving you a pass on high-priority work.”

“I understand.”

“I hope you do.” Kevin stands. Opens the door. “Think about what you want. Because this trajectory—turning down projects, questioning the mission—that doesn’t end well here.”

David nods. Walks back to his desk.

His hands are shaking slightly.

He just made his job harder. Probably damaged his relationship with Kevin. Maybe capped his career here.

For what? The feature is still getting built. Tom will probably take it. He’ll do a good job. Users will get manipulated. Nothing will change.

Except David won’t be the one who did it.

And somehow, that matters.

That evening, David sits in his apartment.

Nice apartment. Floor-to-ceiling windows. Granite countertops. All bought with salary from building things he doesn’t believe in.

He opens his laptop. The company Slack is buzzing. Tom already volunteered for the notification project. Kevin thanked him publicly. Several people reacted with thumbs-up emojis.

David closes Slack.

Opens his email. Three messages from recruiters. He usually deletes them immediately.

Tonight he reads one.

“Senior Engineering role at StartupCo. Mission-driven. Building tools that help people learn. Competitive salary. Would love to chat.”

Tools that help people learn.

David hovers over the delete button.

Doesn’t click it.

Saves it to a folder instead. Labels it: “Maybe.”

He knows what’s happening. The comfortable cage is cracking. The numbness is wearing off. He’s starting to see clearly again.

And what he sees is unbearable.

Three years building features nobody needs. Optimizing metrics that don’t matter. Playing politics to climb a ladder that leads nowhere he wants to go.

Making things worse in the world. One dark pattern at a time.

His mother calls. He doesn’t answer. Can’t handle the question “how’s work?” Can’t lie anymore. Can’t tell the truth.

The missed call sits there.

David opens his Notes app. Scrolls to “Ideas.”

Thirty-seven entries. Two years since he added one.

He hovers over the ”+” button.

Types: “#38 - Something that doesn’t manipulate people. Something honest. Something I’d actually be proud to build.”

Saves it.

Looks at it.

Thirty-eight ideas now.

None of them built. All of them requiring him to leave this comfortable cage.

David closes the laptop.

Stands at the window. The city glows below. Thousands of people in their apartments. Some happy. Some miserable. Most just—getting by.

David is getting by.

Good salary. Good apartment. Good career.

Building things he’s ashamed of.

For the first time in three years, the math doesn’t work. The paycheck doesn’t justify the emptiness. The comfort doesn’t justify the cost.

Something has cracked.

Not broken. Not yet.

But cracked enough that he can see light through it.

Light, or an exit.

He’s not ready to walk through. The fear is too big. The salary too necessary. The path forward too unclear.

But he sees it now.

The door he’s been pretending doesn’t exist.

The possibility of leaving.

Of building something honest.

Of becoming the person sixteen-year-old David thought he’d be.

Not yet. But soon.

The crack is spreading.

That night, David dreams about slot machines.

He’s pulling a lever. Over and over. Sometimes he wins. Mostly he doesn’t.

He wants to stop but can’t. His hand keeps moving.

Behind him, a line of people waiting for their turn. All of them pulling levers. All of them unable to stop.

He built the machines. He knows how they work. He designed them to be impossible to quit.

And now he’s trapped in one.

David wakes at 3 AM. Sweating. Heart racing.

The apartment is dark. Silent.

He lies in bed. Staring at the ceiling.

Tomorrow he’ll wake up. Badge in. Sit through meetings. Write code that makes the metrics go up.

The comfortable routine.

But tonight, in the dark, David knows something he can’t unknow:

He’s in a cage. And he built it himself.

One feature at a time.

One compromise at a time.

Until the salary bought his silence and the benefits bought his complicity and the comfort bought his soul.

Not dramatically. Quietly.

The way most people sell themselves.

For something safe.

Something reasonable.

Something slow and painless enough that you don’t notice until it’s too late.

But now David notices.

And he can’t stop noticing.

The crack is there.

Growing.

Waiting.

End of Chapter 3

Chapter 4: The First Month

Mon, 10 Nov 2025 00:00:00 GMT

Chapter 4: The First Month

The coffee shop is half-empty at 9 AM. Too late for the morning rush, too early for the laptop crowd.

David arrives first. Orders a drip coffee. Finds a table by the window where he can watch the door.

His laptop bag feels heavier than usual. Inside: three years of corporate belonging, now just a tote bag of personal items. The coffee mug. The fidget cube. A notebook he never used.

Alex walks in at 9:03. Hair still wet from the shower. He scans the room, finds David, waves.

They haven’t seen each other in person for—what? Four months? Six? The last few times they tried to meet up, something always came up. Sprint planning. Quarterly reviews. Seattle trips.

Alex orders at the counter. Returns with something complicated—oat milk latte with extra espresso. Sits down across from David.

“So.” Alex’s smile is careful. “How are you holding up?”

David wraps his hands around his coffee cup. The ceramic is warm. “I’m good. Actually good.”

“Yeah?” Alex studies his face. “You don’t look devastated.”

“I’m not.”

The silence stretches. Outside, a bus hisses to a stop. Passengers board. The bus pulls away.

“Okay,” Alex says slowly. “I’ll bite. Why aren’t you devastated?”

David opens his laptop. The product spec from yesterday is still there. Eight thousand words. He’s added another two thousand since he got home last night.

“I want to show you something.”

He turns the screen toward Alex. Watches his friend’s eyes scan the document. The title: “Learning Companion - Full Product Spec.”

Alex reads for two minutes. Three. His expression shifts from polite interest to actual focus.

“You wrote this yesterday?”

“Started it at my desk. Before they deactivated my access. Kept going at a coffee shop after the exit interview. Finished around midnight.”

“Ten thousand words in one day.”

“About that.”

Alex scrolls down. Past the problem statement, the user personas, the technical architecture notes. “David, this is—” He pauses. “This is really detailed.”

“I know the idea isn’t perfect. There are gaps. The monetization strategy is weak. I haven’t validated any of the assumptions. But—”

“But you want to build it.”

It’s not a question. David nods anyway.

Alex leans back. Takes a sip of his latte. “Okay. Walk me through it. From the top.”

David feels something unclench in his chest. Not “this is a terrible idea.” Not “you should focus on finding another job.” Just—walk me through it.

He starts talking.

About the education system that sorted him and Marcus like products. About spending six years building features nobody needed while the real problems stayed unsolved.

About thirty-eight ideas gathering dust because he was too afraid.

About the layoff feeling like permission. Like the universe hitting him with a brick.

Alex listens without interrupting. When David finishes, they sit in silence for a moment.

“You know the statistics,” Alex says finally. “Nine out of ten startups fail.”

“I know.”

“You have—what—six months of runway with severance?”

“Four, realistically. Less if I’m not careful.”

“Your mom is going to lose her mind.”

David’s coffee has gone cold. “Yeah.”

“And you still want to do this.”

“Yeah.”

Alex sets down his cup. “Then I’m in.”

David blinks. “What?”

“I’m in. As a co-founder. If you’ll have me.”

“Alex—”

“Look, I’ve been at TechCorp for four years. Every quarter they promise the work will get more interesting. It never does. I’m building recommendation algorithms for ads nobody clicks. My manager just told me I’m ‘exceeding expectations.’ I wanted to throw my laptop out the window.”

“You have a good job. Stable income. You didn’t just get laid off.”

“I know. But I also know that if I don’t do this now, I’ll be fifty years old wondering what would have happened if I’d been brave enough to try.” Alex pauses. “We were roommates for three years. I know how you think. How you work. We’re good together.”

“This could fail spectacularly.”

“Probably will.”

“We could lose everything.”

“Yep.”

“Your parents—”

“Will be disappointed. Same as yours. We’ll survive.” Alex grins. It’s not a comfortable grin. It’s the grin of someone jumping off a cliff. “So. Are we doing this?”

David looks at his laptop. The product spec. Ten thousand words about something that doesn’t exist yet.

His mother’s voice echoes in his head: Your father and I didn’t sacrifice everything so you could throw away stability.

His father’s quiet disappointment when David told him about the layoff: What will you do now?

The statistics. Nine out of ten. Probably fail.

He thinks about sixteen-year-old David on those library steps. Carrying that small, quiet yearning. Wondering if there was another way to live.

“Yeah,” David says. “We’re doing this.”

Alex extends his hand across the table. David shakes it. Neither of them says anything. The handshake lasts maybe three seconds.

It feels like stepping through a door that locks behind you.

Three weeks later.

Two IKEA desks assembled at midnight. Two monitors. One whiteboard: “MVP Complete: May 15.”

Alex moved in last week—not officially, but his laptop lives on the second desk now. They work fourteen hours a day because they can’t stop.

David’s severance plus Alex’s savings: eight months of runway if they’re brutally careful.

Eight months to learn if the vision is real.

At TechCorp: processes, committees, risk reduction. Here: just building.

Alex on backend. David on frontend and ML. They argue, compromise, change minds, argue again.

Messy. Inefficient. The most alive David has felt in years.

2 AM. His mother texts: How’s the job search?

Behind him, Alex debugs API timeouts.

They haven’t told their parents. David said “exploring opportunities.” Alex said “figuring things out.” Both lies by omission.

Still interviewing, David types.

The algorithm he’s building adapts to learning styles—visual, auditory, kinesthetic. The problem: it guesses. They need real users. Can’t get users without a working product. Can’t have a working product without users.

“We’re building in the dark,” David says.

“Then we’ll find out and adjust,” Alex says. “That’s more than most people do.”

David wants to argue. But Alex is already back to debugging.

A LinkedIn notification: someone from TechCorp got promoted. David dismisses it.

Three weeks in. Balance dropped from $47,000 to $43,200. Rent, food, desks, coffee sessions—hemorrhaging faster than expected.

Severance pays out $2,500 every two weeks. Helps. Won’t last.

He opens a spreadsheet. Rent: $1,600. Food: $800. Utilities: $150. Total burn: $3,500/month.

Current savings plus remaining severance: $58,200. Realistic runway: ten months. Maybe twelve if ruthless.

Ten months to build, test, find product-market fit, generate revenue.

Or be thirty, broke, explaining to his mother why he wasted his prime years chasing a dream.

Outside, 3 AM darkness. Normal people asleep with normal jobs.

David could still go back. Update LinkedIn. Two weeks to offers. Different company, same cage.

He looks at the code. Not done. Might never work. But his.

He starts typing. One line. Then another.

Alex falls asleep on the couch at 4 AM. David covers him with a blanket. Makes more coffee.

The algorithm tries to predict learning preferences from behavior. Visual, auditory, kinesthetic. Simple in theory. Impossible in practice. Full of assumptions and guesses.

But it’s a start.

First light at 6 AM. Grey. Cold. March.

David saves. Closes the laptop. Two desks, cables, coffee cups. Alex asleep. Boxes still unpacked from eight months ago.

This is his life now.

His mother texts: Your aunt’s friend’s company is hiring.

Still looking, he types. Lying comes easier.

Before sleeping, he opens the product spec one last time:

“An education system that asks what you’re curious about, not just what you’re supposed to know.”

Somewhere is a kid like Marcus. Losing a race they never wanted to run.

What if there was a way out?

David closes the laptop. Falls asleep on the floor, jacket as pillow.

Wakes five hours later. Alex making coffee: “Ready for authentication flow?”

Back hurts. Neck stiff. Mouth tastes like regret.

“Yeah,” David says. “Let’s do it.”

They work until sunset. One day closer to running out of money. One day closer to something real.

Or to admitting it was a mistake.

Can’t know yet.

So he keeps building.

End of Chapter 4

Chapter 5: The Cracks

Mon, 10 Nov 2025 00:00:00 GMT

Chapter 5: The Cracks

Three months in. May.

David’s checking account: $38,950.

The number sits on his phone screen. He refreshes the banking app. Still $38,950.

He’s been careful. Brutally careful. Rice and eggs. No coffee shops unless he’s meeting someone. The heat stays off even when the apartment is cold. He walks instead of taking the subway when he can afford the time.

The last severance payment came two weeks ago. That safety net is gone now.

Still. Three months. Nearly nine thousand dollars gone from savings, even with the severance cushion.

At this rate: eight months left. Maybe ten if he stops eating out entirely.

The calculator in his head runs constantly now. Every purchase translated into days of runway. That sandwich: half a day. New headphones to replace the broken ones: three days. The domain name renewal: two days.

His mother texted yesterday: Your cousin just bought a condo. Two bedrooms.

David didn’t respond.

The prototype is almost done. That’s what they tell themselves.

“Almost done” has meant different things over the past month. First it meant “core features working.” Then “ready for internal testing.” Now it means “showable to real users without it crashing immediately.”

The bar keeps lowering.

David sits at his desk—the IKEA desk that cost three days of runway—staring at the adaptive learning algorithm. It’s supposed to detect how students learn. Visual, auditory, kinesthetic. Fast-paced or deliberate.

The problem: it’s guessing. Badly.

He runs the simulation again. A test student clicks on a video. The algorithm decides: visual learner. Serves more videos. The student skims the text quickly. The algorithm adjusts: prefers text, fast-paced.

But what if the student clicked the video because the text was poorly written? What if they skimmed because they were bored, not because they prefer fast-paced content?

The algorithm can’t tell the difference. It just guesses and hopes.

David closes the file. Opens it again. Stares at the code.

Behind him, Alex is on a video call with a potential beta tester—a teacher friend from college. David can hear half the conversation.

“Yeah, we’re targeting high school students initially… Personalized learning paths… Uses AI to adapt to how each person learns best…”

The words sound good. Polished. Like they know what they’re doing.

David returns to the algorithm. Changes a parameter. Runs the test again. Slightly better. Still guessing.

He changes it back.

At 7 PM, they order pizza. Too expensive, but neither of them has eaten since breakfast and the code isn’t working and they need something.

Alex pays. David doesn’t argue. He’s started keeping a mental tally of who pays for what. Alex has paid for the last four meals. David paid for the domain and hosting. Alex covered the API costs. David bought the whiteboard.

They don’t talk about it. But the scorecard exists.

They eat in silence for a few minutes. The pizza is mediocre. David eats three slices anyway.

“I think we should push back the user testing,” Alex says.

David looks up. “We’re already behind schedule.”

“I know. But the prototype isn’t ready. If we show it now and it crashes—”

“It won’t crash. The core functionality works.”

“The adaptive algorithm—”

“—will improve with real data. We can’t get real data without real users.”

Alex sets down his pizza. “David. It’s not good enough yet.”

The words hang in the air.

Not good enough.

David knows he’s right. The prototype is held together with duct tape and optimism. The UI is clunky. The algorithm guesses more than it learns. It crashes if you click certain buttons in the wrong order.

But if they wait longer, they burn more savings. More days off the runway. And for what? To make it slightly less broken?

“How much longer do you want to wait?” David asks.

“Two weeks. Maybe three.”

“That’s a thousand dollars.”

Alex pauses. “I know.”

“Do you? Because I’m looking at my account every morning and watching it go down and we haven’t made a single dollar yet. We haven’t validated anything. We’re just building in the dark and hoping.”

“So what do you want to do? Show them something broken?”

“I want to find out if we’re building the right thing. Before we run out of money building the wrong thing.”

The silence is different now. Heavier.

Alex picks up another slice. Doesn’t eat it. “Okay. When?”

“Next week. I’ll recruit the testers.”

“How many?”

“Ten. Maybe twelve.”

“High school students?”

“Yeah.”

Alex nods. Sets down the pizza. “Then we better fix the button crash bug.”

David spends the next three days recruiting. He posts in local education forums. Reaches out to teachers he vaguely knows from college. Offers $25 gift cards to participants.

Twelve students sign up. Ages 14 to 17. Mix of school backgrounds.

The sessions are scheduled for Saturday. Two weeks earlier than planned. Three weeks later than David wanted.

The compromise that satisfies no one.

Thursday night, David stays up until 4 AM fixing bugs. The button crash. The infinite loading screen. The feature that accidentally deletes user progress.

He makes a list of things that are still broken:

Algorithm guesses too much
UI confusing on mobile
Content library too small
Onboarding flow skips steps randomly
No way to track actual learning outcomes
Sometimes serves the same question three times in a row

He stares at the list. Closes his laptop. Opens it again.

Adds:

Might not solve the actual problem

Friday evening. Alex leaves around 6 PM—his mother’s birthday dinner. David says he’ll keep working on the prototype.

He does, for about an hour. Then he stops.

Opens his banking app. $37,200.

Opens LinkedIn. Scrolls through updates. Someone from his old company just got promoted. Senior Staff Engineer. David wonders what the salary is. $300k? $350k?

He closes LinkedIn. Opens his email.

Three unread messages from his mother. He’s been avoiding them. He knows what they say without reading. Questions about the job search. Suggestions about companies hiring. Worry disguised as helpfulness.

He opens the most recent one anyway.

Your father is asking about health insurance. When you get a new job, make sure they have good coverage. Remember when you needed that specialist? Don’t pick a plan with high deductibles.

David closes the email.

She doesn’t know he’s not looking for jobs. Doesn’t know he’s building something. Doesn’t know he’s choosing this.

He’s still telling her he’s “interviewing.” The lie gets easier each time.

His phone buzzes. Alex.

How’s it going?

David looks at his screen. The prototype is open. He hasn’t touched it in twenty minutes.

Good. Fixed two bugs. Should be ready for tomorrow.

Nice. Get some rest.

David puts the phone down. Looks around the apartment.

Two desks. Two chairs. Cables everywhere. The whiteboard covered in diagrams that made sense two weeks ago. Empty coffee cups. A blanket on the couch where Alex crashed last Tuesday.

This is his life now. This is what he chose instead of $300k and good health insurance.

He opens the prototype. Runs through the user flow one more time. Clicks through the screens. Everything works. Mostly.

Tomorrow they’ll find out if it matters.

Saturday. 10 AM.

Coffee shop private room. David early. Alex brings coffee.

“Ready?”

Not ready.

First student, 17, wants to study CS. Clicks around fifteen minutes. Feedback: “It’s cool. Kind of like Khan Academy?”

David’s chest tightens.

Second student, 15, struggles with math: “Pretty similar to stuff at school. They all kind of feel the same.”

Third: “Like a homework app.”

Fourth: “Reminds me of Duolingo.”

Fifth: “I probably wouldn’t use it unless I had to.”

By the sixth session, David stops taking notes. He knows what’s coming.

The seventh student is fourteen. Quiet. Barely makes eye contact. She uses the prototype for ten minutes without saying anything.

When they ask for feedback, she pauses.

“It’s okay.”

David waits. Something in her hesitation feels different.

“Was there anything you liked about it?” Alex asks.

She picks at her thumbnail. “I guess… there was that part at the beginning where it asked what I’m curious about.”

David leans forward slightly. “The onboarding questions?”

“Yeah. Like, it asked what I actually want to learn. Not what I’m supposed to learn.” She shrugs. “No one ever asks that.”

“Did it feel useful?”

“I mean, I don’t know. I just typed something random because I didn’t think it actually mattered. Does it?”

David and Alex exchange a glance.

“It’s supposed to,” David says. “To personalize what you see.”

“Oh. That’s cool.” She looks back at the screen. “The rest of it kind of felt like homework though.”

They thank her. She leaves.

Alex closes his laptop. The coffee shop is getting crowded—Saturday afternoon rush. They have six more sessions scheduled.

“She liked the curiosity question,” Alex says.

“She typed something random because she didn’t think it mattered.”

“But the idea resonated. That’s something.”

David doesn’t respond. His phone buzzes. Reminder: Next session in 10 minutes.

They do the remaining six sessions. The feedback blurs together.

It’s fine. It’s okay. It’s like the other apps. I’d maybe use it. Probably not. It’s cool, I guess.

At 6 PM, they’re done. Twelve sessions. Two hundred dollars in gift cards. Six hours of feedback.

They pack up in silence. Walk back to David’s apartment. The spring evening is warm. People are out—couples, families, groups of friends heading to dinner.

David and Alex walk without talking.

Back at the apartment, Alex sits on the couch. David stands by the window.

“So,” Alex says finally. “That was rough.”

“Yeah.”

“Not all bad though. The girl who liked the curiosity question—”

“One person. Out of twelve. And she still said the rest felt like homework.”

“It’s a first prototype. We can iterate.”

David turns from the window. “Into what? Another homework app? Another Khan Academy clone? They all kind of feel the same, apparently.”

“We just need to figure out what makes it different.”

“I thought we knew what made it different. We spent two months building it.”

Alex is quiet for a moment. “David. This is part of the process. User feedback. Iteration. It’s—”

“Don’t.” David’s voice is flat. “Don’t give me the startup playbook speech. I know the process. I know we’re supposed to embrace failure and iterate quickly and all that bullshit. But we just spent eight thousand dollars to build something twelve people said feels exactly like everything else.”

The words sit in the air.

Alex stands up. “I’m going to head out. Give you some space.”

“You don’t have to—”

“Yeah, I do. We’re both tired. Let’s regroup tomorrow.”

Alex grabs his jacket. Stops at the door. “For what it’s worth, I still think we’re onto something. We just haven’t found it yet.”

He leaves.

David stands alone in the apartment. The whiteboard mocks him. “MVP Complete: May 15” is still written at the top in blue marker. Below it, the timeline that seemed optimistic six weeks ago now seems delusional.

He opens his laptop. Pulls up the feedback notes.

Twelve users. One semi-positive comment about the curiosity question. Eleven variations of “it’s like everything else.”

His phone buzzes. His mother.

Have you heard back from any interviews? Your father knows someone at Microsoft if you need an introduction.

David sets the phone face-down.

Opens his banking app. $36,800.

Two hundred dollars for gift cards. Eighty dollars for the coffee shop. Twenty-two days of work. Eight thousand dollars in savings.

To build another homework app.

He closes the laptop. The apartment is dim—he never turned on the lights. The city glows through the window. Out there, people are having normal Saturday nights. Dinner. Movies. Drinks with friends.

David sits on the floor. Back against the couch. The ceiling has a crack he’s never noticed before.

His phone buzzes again. He ignores it.

The prototype is open on his laptop. The screen has dimmed to save battery. He can barely see it in the dark.

He doesn’t open it again.

Just sits there. In the dark. As the city continues outside and the crack in the ceiling stays unnoticed and the savings account ticks down and twelve people’s voices echo:

It’s like everything else.

They all kind of feel the same.

Another homework app.

The cursor blinks on the black screen.

David closes his eyes.

End of Chapter 5

Chapter 6: The Descent

Mon, 10 Nov 2025 00:00:00 GMT

Chapter 6: The Descent

June arrives without ceremony.

David’s checking account: $31,400.

May was expensive. The user testing. The realization that twelve people saw his three months of work as “just another homework app.” The week after where he paid for API access to better ML models, convinced that better technology would solve what was actually a vision problem.

It didn’t.

The second iteration started two weeks ago. Not a pivot—Alex keeps using that word and David keeps flinching—just a rethinking. A fundamental rethinking.

What did that girl say? “No one ever asks what I’m curious about.”

She typed something random because she didn’t think it mattered.

The problem wasn’t asking the question. The problem was that the product didn’t make it feel like it mattered. The curiosity question was tagged on—a nice-to-have feature, not the foundation.

So they’re rebuilding. Again.

David opens the new prototype. The interface is simpler now. Stripped down. When you first open it, there’s just one question:

“What do you actually want to learn about?”

No multiple choice. No suggested topics. Just an empty text box and the assumption that what you type matters.

Then—and this is the part they’re still figuring out—the entire learning path restructures around that answer. Not just serving related content. Actually building a curriculum that starts with curiosity and expands outward.

In theory, it’s beautiful.

In practice, it requires a content library they don’t have, an algorithm that doesn’t exist, and a level of personalization that probably needs ten times more engineering hours than they can afford.

David adds a comment to the code: // TODO: Figure out how to make this actually work

His phone buzzes. Rent reminder. Due in three days.

$1,600.

After rent: $29,800.

The math runs automatically now. A constant background process. Every purchase converted to days of runway. That coffee: 0.4 days. The sandwich: 0.6 days. The domain renewal: 1.8 days.

His mother called yesterday. He didn’t answer. She left a voicemail he hasn’t listened to.

The lie about interviewing is getting harder to maintain. How many months can you be “in final rounds” at companies before someone asks why you haven’t gotten an offer yet?

Alex arrives around noon with groceries. Eggs, rice, vegetables. Cheap protein. They’ve stopped ordering delivery. Stopped going to coffee shops unless it’s for a meeting.

“Got an email from Marcus,” Alex says, unpacking the bags.

Marcus. The guy from David’s high school. The one who got 94 instead of 98.

“He’s a PM at Google now,” Alex continues. “Asked if we wanted to grab lunch sometime. Catch up.”

David doesn’t look up from his screen. “What did you say?”

“That we’re busy. Didn’t mention why.”

“Good.”

Marcus wouldn’t understand. Would probably be supportive in that way people are when they think you’re making a mistake but are too polite to say it directly. Would talk about how great it is that they’re “taking the leap” while mentally calculating how much salary they’re missing out on.

David has started avoiding people. Old coworkers. College friends. Anyone who might ask how it’s going.

Because how is it going?

They’ve been at this for four months. Four months. They have a half-broken prototype that’s barely better than the first one. Zero users. Zero revenue. Zero validation that any of this matters.

They have diagrams on a whiteboard and code that crashes and a vision that sounds increasingly delusional when David tries to explain it at 3 AM.

“I think the content graph is wrong,” David says.

Alex looks up from chopping vegetables. “Which part?”

“All of it. We’re still thinking in terms of subjects. Math, science, history. But curiosity doesn’t work that way. A kid might be curious about how airplanes fly, which touches physics and engineering and materials science and history. The traditional subject boundaries are the problem.”

“Okay. So we need a different content structure.”

“We need to rebuild the entire data model.”

Alex sets down the knife. “How long?”

“Two weeks. Maybe three.”

“We don’t have three weeks, David. We need to test this iteration.”

“We can’t test it if the foundation is wrong.”

“We also can’t wait forever for it to be perfect.”

The same argument they’ve had four times this week. Different words, same collision.

David closes his laptop. Harder than necessary. “It’s not about perfect. It’s about not wasting people’s time with something that doesn’t actually solve the problem.”

“And how do we know what solves the problem if we don’t talk to users?”

“We talked to users. Remember? They said it feels like everything else.”

“That was the first iteration—”

“This is barely different! We’re still serving content the same way. We’re still assuming we know what ‘personalized learning’ means. We’re still—”

David stops. Takes a breath.

Alex is right. They can’t build in a vacuum forever. But Alex is also wrong. Shipping something broken just to ship something is how you get Khan Academy clones.

“Two weeks,” David says. “Give me two weeks to rebuild the content model. Then we test. Deal?”

Alex looks at him for a long moment. “One week. That’s all we can afford.”

“One week isn’t—”

“One week. Or I’m recruiting testers on Friday whether you’re ready or not.”

David wants to argue. But the look on Alex’s face says the conversation is over.

“Fine. One week.”

The week is brutal.

David works sixteen-hour days. The content model needs to be deconstructed—not subject-based but concept-based. Everything interconnected. A kid curious about airplanes should naturally flow into Bernoulli’s principle, which connects to fluid dynamics, which connects to weather patterns, which connects to climate science.

Every topic a node. Every connection weighted by curiosity-distance, not curriculum-distance.

The code sprawls. David writes classes, then rewrites them. The database schema changes three times in four days.

On Wednesday night, he realizes the entire approach requires a knowledge graph they don’t have time to build. Even if they narrow the scope to just a few topics—say, starting with twenty core curiosity areas—they’d need hundreds of hours of content curation.

They don’t have hundreds of hours. They have days.

David sits back in his chair. Stares at the ceiling. The crack on the ceiling isn’t visible in this light, but he knows it’s there.

“It’s not going to work,” he says.

Alex looks over from his desk. “What’s not going to work?”

“The knowledge graph. We don’t have the resources to build it properly. Not with the quality it needs.”

“So we scope it down.”

“I’ve already scoped it down. It’s still too big.”

“Then we scope it down more.”

“At what point does scoping it down just mean we’re building another mediocre product?”

Alex closes his laptop. Turns to face David. “You want to know what I think?”

“Not really.”

“I think you’re scared.”

David laughs. No humor in it. “Of course I’m scared. We’re four months in and we have nothing.”

“We have a vision. We have a prototype. We have—”

“We have $31,000 in savings and no path to revenue. That’s what we have.”

The silence sits heavy.

Alex stands up. Walks to the whiteboard. Picks up a marker.

“What are you doing?” David asks.

“Making a list.” Alex writes at the top: “Things We Actually Need to Test.”

He draws a line. Writes below it:

Does the curiosity question resonate?
Do users engage more when content follows their interests?
Does the app feel different from homework?

“That’s it,” Alex says. “That’s what we need to learn. Everything else—the perfect knowledge graph, the sophisticated content model—that comes later. First, we validate the core assumption: that people actually want this.”

David stares at the list.

“We can fake the knowledge graph,” Alex continues. “For ten users, we can manually curate twenty curiosity paths. It won’t scale, but it’ll tell us if we’re onto something.”

“Manually curate—”

“Yes. You and me, spending forty hours building twenty really good curiosity journeys. Aviation. Cooking. Music production. Whatever. We show them to users. We watch what happens.”

“That’s not sustainable—”

“It’s not supposed to be sustainable. It’s supposed to answer the question: should we keep going?”

David looks at the whiteboard. Then at his laptop. The half-built knowledge graph system that would take another three weeks minimum.

Alex is right. Much as David hates it, Alex is right.

“Forty hours,” David says. “We can curate twenty paths in forty hours?”

“If we focus. No perfectionism. Just good enough to test the concept.”

David nods slowly. “Okay. Let’s do it.”

They spend the next four days building content paths.

Not writing original content—they don’t have time for that. Curating. Finding the best YouTube videos, articles, interactive simulations. Stringing them together into journeys that feel organic, not prescribed.

David takes: How Airplanes Fly, The History of Video Games, Understanding Climate Change, How the Brain Works.

Alex takes: Music Production, Why Empires Fall, The Science of Cooking, Introduction to Machine Learning.

They work in parallel. Sometimes they share screens, debating whether a particular video is too basic or too advanced. Sometimes they work in silence, just the sound of clicking and typing.

On Saturday night, they have sixteen curiosity paths done. They’re exhausted. David’s eyes hurt from screen time. His back aches from too many hours in the chair.

“Four more,” Alex says. “We can finish tomorrow.”

David looks at the clock. 11 PM.

“Yeah. Tomorrow.”

He saves his work. Closes his laptop.

Alex heads to the couch—he’s been sleeping here more often than at his own place. David walks to the window.

The city is alive on a Saturday night. People out there living normal lives. Dates. Parties. Friends grabbing drinks.

David hasn’t seen anyone outside of Alex in two weeks. Hasn’t been to a party in—when? Six months? Longer?

His college friends have stopped texting. Or maybe he stopped responding. The line is blurry.

He pulls out his phone. Opens his mother’s voicemail from earlier this week. Presses play.

Her voice fills the quiet apartment: “David, it’s your mother. You haven’t called in three weeks. I’m worried. Your father is worried. Are you eating? Are you taking care of yourself? Please call me back. I need to know you’re okay.”

Not angry. Just worried.

David deletes the voicemail. Opens his messages. Types: Sorry I’ve been quiet. Job search is taking longer than expected but I’m okay. Will call soon.

Send.

Another lie. The collection keeps growing.

He looks at his banking app. $29,950. Rent paid. Food and groceries: $400. API costs: $89. Domain renewals: $36. Coffee: $47 (he’s trying).

The number drops every day. A timer counting down.

But then David thinks about the curiosity paths they’ve built. The one about how airplanes fly that starts with a simple question—why don’t planes fall?—and naturally spirals into Bernoulli’s principle, then fluid dynamics, then the history of aviation, then modern aerospace engineering.

A kid who starts curious about one thing ends up learning about ten things. Not because they were forced to. Because the connections were beautiful.

That’s what he’s building. Not another homework app. Something that treats curiosity as the foundation, not a feature.

He doesn’t know if it’ll work.

But for the first time in weeks, he feels something other than dread.

Sunday they finish the last four paths. By 6 PM, they have twenty complete curiosity journeys. Each one curated, tested, refined.

Alex leans back. “That’s it. We’re done.”

“Now we integrate them into the prototype.”

“How long?”

David thinks. “Two days to wire everything up. Another day for testing and bug fixes.”

“So Wednesday we’re ready to show people.”

“Yeah. Wednesday.”

Alex grins. It’s the first genuine smile David’s seen from him in weeks. “We actually did it.”

“We built twenty content paths. We haven’t validated anything yet.”

“One step at a time, man. One step at a time.”

They order pizza. Too expensive, but they haven’t eaten all day and they’re both too tired to cook. They eat in front of the TV—something they haven’t done in months. Some comedy special neither of them pays attention to.

David’s phone buzzes. LinkedIn notification. Someone from his cohort at TechCorp just got promoted to Staff Engineer.

He dismisses it without reading the details.

“You ever think about going back?” Alex asks.

“To where?”

“Corporate. The safe path.”

David takes another bite of pizza. Chews slowly. “Every day.”

“Yeah?”

“Yeah. Every time I check my bank account. Every time my mother calls. Every time I think about how much easier everything would be if I just—” He pauses. “But I can’t. I don’t think I could breathe in that world anymore.”

Alex nods. Doesn’t say anything.

They finish the pizza in silence. Clean up. Get ready for bed.

David sets his alarm for 8 AM. Tomorrow they start integration. Wednesday they test.

One more iteration. One more chance to find out if this vision is real or just expensive delusion.

Before he closes his eyes, he opens the prototype one last time. Looks at the curiosity question interface.

“What do you actually want to learn about?”

Simple. Direct. Hopeful.

Maybe it’ll work. Maybe kids will type something real instead of something random. Maybe the content paths they’ve built will feel magical instead of mechanical.

Maybe.

David closes the laptop.

Falls asleep thinking about airplanes and curiosity and mothers who worry and visions that might—if he’s lucky—mean something.

Monday and Tuesday blur together.

Integration work. David wires the twenty curiosity paths into the prototype. Alex builds the backend systems to serve them. They test flows. Fix bugs. Break things. Fix them again.

By Tuesday night, they have something showable. Not perfect. But functional.

“We should recruit testers for Thursday,” Alex says.

“Thursday? That’s two days.”

“I know some high school teachers. I can ask if their students want to participate.”

David hesitates. The familiar fear creeping back. What if it’s not ready? What if they test too early again?

But Alex is looking at him with that expression that says: we have to jump sometime.

“Okay,” David says. “Thursday.”

Alex starts emailing. David watches their savings account tick down.

$28,100.

June is almost over. Four months since the layoff. They’ve burned through nearly $37,000.

For what? Two failed prototypes and twenty curated content paths.

David’s mother calls. He lets it go to voicemail again. Can’t handle her voice right now. Can’t handle the questions.

Instead, he opens the code.

At 1 AM on a Tuesday in June, something shifts.

David is debugging the curiosity path for “How the Brain Works.” A small bug—the content sequence sometimes skips the second video. Barely noticeable. Most engineers would ship it. Call it edge case. Move on.

But David can’t.

The flow has to be right. When someone asks “how do thoughts happen,” the journey from neuron basics to synaptic communication must feel inevitable. Like discovering a path through woods that was always there, just hidden.

He traces through the code line by line. The content sequencer—three hundred lines of logic determining what to show next based on user behavior, curiosity patterns, comprehension signals.

There. Line 247. A malformed conditional. The boolean logic checks for video completion status but fails to account for users who pause mid-video to think. So it skips ahead, thinking they’re bored.

But what if they’re not bored? What if they’re thinking?

David rewrites the conditional. Adds a timer threshold. If paused less than thirty seconds: likely thinking. More than two minutes: likely bored or distracted.

He tests it.

The flow works. Opens the path from the beginning.

First screen: “How do thoughts actually happen?”

Not “What are neurons?” Not “Introduction to neuroscience.” The question a curious person would actually ask.

Click. The interface responds.

An animation loads—beautiful, simple. A single neuron rendered in gentle blues and whites. It pulses softly, like breathing.

Text appears beneath: “Right now, as you read this, 86 billion of these are working together to create your experience of reading. Let’s see how.”

The animation zooms in. Shows the synapse—the gap between neurons. A tiny space, impossibly small. The text explains without lecturing: “Thoughts are electrical signals jumping across spaces smaller than you can imagine.”

David watches the flow. The pacing. How each element builds on the last without rushing.

Next: a video. A researcher explains synaptic firing. Not dry. Excited. Like someone sharing a secret. “When you learn something new, these connections physically change. You’re literally rebuilding your brain right now.”

The video ends at exactly the right moment—before boredom, after understanding.

Then: an article on neuroplasticity. The text is clean, scannable. Key phrases highlighted. “Your brain isn’t fixed. It’s a garden you’re constantly tending.”

David realizes his face hurts.

He’s smiling.

Actually smiling. Not the performative smile of meetings. Not the polite smile of small talk. The private smile of someone alone with something beautiful.

When was the last time he smiled while working?

He thinks back. Not at TechCorp. Not once. Three years of code reviews and sprint planning and quarterly OKRs and not a single moment of actual joy in the craft itself.

But here. Now. At 1 AM in a cold apartment with $27,000 in savings and no idea if this will work.

He’s smiling.

He opens the curiosity path again from the start. Watches the whole sequence. The animation, video, article. Then the branches—connections to memory, to learning, to consciousness. Each path carefully curated. Each transition weighted so it feels like discovery, not instruction.

This is what he’s been trying to build. Not another way to deliver content. A way to make curiosity feel like it matters. Like following your interest isn’t deviation from learning—it is learning.

David leans back. The chair creaks. His neck is stiff. His eyes burn from screen time. The apartment is cold—he hasn’t turned on heat in weeks to save money.

But none of that touches him right now.

He opens another path. “Why do we dream?” Watches it unfold. The same attention to flow. The same care in sequencing. Someone curious about dreams naturally flows into REM sleep, into memory consolidation, into creativity, into the mystery of consciousness itself.

Then “How Music Works”—from “why do some songs make me feel things” to sound waves to frequency to emotion to culture to neuroscience.

Each path a doorway. Each curiosity honored.

David is not thinking about users or revenue or whether this will work. He’s not calculating runway or worrying about his mother or fearing failure.

He’s just… here. Present. Experiencing the thing he made.

And it’s beautiful.

Not perfect. The animations could be smoother. Some transitions feel slightly forced. The content library is still thin. There are bugs he hasn’t found yet.

But the essence—the core idea that curiosity itself is worth honoring—it’s there. Alive in the code. Visible in the flow.

He thinks about why he learned to code. Seventeen years old, first computer science class. The teacher showed them how to make text appear on screen. “Hello World.”

Stupid simple. But magic. You write words in one language, the computer translates them to another, and something happens. Creation from thought.

That feeling—the joy of making something from nothing—he’d chased it through college, through job interviews, through three years at TechCorp.

And lost it. Somewhere in the sprint planning meetings and A/B tests for button colors and features nobody asked for, the joy leaked out.

But it’s back now.

Not because this will succeed. Not because people will use it. But because the work itself—the craft of building something well, the art of making complex ideas feel simple, the satisfaction of solving problems elegantly—is its own reward.

The difficulty isn’t burden. It’s the point.

He spent three years making things easy and feeling empty. Now he’s making something hard and feeling alive.

Life has become amazingly enjoyable. Not despite the difficulty. Because of it.

David opens another path. Then another. Not testing functionality. Just experiencing them. Like walking through a garden he planted.

Around 3 AM, his hands stop moving across the keyboard. He’s just watching now. The way the knowledge graphs bloom when someone types a question. The way connections draw themselves. The way curiosity becomes visible.

A kid using this won’t just read about neurons. They’ll see their question matter. They’ll watch the answer unfold in response to their specific curiosity. They’ll feel, maybe for the first time, that what they wonder about is valuable enough to build entire worlds around.

That’s what he’s been trying to create since the first failure. Since “it feels like everything else.” Since the girl who typed something random because she didn’t think it mattered.

He’s showing them it does matter.

Tears surprise him. Not sad. Not happy exactly. Something else. The overwhelming recognition of being exactly where you’re supposed to be, doing exactly what you’re meant to do, even when nothing makes sense.

Especially when nothing makes sense.

This is the goddess. Not a person. Not success. This: the reconnection with why. The alignment of work and soul. The love of craft returning after years of exile.

Three months burning through savings to find this feeling. Worth it.

At 4 AM, Alex wakes up on the couch. “You still working?”

“Yeah.”

“You should sleep.”

“I know.”

But David doesn’t close his laptop. He keeps refining. Keep polishing. Not chasing perfection—just making it a little bit better. Then a little bit better again.

Alex watches him for a moment. Then gets up, makes coffee. Sits down at his own laptop.

“What are you doing?” David asks.

“If you’re working, I’m working.”

They code in silence. The city dark outside. The world asleep except for them and whoever else is crazy enough to build things at 4 AM on a Wednesday.

First light comes around 6.

David saves his work. Stretches. His neck cracks. His eyes burn.

“It’s good,” he says.

“Yeah?”

“Yeah. It’s actually good.”

“Think people will like it?”

“I have no idea.” David grins. It feels strange on his face. Like a muscle he forgot he had. “But I like it. For the first time, I actually like what we built.”

Alex nods. “That’s something.”

“Yeah. That’s something.”

They sleep for three hours. Wake up to the alarm. Test the prototype one more time.

Tomorrow they’ll show it to real users. Tomorrow they’ll find out if anyone else sees what they see.

But today—right now—David feels something he hasn’t felt since this started.

Not confidence. Not certainty.

Just love.

Love for the craft. For the work itself. For the act of building something beautiful even when the outcome is uncertain.

Life has become amazingly enjoyable. Not despite the difficulty, but because of it.

This is the first crack of light in the darkness.

Thursday arrives.

Eight students. Ages 14-17. Mix of backgrounds.

David and Alex set up in the same coffee shop as last time. Private room. Laptops. Notepads.

David’s hands are shaking slightly. He hides them under the table.

The first student arrives. Sixteen. Junior in high school. Interested in science.

They go through the new prototype. Show him the curiosity question. He types: “How do black holes work?”

They don’t have a curated path for black holes. They have twenty paths. Black holes isn’t one of them.

David’s chest tightens.

“Ah, we don’t have that topic built yet,” Alex says smoothly. “Could you try one of these instead?” He shows the list of available paths.

The student picks “Understanding Climate Change.”

He goes through the content. Watches videos. Reads articles. Follows the path from “why is weather getting weird” to “greenhouse effect” to “carbon cycles” to “human impact.”

After twenty minutes, they ask for feedback.

“That was cool,” the student says. “I didn’t know all those things were connected.”

“Would you use something like this on your own?” David asks. “Not for homework. Just to learn.”

The student thinks. “Maybe? If I was curious about something.”

They thank him. He leaves.

David and Alex look at each other.

“That was… better?” Alex says.

“He said maybe.”

“He said the connections were cool.”

“He also said maybe.”

The second student is fifteen. She picks “The Science of Cooking.”

Goes through the path. Seems engaged. Actually laughs at one of the videos.

Feedback: “I liked how it showed why things work, not just what to do. Like, I never thought about why eggs solidify when you cook them.”

Third student: “The History of Video Games.” Finishes the whole path. Says it’s “actually interesting.”

Fourth student: Picks “Why Empires Fall.” Gets bored halfway through. Says it’s “kind of a lot of reading.”

Fifth through eighth students: Mixed feedback. Some like it. Some don’t. No one says it’s “just another homework app.”

By 5 PM, they’re done.

David and Alex pack up in silence. Walk back to the apartment.

“Well?” Alex says finally.

“I don’t know.”

“It was better. You saw that right? It was definitely better.”

“Yeah. It was better.”

“But?”

“But better doesn’t mean good enough. Better doesn’t mean anyone will actually use it.”

They walk the rest of the way without talking.

Back at the apartment, David opens his laptop. Pulls up the feedback notes.

Eight users. More positive than last time. Some genuine engagement. A few moments where people seemed actually curious.

But no one said “I need this.” No one said “When can I use this for real?”

His phone buzzes. Bank notification. Monthly fee: $12.

Balance: $27,088.

David closes his eyes.

Five months in. $38,000 burned. Two iterations tested. And they’re still not sure if anyone actually wants this.

Alex is in the kitchen making dinner. Rice and eggs again. The smell fills the apartment.

David should feel discouraged. Should feel the weight of the dwindling savings and the inconclusive feedback and the mounting pressure.

But he doesn’t.

He thinks about last night. Debugging at 4 AM. Watching the curiosity paths flow. The satisfaction of making something work beautifully.

The difficulty was the point. The craft was the point.

He doesn’t know if this will succeed. Doesn’t know if they’ll run out of money before they figure it out.

But he knows he’s not done yet.

David opens a new document. Types: “Iteration 3 - What We Learned.”

His fingers move across the keyboard.

Outside, June ends and July begins and the city keeps turning and the savings keep declining.

David keeps building.

Not because he has answers. But because the work itself—the act of trying to make something beautiful and true—has become its own reason.

End of Chapter 6

Chapter 7: The Gray

Mon, 10 Nov 2025 00:00:00 GMT

Chapter 7: The Gray

The week after the user testing, David stops setting alarms.

Not as a decision. He just forgets. Or doesn’t care. The line is blurry.

He wakes when his body wakes. Usually around 10 AM. Sometimes 11. Once, on Thursday, at 1:47 PM. The afternoon sun cutting harsh angles through the blinds.

The apartment smells stale. Not terrible. Just—lived in. Unwashed dishes in the sink. A coffee mug on the desk with a ring of dried residue. Laundry in a pile near the closet. He meant to wash it. When? Last week? Two weeks ago?

Time is strange. Days blend together.

Monday—maybe Monday—David spends four hours fixing a bug in the content sequencer.

Not because it matters. The whole approach is wrong. He knows it’s wrong. The twelve users said so: It feels like everything else.

But the alternative is staring at the wall.

So he fixes the bug. The code compiles cleanly. All tests pass. Green checkmarks. The satisfaction lasts maybe thirty seconds.

Then nothing.

He closes the laptop. Opens the refrigerator. Rice and eggs. He’s been eating rice and eggs for—how long? The rice bag is nearly empty. He should buy more.

He doesn’t.

Eats the eggs scrambled. No salt. Standing at the counter. Doesn’t taste them. Just chews. Swallows. Puts the plate in the sink with the others.

The apartment is quiet. Outside, the city hums. Cars. Voices. Someone’s music thumping from a few floors down.

David returns to his desk. Sits in the chair. The laptop is closed. His phone is face down. The whiteboard on the wall still shows their optimistic timeline from March: “MVP Complete: May 15.”

It’s June now. Late June. Nearly July.

He should erase it.

Doesn’t.

Just sits.

Tuesday—if it is Tuesday—Alex texts three times.

“You good?”

“Want to sync up this afternoon?”

“David?”

David sees the messages. Doesn’t respond.

Not because he’s angry. Not because he’s avoiding.

He just… doesn’t have anything to say.

What would he say? “I’m fine”? He’s not fine. “We need to pivot”? To what? “I’m thinking about next steps”? He’s not thinking. He’s not doing anything.

Around 6 PM—he thinks it’s 6 PM, the light is fading—David picks up his phone. Opens the messages. Types: “Sorry. Busy. We’ll talk soon.”

Deletes it.

Types: “Not in a good place. Need some time.”

Deletes it.

Types: “Yeah I’m good.”

Sends it.

Alex responds immediately. “Cool. Let me know when you want to regroup.”

David sets the phone face-down again.

The lie is easier. Simpler. Requires less energy than the truth.

Wednesday, he doesn’t get out of bed until noon.

Not because he’s tired. He slept eleven hours. Just—what’s the point?

The checking account sits at $36,800. Rent is due in six days. That’s $1,600. After that: $35,200.

Eight months of runway becomes seven. Becomes six. The countdown continues whether he’s building or not.

David lies in bed. Stares at the ceiling. There’s a crack he’s never noticed before. Small. Hairline. Starts near the light fixture and runs toward the corner.

How long has that been there?

He stares at it for forty minutes.

Eventually his bladder forces him up. He uses the bathroom. Catches his reflection in the mirror. Hasn’t shaved in—a week? More? His hair is greasy. His eyes are dull.

He looks like someone who’s given up.

Is that what this is? Giving up?

David doesn’t know. Doesn’t have the energy to figure it out.

He shuffles to the kitchen. Opens the refrigerator. Nearly empty. Eggs are gone. Just rice. Some condiments. A beer Alex left three weeks ago.

He should go to the store.

Instead he makes coffee. Black. No milk left. The coffee tastes bitter. Burnt. He drinks it anyway.

Returns to bed. Pulls the laptop onto his lap. Opens it.

The prototype is there. Minimized. He forgot to close it last time.

David looks at it. The curiosity question sits at the top of the screen: “What do you actually want to learn about?”

He closes it without testing anything.

Opens his email instead. Forty-seven unread messages. Probably his mother. Probably Alex. Probably automated subscriptions he never unsubscribed from.

He doesn’t check.

Closes the email. Closes the laptop. Sets it on the floor.

Lies back down.

The ceiling crack is still there.

Thursday his mother calls.

He answers. Immediately regrets it.

“David?” Her voice is concerned. “I’ve been calling. You haven’t answered.”

“Sorry. I’ve been busy.”

“Busy with what?”

“Work. The company.”

“How is that going?”

The question hangs in the air. How is it going?

Failed. Failing. Dead in the water. Twelve users said it’s like everything else. $8,000 burned for nothing. Seven months of runway left. No path forward. No plan. No energy to make a plan.

“It’s going,” David says.

“Your father is asking when you’ll visit. Maybe for his birthday in August?”

August. Two months away. Will David still be doing this in August? Or will he be back in a corporate job, this whole chapter filed under “lessons learned”?

“Maybe,” he says. “I’ll check my calendar.”

“You said that last time.”

“I know. I’m sorry. Things are just—” He stops. Can’t finish the sentence. “—busy.”

Silence on the other end. His mother can hear the lie. She always can.

“Are you eating?” she asks quietly.

“Yes.”

“Real food?”

“Yes, Mom.”

More silence.

“Okay,” she says finally. “Call me next week. Please.”

“I will.”

They hang up.

David sets the phone down. Feels nothing about the conversation. Not guilt. Not love. Just—blank.

When did feelings stop?

He can’t remember.

Friday—he thinks it’s Friday, but honestly, who knows—David sits at his desk for six hours.

Doesn’t code. Doesn’t plan. Doesn’t email.

Just sits.

The chair is uncomfortable. His lower back developed a constant ache somewhere in the past month. From too many hours sitting. Or lying in bed. His body hurts in vague, ambient ways.

Around 3 PM, he realizes he hasn’t eaten today.

He should eat.

Doesn’t.

Just keeps sitting.

The screen saver activates. Photos from his college graduation. He looks young in them. Optimistic. The smile looks real.

When was that? Six years ago? Seven?

Different person.

The photos cycle. Family dinner. His parents looking proud. His father’s hand on his shoulder. His mother in a dress she probably bought special for the occasion.

They were so happy.

Now David is—what? Almost broke. Building something nobody wants. Lying to them about how it’s going.

He closes the laptop. The photos disappear.

The apartment is very quiet.

Outside, the city is alive. Friday evening. People are probably heading to happy hour. Making weekend plans. Living normal lives.

David sits in the quiet.

Feels nothing about it.

Not envy. Not loneliness. Just—nothing.

This is the bottom. Not dramatic. Not a breakdown.

Just the flat, gray place where caring stops.

The weekend passes.

David doesn’t remember most of it.

Saturday: couch. Sunday: bed. Maybe some food. Maybe a shower. The details are fuzzy.

He exists. That’s about it.

Monday.

David wakes at 11:17 AM. The apartment is warm. Stuffy. When did he last open a window?

He lies in bed for twenty minutes. Staring at the ceiling crack.

It’s gotten longer. Or he’s noticing more of it. The crack branches near the corner. Creates a Y-shape.

Cracks do that. Spread. Split. Get worse if you don’t fix them.

He should probably tell the landlord.

Won’t.

Eventually, he gets up. Uses the bathroom. Looks in the mirror.

His beard is uneven. His eyes are bloodshot. He looks sick.

Maybe he is sick. Depression is sick, right? Or is this just what failure looks like?

David splashes water on his face. Doesn’t help.

He shuffles to the kitchen. Opens the refrigerator.

Empty except for condiments and Alex’s beer.

He should go to the store. Should eat real food. Should do… something.

Instead he opens the beer. Takes a sip. It’s flat. Tastes awful.

He drinks it anyway. Standing at the counter. Looking out the window.

The city below is bright with early summer. Trees in bloom. People in shorts. Life happening.

David finishes the beer. Sets the bottle on the counter with the dirty dishes.

Returns to his desk.

The laptop is still closed from Friday. Or Thursday. Whichever day that was.

He should work. Should open it. Should try again.

But what’s the point?

He’s tried three times. Three iterations. Each one failed. The users don’t want it. Or they want it but don’t need it. Or they need it but won’t pay for it.

The math doesn’t work. The vision doesn’t translate. The gap between what he imagines and what he can build is too wide.

Maybe he’s not good enough.

Maybe the idea is bad.

Maybe his mother was right and this whole thing is him refusing to grow up and get a real job.

David sits at the desk. Doesn’t open the laptop.

Just sits. Hands in his lap. Staring at the closed aluminum lid.

Minutes pass. Many of them.

The sunlight shifts. The room gets warmer.

Outside, someone laughs. The sound carries through the closed window. Bright. Genuine.

David can’t remember the last time he laughed.

Around 2 PM—the clock says 2:13—David’s hand moves without conscious decision.

Opens the laptop.

Not to work. Just to… do something. Anything. The blankness is worse than failure.

The prototype loads. Still open from whenever.

The curiosity question: “What do you actually want to learn about?”

David stares at it.

When was the last time he was curious about anything?

Not the platform. Not the metrics. Just—genuinely curious. Wanting to know something for the sake of knowing.

He can’t remember.

Sixteen-year-old David in that library was curious. Heard Jobs’s voice and wanted to know what it meant. Carried that yearning for years.

Where did it go?

His fingers hover over the keyboard.

Then, without planning to, he types: “What happens when you stop caring about anything?”

It’s not a real query. The prototype doesn’t have content for that. But he types it anyway.

The screen thinks. Tries to process. The knowledge graph starts to form.

Then crashes. Error message. “No content path found.”

David almost smiles. Of course. Even the prototype can’t answer that.

He closes the error.

Sits looking at the empty search box.

Actually—wait.

Why did it crash instead of saying “sorry, I don’t have content for that”?

It’s a small thing. A bug. Barely matters.

But David’s brain—engineer brain, problem-solver brain—catches on it.

The error handling is wrong. If there’s no content path, it should gracefully fail. Not throw an exception.

He pulls up the code. Scrolls to the error handling module.

There. Line 67. It checks for empty results but doesn’t handle null returns.

One-line fix. Add a null check.

David fixes it. Not because it matters. Just because he’s looking at it.

Tests it. Types the same query: “What happens when you stop caring about anything?”

This time: “I don’t have content for that yet. Try something else?”

Better.

He closes the test.

Looks at the code again.

While he’s here, there’s another bug. The content sequencer sometimes displays nodes in the wrong order. He’s known about it for weeks. Never fixed it because—why bother?

But his fingers are moving now. Muscle memory. Find the bug. Fix the bug.

Ten minutes later, it’s fixed.

He tests it. Works.

Sits back.

Two bugs fixed. Neither matters. The product is still wrong. The users still don’t want it.

But his hands aren’t shaking anymore.

His chest doesn’t feel quite so tight.

For the first time in eight days—or nine, or ten, he’s lost count—David’s brain is doing something other than numbly existing.

It’s not excitement. Not hope. Not even really interest.

Just—motion. Forward. Something instead of nothing.

He opens the prototype again. Looks at the curiosity question.

“What do you actually want to learn about?”

The girl from user testing said she typed something random because she didn’t think it mattered.

Why didn’t she think it mattered?

The question arrives quietly. Not urgently. Just—there.

David opens a blank document. Types: “Why didn’t it feel like it mattered?”

Stares at the question.

Doesn’t have an answer yet.

But for the first time in days, he’s asking.

That’s something.

Not recovery. Not breakthrough.

Just—a small return of curiosity.

The smallest crack in the numbness.

David closes the document. Saves it. Labels it: “Questions.”

Looks at the clock. 3:47 PM.

He should eat. Should shower. Should call Alex back. Should do a lot of things.

Instead he opens the code again.

There’s a third bug. Minor. The knowledge graph rendering sometimes overlaps nodes on mobile.

He’s known about it. Never cared.

Now—for no reason he can name—he wants to fix it.

Not because it’ll save the company. Not because users are demanding it.

Just because it’s there. Broken. Fixable.

And fixing broken things is what he does.

Even when nothing else makes sense.

At 11 PM, David is still at his desk.

Fixed seven bugs. Not urgent ones. Just—things that were wrong.

His back hurts. His eyes hurt. His stomach is empty.

But his hands are moving. His brain is working.

He’s not numb anymore.

Not happy. Not hopeful. Not confident.

Just—present. Doing the work. One line of code at a time.

Around midnight, he saves everything. Closes the laptop.

Looks around the apartment.

It’s a mess. Dirty dishes. Laundry pile. Stale air.

He opens a window. The night air flows in. Cool. Fresh. The city sounds filter through—distant traffic, someone’s TV, the hum of existing.

David takes a breath. The first real breath in days.

Tomorrow he’ll clean. Maybe. Or maybe he’ll keep coding. Fix more bugs. Figure out what’s broken and why.

Not to save the company. Just to do the work.

Because the work—even when it doesn’t matter—is better than the gray.

The numbness is lifting. Slowly. Unevenly.

But lifting.

And somewhere under it, faint but present, is the thing he thought he’d lost:

Curiosity.

Not about success. Not about the vision. Just—what’s broken? What’s the next problem? What happens if I try this?

The smallest questions.

The beginning of caring again.

David turns off the lights. The apartment goes dark. The city glows through the open window.

He falls asleep on the futon—not the floor, at least that’s progress.

Dreams about code. About bugs fixed and problems solved.

Nothing profound. Nothing transformative.

Just work.

And that’s enough.

For tonight.

For now.

The gray is fading.

End of Chapter 7

Chapter 8: The Breaking Point

Mon, 10 Nov 2025 00:00:00 GMT

Chapter 8: The Breaking Point

October. 3 AM.

The cursor blinks. White against blue.

Google—Senior Software Engineer, Education Technology.

David’s checking account: $3,847. Rent due in eleven days.

The apartment is quiet in the way only 3 AM can be. His desk lamp creates a small circle of light. Everything beyond it remains in shadow.

He’s been staring at this screen for forty-seven minutes. Maybe longer. Time moves differently at this hour.

His co-founder’s text from earlier today is still visible, minimized at the bottom: The user feedback is tough but we can pivot. You’re brilliant at this. We’ll figure it out. Get some rest.

Alex’s optimism used to help. Now it just makes the emptiness louder.

Eight months since the layoff. Three failed iterations. Thirty-two users who “like it” but don’t need it. $43,153 burned through. Seven weeks of runway left.

The math is simple. The decision should be simple.

Click the button. Send the application. Interview in two weeks. Offer letter in a month. Back to safety. Back to salary and health insurance and his mother sleeping through the night again.

His hand moves to the trackpad.

But doesn’t click.

Just hovers. Neutral territory.

Behind him, the whiteboard mocks him with its optimistic timeline from March. “MVP Complete: May 15.” They’ve had three MVPs since then. None of them complete. None of them right.

His phone buzzes. His mother. Another missed call to add to the collection.

She knows now. Has known since August. The lie about interviewing finally collapsed under its own weight. She calls once a week. Asks if he’s eating. If he’s sleeping. If he’s thought about real jobs.

She’s trying to accept it. He hears the effort in her voice. The way she doesn’t push anymore. Just—worries. Quietly. The way mothers do.

It would be easier if she were angry.

David’s eyes burn from screen time. His lower back has that hollow feeling from too many hours in the chair. When did he last stand up? The coffee he made around midnight sits cold and forgotten.

The job posting describes what he used to be: Strong background in full-stack development. Experience shipping products at scale. Passion for education technology.

He could write the cover letter in twenty minutes. Has the template saved. Just change the company name. Same lies about passion. Same performance of enthusiasm.

Three months at a time, he could make $150,000 a year pretending to care about features that don’t matter.

Or he could burn through the last $3,847 building something thirty-two people use but don’t love.

The cursor blinks.

David thinks about the user testing from last month. Eight people. Better feedback than the first round. “It’s engaging.” “My daughter actually used it.” “Better than Khan Academy.”

Better. That word again.

Better but not essential. Better but not needed. Better but not—

Wait.

David sits up straighter.

The girl from first user testing. Fourteen. Quiet. Barely spoke.

She said something.

He opens his notes. Scrolls frantically. May. Where is it? There—

“I liked that part at the beginning where it asked what I’m curious about. No one ever asks that.”

“Did it feel useful?”

“I mean, I don’t know. I just typed something random because I didn’t think it actually mattered. Does it?”

David reads it once. Twice. Three times.

The cursor on the job posting stops blinking. The room stops moving. Everything narrows to these words.

I just typed something random because I didn’t think it actually mattered.

His hands have stopped shaking. His breath has stopped catching. Everything is suddenly, impossibly clear.

The question was there. Right at the start of the prototype. The curiosity prompt. The entire vision—start with what kids actually want to learn instead of what they’re supposed to learn.

But she typed something random.

Not because she didn’t know what she was curious about. Not because she didn’t care.

Because she didn’t think it mattered.

Because the education system—every homework assignment, every standardized test, every “read chapter 5 and answer the questions at the end”—had taught her that what she cares about is irrelevant. That learning isn’t about curiosity. It’s about compliance.

Fill in the blank. Give the expected answer. Don’t actually think about what you care about because nobody cares what you care about.

And their prototype—despite the curiosity question, despite the personalization, despite everything they built—reinforced that lesson.

Asked what she’s curious about, then immediately ignored her answer to feed her what the algorithm decided she needed.

“Thank you for sharing. Now let me show you what I think is important.”

The same pattern. The same broken system. Just prettier packaging.

David’s vision blurs. Not from exhaustion. From the sudden, overwhelming clarity of seeing exactly what was wrong.

They weren’t asking the wrong question. They were asking the right question in the wrong way.

The curiosity prompt was a feature. An add-on. A nice-to-have that made the product feel different from other homework apps.

But the moment they asked what she was curious about, the algorithm took over. Decided what to show next based on learning styles, difficulty levels, curriculum standards. All those smart things they’d built.

And in doing that, they told her: your curiosity is a data point. We’ll use it to optimize your learning path. But we—the system, the algorithm, the platform—still know better than you what you need.

No wonder it felt like everything else. It was everything else.

David leans back. The chair creaks. The apartment is so quiet he can hear his own heartbeat.

Eight months. Three iterations. $43,000 in savings. All spent building better cages.

He thinks about Marcus. The numb look when he got 94 instead of 98. Four points that meant everything in a system that sorted people like products.

He thinks about sixteen-year-old David in that library. Hearing Jobs’s voice. The yearning for something different.

He thinks about this girl. Fourteen years old. Already trained that her curiosity doesn’t matter. So thoroughly conditioned that even when directly asked what she wants to learn, she types something random.

Because what’s the point? Nobody actually listens.

The tragedy isn’t that she didn’t know what she was curious about.

The tragedy is that she didn’t believe anyone cared.

And their prototype proved her right.

David closes the job posting tab.

Then closes the entire browser. Not just the tab. The whole thing. Every escape route.

Opens the prototype with new eyes.

The curiosity question sits there at the start: “What do you actually want to learn about?”

Pretty font. Nice design. Looks inviting.

But then what happens?

User types “Why do we dream?”

System thinks: Okay, dreams. That touches sleep science, neuroscience, psychology. Let me check this user’s learning style preference from their previous behavior. They seem to like videos. Okay, serve them the video about REM sleep first. Then the article about sleep cycles. Then the interactive quiz to check comprehension.

All smart. All reasonable. All wrong.

Because the system made the decision. The algorithm decided the path. The user’s curiosity was input for optimization, not the foundation of the experience.

They might as well have asked “What do you want to learn?” then said “That’s nice, now here’s what we think you should learn.”

David’s hands start moving without conscious decision. Opening a new document.

Not code. Just thinking. Writing.

What if the user’s curiosity wasn’t input for the algorithm? What if it was the algorithm?

What if when she types “Why do we dream?” the screen doesn’t immediately load content. Instead, it shows her the question itself becoming a world.

A visualization. Her curiosity as the center. Connections radiating out—not because we decided they were relevant, but because they genuinely connect. REM sleep, yes. But also creativity. Memory. Why humans need sleep at all. What happens when we don’t dream. How dreams have been interpreted across cultures. The neuroscience and the mystery and the art all tangled together.

A knowledge graph that blooms in response to her specific question. That shows her—visually, immediately, undeniably—that her curiosity just unlocked an entire world.

And then—here’s the crucial part—she chooses where to go. Not the algorithm. Her.

She can click into the neuroscience if that’s what calls to her. Or the cultural interpretations. Or the connection to creativity. Or something else entirely. The system shows the possibilities. She makes the choice.

Her curiosity leading. The system following. Not the other way around.

David stops typing. Reads what he wrote.

This is different. Fundamentally different.

Not “better personalization.” Not “smarter algorithms.” Different.

The current prototype asks “What are you curious about?” then ignores the answer to optimize learning outcomes.

This would ask “What are you curious about?” then show the user that their curiosity is valuable enough to build entire worlds around.

Not telling them it matters. Showing them.

David closes the job posting tab.

Opens the prototype. Looks at it with new eyes.

The curiosity question is there. Right at the start. “What do you actually want to learn about?”

But then what happens? The algorithm takes over. Decides what content to serve. Decides the sequence. Decides the pace.

The user types their curiosity. The system says “thank you for sharing” and then proceeds to ignore it in favor of what the algorithm thinks they need.

No wonder it feels like everything else. It is everything else. Just with a prettier opening question.

David leans back in his chair.

Eight months. Three iterations. $43,000 in savings. All spent chasing the wrong problem.

They were trying to build a better homework app. Trying to make the cage more comfortable instead of opening the door.

But what if—

What if the entire product restructured around the curiosity? Not just asked about it. Not just tagged content with “related to your interests.”

What if the user’s curiosity was the only thing that mattered? What if they could see their question unfold in real-time? See the connections being made? See that their interests—their actual, real, unfiltered interests—were valuable?

What if the product made them feel it? Not through words. Through action. Through showing them that their curiosity unlocks doors.

David pulls up a blank document. His fingers hover over the keyboard.

The job posting is closed. But so is the browser. Not just the tab. The entire browser. Every escape route.

Because somewhere in the last forty-seven minutes of hovering, something shifted.

He’s not hovering anymore.

He types: “Prototype #3 - Making Curiosity Matter”

Then stops.

Opens a new tab. Searches for something he hasn’t watched in months.

The Stanford commencement speech. June 2005. Steve Jobs.

He skips past the famous parts. “Stay hungry, stay foolish”—everyone knows that line. It’s on posters. T-shirts. LinkedIn bios.

He scrolls to the part no one quotes. The part about getting fired from Apple.

Jobs’s voice fills the quiet apartment. Tired. Real.

“I didn’t see it then, but it turned out that getting fired from Apple was the best thing that could have ever happened to me. The heaviness of being successful was replaced by the lightness of being a beginner again, freed from the burden of knowing. It freed me to enter one of the most creative periods of my life.”

David has heard this dozens of times. Hundreds.

But tonight—sitting here at 3 AM with $3,847 left and seven weeks of runway and three failed prototypes behind him—he hears it differently.

Not as inspiration. As recognition.

Jobs wasn’t talking about the lightness feeling good. He was talking about how devastating it felt. How it freed him not because freedom is comfortable, but because he had nothing left to lose.

The video continues.

“I’m convinced that the only thing that kept me going was that I loved what I did. You’ve got to find what you love… Your work is going to fill a large part of your life, and the only way to be truly satisfied is to do what you believe is great work. And the only way to do great work is to love what you do.”

David pauses the video.

Does he love this?

The honest answer: he doesn’t know anymore. The past eight months have been brutal. Exhausting. Terrifying.

But—

He thinks about last night. Debugging the content sequencer at 2 AM. The satisfaction when the flow finally worked. Not because it would make money. Not because users would notice. But because it was right. Because the craft of it—the elegance of solving a problem well—mattered.

He thinks about the email from the teacher in Ohio. The student who spent two hours learning about marine biology. Who was told she wasn’t smart. Who found something she cared about and couldn’t stop.

He thinks about sixteen-year-old David in that library. Hearing Jobs’s voice for the first time. The quiet yearning. The sense that there was another way to live.

Ten years. From library to layoff to this moment. This 3 AM silence. This choice.

Jobs keeps talking.

“And most important, have the courage to follow your heart and intuition. They somehow already know what you truly want to become.”

David’s heart says: you’re not done.

His intuition says: you were close but not quite there. The vision is right. The execution is wrong.

He closes the video.

Opens the document again.

“Prototype #3 - Making Curiosity Matter”

He starts typing.

Not code. Not a product spec. Just—thinking. Working through the problem.

What if the entire interface showed the knowledge graph? What if when you typed your curiosity, you could see it expand? See the connections forming? See that your question—your specific, unique, random question—was valuable enough to build a whole world around?

What if instead of the system deciding what you need, it showed you what’s possible and let you choose?

What if curiosity wasn’t a feature but the only feature?

The words flow. Not perfectly. Not polished. But real.

David types until his neck aches. Until his eyes burn. Until the first birds start their morning calls and the darkness begins to thin.

At 6:47 AM, he saves the document. Fifteen pages of notes. Problems. Solutions. A completely different approach.

It might be wrong. Probably is. But it’s closer.

He closes the laptop.

Stands up. His knees crack. He walks to the window.

The city is waking. First light touching the buildings. People starting their days. Commuting to offices. Opening shops. Living normal lives.

David thinks about his mother. She’s probably awake now. Making breakfast. Worrying about him. Trying to accept something she doesn’t understand.

He thinks about Alex. Still asleep on his couch across town. Still believing despite the mounting evidence that maybe they should have backup plans.

He thinks about the girl who typed something random because she didn’t think it mattered.

What if he could show her it did? What if a million kids like her—kids told they’re not smart, kids sorted and ranked and measured—what if they all saw that their curiosity mattered?

Not through words. Through the product itself. Through an experience that made them feel it.

That’s what he’s building for.

Not to prove his mother wrong. Not to validate his choices. Not even to succeed by conventional metrics.

To show one kid that her curiosity matters. That she matters. That the system that tried to standardize her was wrong.

If he can do that—if even one person has that experience—then the eight months, the $43,000, the sleepless nights, all of it means something.

David returns to his desk.

Opens his laptop.

The job posting is gone. The browser closed. The escape route sealed.

He opens his code editor instead.

Types at the top: ”// Prototype 3: The curiosity is the foundation, not a feature”

His fingers move across the keyboard. Not writing the perfect solution. Just taking the next step.

Behind him, the whiteboard still shows the optimistic timeline from March. He should erase it. Should write a new one.

But he doesn’t.

Instead he adds below it, in different colored marker:

“October - Start over. Make curiosity matter.”

Seven weeks of runway left. Maybe less.

Enough time to find out if this vision is real or if he’s been chasing delusion.

Either way, he’ll know.

David codes until the sun is fully up. Until Alex texts asking if he’s okay. Until his stomach demands food and his body demands rest.

But before he closes the laptop, he does one thing.

Opens his phone. Scrolls to his mother’s contact. Types:

I’m okay, Mom. I think I figured something out. Will call you later.

Send.

Then to Alex:

Come over when you’re up. I want to show you something.

He sets the phone down.

Looks at the document again. “Prototype #3 - Making Curiosity Matter.”

Fifteen pages of notes. A completely different approach. A vision that might fail.

But a vision he still loves.

Jobs’s voice echoes in his memory: I had been rejected, but I was still in love. So I decided to start over.

David is still in love. Not with the prototypes. Not with the struggle. But with the why.

With helping kids escape the cage that held him. With building something that says: your curiosity matters. You matter. The system was wrong.

He’s not done yet.

The breaking point becomes the turning point.

David saves his work. Closes the laptop.

Steps into the October morning.

Seven weeks left. $3,847 in the bank. Three failed prototypes behind him.

And a fourth one—the right one—waiting to be built.

He doesn’t know if it’ll work.

But he knows he has to try.

Not because success is guaranteed. But because the alternative—giving up now, going back, never knowing—would be worse than failure.

The darkness is thinning.

Not gone. Not yet.

But for the first time in months, David can see the shape of what comes next.

And it looks like hope.

End of Chapter 8

Chapter 9: The Rebuild

Mon, 10 Nov 2025 00:00:00 GMT

Chapter 9: The Rebuild

November.

David’s checking account: $2,950.

The number should terrify him. Five weeks ago it was $3,847. Now it’s barely enough to cover one month’s rent with $1,350 left over.

But he doesn’t check the banking app as often anymore. Not because the number stopped mattering. Because checking it won’t change anything.

The fourth prototype is taking shape.

Not the fourth iteration. The fourth reimagining.

Alex is sitting across from him, staring at the wireframe on David’s screen. It’s been three minutes since either of them spoke.

“It’s completely different,” Alex says finally.

“Yeah.”

“We’d have to rebuild everything.”

“Yeah.”

“From scratch.”

David nods. The wireframe shows something that looks nothing like what they’ve built before. No list of content. No algorithmic recommendations. No lesson sequences.

Just a blank space. A search box. And underneath: “What are you curious about?”

When you type something—anything—the screen transforms into a living knowledge graph. Your question becomes a node. Related concepts branch out from it like roots spreading through soil. You can see the connections. See how your curiosity touches physics, history, art, science. See that your random question isn’t random at all—it’s a doorway.

You choose where to go. The system doesn’t decide for you. It just shows you what’s possible.

“This is what you wrote at 3 AM?” Alex asks.

“Yeah.”

“Fifteen pages of notes?”

“Yeah.”

Alex leans back. Rubs his face. “David. We have maybe six weeks of money left. Probably less. You want to throw away three months of work and start over?”

“The three months of work was wrong.”

“It wasn’t wrong. It was getting better. The feedback from the last test was positive—”

“It was ‘better.’ Not good. Not essential. Better.” David turns the screen toward Alex. “This is different. This makes curiosity visible. Makes it real. Shows kids that what they care about matters.”

“How do we build the knowledge graph? That’s hundreds of hours of content curation. Thousands of connections.”

“We start small. Twenty topics. Build out from there.”

“We already tried manual curation—”

“Not like this.” David opens another document. “Before, we were curating paths. Start to finish. A to Z. This is different. We’re mapping connections. Any question can lead anywhere. The kids follow their own curiosity.”

Alex is quiet for a long moment.

“The girl from the first user test,” he says. “The one who typed something random.”

“Yeah.”

“This would show her it matters.”

“Yeah.”

More silence. The apartment is cold. David hasn’t turned on the heat. Forty-seven cents per hour, the calculator in his head says. Every hour the heat is on costs forty-seven cents.

“If we do this,” Alex says slowly, “we’re all in. No backup plan. No safety net. If it doesn’t work—”

“I know.”

“Do you? Because I’ve been thinking about backup plans. I’ve been looking at jobs. Not applying. Just looking. And I need to know if you’re—” He stops. Starts again. “I need to know if you’re sure.”

David thinks about the 3 AM moment five weeks ago. The cursor hovering. The escape route open. The moment he closed the browser—all of it.

“I’m not sure it’ll work,” he says. “But I’m sure we have to try.”

Alex nods slowly. “Okay.”

“Okay?”

“Okay. Let’s rebuild.”

They spend the next week mapping.

Not coding. Not designing. Just mapping.

Twenty curiosity topics. Starting points that could branch anywhere:

How do airplanes fly?
Why do people fight wars?
What makes music sound good?
How does the internet work?
Why do we dream?

For each topic, they map connections. Not linear paths. Webs. Networks. A kid curious about airplanes might branch into physics, or engineering, or World War II history, or environmental impact of aviation. Every connection mapped. Every node linked.

The work is meticulous. Exhausting. Sometimes they spend three hours debating whether two concepts should be connected, and if so, how strongly.

David’s checking account: $2,650.

Rent paid. Rice and eggs. The heat stays off. He wears two hoodies.

“This connection doesn’t feel right,” Alex says on Thursday afternoon. They’re mapping “Why do we dream?” and trying to connect it to neuroscience, psychology, and creativity.

“Which one?”

“Dreams to artistic inspiration. It’s too vague. Too fluffy.”

David looks at the diagram. “What if we connect through REM sleep? Show how brain activity during dreaming is similar to creative problem-solving?”

“That’s better. More concrete.”

They redraw the connection. Add a node for REM sleep. Link it to memory formation, creativity, problem-solving.

The web grows more complex. More beautiful.

At 11 PM, they step back. The whiteboard is covered in nodes and connections. Twenty topics, maybe three hundred nodes, thousands of links.

“This is insane,” Alex says. Not angry. Just stating fact.

“Yeah.”

“We can’t actually build this in six weeks.”

“No.”

“So what do we do?”

David stares at the whiteboard. All those connections. All those doorways.

“We build enough to prove it works,” he says. “Pick five topics. Map them fully. Build the interface. Show that when a kid types ‘How do airplanes fly,’ they see a world open up.”

“Five topics.”

“Yeah.”

“That’s still a hundred hours minimum.”

David checks his phone. It’s 11:17 PM. “Then we better start.”

Two weeks blur together.

David works sixteen-hour days. Sometimes eighteen. The code sprawls across his screen—graph algorithms, connection weights, visualization layers.

Alex handles the content. Finding the best videos, articles, simulations for each node. Making sure the connections feel organic, not forced.

They don’t talk much. Just work in parallel. Coffee going cold. Meals eaten at desks. The apartment dark except for two laptop screens.

David’s mother calls twice. He answers both times. Tells her he’s okay. That he’s close to something. She doesn’t ask for details. Just: “Are you eating? Are you sleeping?”

“Yes,” he lies.

“David—”

“I’m okay, Mom. Really.”

She doesn’t believe him. But she lets it go.

The balance: $2,180.

Mid-November. Four weeks until rent is due again.

The interface starts working. When you type a question, the graph blooms on screen. Nodes appear. Connections draw themselves. You can click any node, see what it links to, follow the thread wherever it leads.

It’s not perfect. The animations are choppy. Sometimes the connections overlap messily. But it works.

“Holy shit,” Alex says when David shows him the first working demo. “That’s actually cool.”

“Yeah?”

“Yeah. Like—I want to click around. See where things go.”

They spend an hour just playing with it. Typing random questions. Watching the graphs bloom. Following threads from topic to topic.

“We still need more content,” Alex says. “Some of these nodes are thin.”

“I know. But the concept works. You feel it, right?”

Alex nods slowly. “Yeah. I feel it.”

They recruit testers for the day before Thanksgiving.

Not twelve people this time. Just five. High school students. Ages fifteen to seventeen.

David can’t afford to rent the coffee shop room again. They do it at the apartment. Set up one desk, two chairs, laptops ready.

The first tester arrives at 2 PM. Sixteen years old. Junior in high school. Wants to study biology.

David walks her through it. “Type anything you’re curious about.”

She types: “Why do some people get cancer?”

The graph blooms. Cancer appears as the central node. Branches spread: genetic mutations, environmental factors, cell division, immune system, treatment methods, prevention research.

The girl leans forward.

“Whoa.”

She clicks on genetic mutations. The graph reorganizes. Shows connections to DNA, heredity, CRISPR, evolution.

She spends thirty minutes clicking. Following threads. Watching the graph shift and grow.

When they ask for feedback, she’s quiet for a moment.

“I’ve never seen learning look like this,” she says. “Like—I can see how everything connects. It’s not just memorizing facts. It’s understanding how things fit together.”

David’s hands are shaking under the table.

“Would you use this?” Alex asks.

“Yeah. Definitely.”

After she leaves, David and Alex sit in silence.

“That was different,” Alex says quietly.

“Yeah.”

“She actually got excited.”

“Yeah.”

The second tester: “How does electricity work?”

Spends twenty-five minutes following connections from circuits to physics to power grids to renewable energy.

Feedback: “This makes science feel less scary. Like I can start anywhere and just explore.”

The third tester: “Why do people speak different languages?”

Goes from languages to migration to culture to writing systems to brain development.

Feedback: “I feel like I’m discovering things instead of being taught them.”

The fourth tester arrives at 6 PM. Seventeen years old. Senior. Looks skeptical from the start.

David walks him through the same intro. “Type anything you’re curious about.”

The boy types: “How do video games work?”

The graph starts to bloom. Game design, programming, graphics, player psychology—

Then freezes.

David’s stomach drops.

The nodes are rendering on top of each other. A jumbled mess. The connections are overlapping so badly the screen looks like someone spilled spaghetti on a blueprint.

“Uh,” the boy says. “Is it supposed to look like that?”

“No,” David says. His fingers are already moving, trying to refresh. “Give me one second—”

The refresh makes it worse. Now the graph is flickering. Nodes appearing and disappearing. The browser throws a warning: “This page is slowing down your computer.”

“Sorry,” David says, his heart pounding. “Let me restart this—”

But the restart doesn’t help. The graph loads—tries to load—but the layout algorithm can’t handle the complexity. Video games connects to too many things. Programming, art, music, psychology, business, narrative design. The algorithm keeps recalculating, keeps trying to find space for all the nodes, keeps failing.

The screen is a mess of overlapping circles and tangled lines.

“This is confusing,” the boy says. Not mean. Just factual.

David force-quits the browser. Reopens it. “Okay, let’s try a simpler topic. What else are you curious about?”

The boy shrugs. “I mean… that was the thing I actually wanted to learn about.”

“I know, I’m sorry. The system has trouble with some topics. Let me—”

“It’s fine.” The boy is already pulling out his phone. Checking the time. “How much longer is this?”

David and Alex exchange a glance.

“We were hoping thirty minutes,” Alex says. “But if the tech isn’t working—”

“Yeah, I should probably go anyway. I have homework.”

They thank him. He leaves. Polite enough. But David saw his face. The disappointment shifting to dismissal. The look that says: This is just another broken app.

After the door closes, David sits very still.

“That was bad,” Alex says.

“Yeah.”

“The graph can’t handle complex topics.”

“I know.”

“We tested this. How did we not catch that?”

“We tested with the topics we built. Video games has too many connections. The layout algorithm couldn’t—” David stops. Runs his hands through his hair. “Fuck.”

Alex is quiet for a moment. “The fifth tester is supposed to be here in twenty minutes.”

“I know.”

“Do we cancel?”

“No.” David opens his laptop. Pulls up the code. “I can fix this. Add a complexity cap. Limit how many connections render at once.”

“In twenty minutes?”

“I can try.”

David’s hands fly across the keyboard. The layout algorithm, line 347. Add a maximum node limit. Render top fifteen connections only. Priority weighted by relevance.

Fifteen minutes. The code compiles. He tests it.

Types: “How do video games work?”

The graph blooms. This time—controlled. Fifteen nodes. Clean. Navigable.

But shallow. He knows it’s shallow. All the depth is hidden. A user would have to click three times to reach things that should be immediate.

The trade-off: usable but limited. Or ambitious but broken.

At 6:25, the fifth tester arrives. Fifteen years old. Quiet. Nervous.

David walks her through it. Holds his breath.

She types: “Why do we dream?”

The graph blooms. Dreams—psychology, REM sleep, memory, creativity. Eight connections. Manageable.

She clicks around for twenty minutes. Follows threads. Seems engaged.

Feedback: “This is cool. I’d use it.”

After she leaves, David and Alex sit in silence.

Three good tests. One disaster. One okay.

“Three out of five is good,” Alex says. Not quite believing it.

“One out of five was a complete failure,” David says. “The fourth kid left thinking we’re amateurs.”

“So we fix the algorithm.”

“How? If we limit connections, it’s shallow. If we don’t limit them, it breaks.”

“We solve it the same way we solve everything else. We figure it out.”

David wants to believe that. Wants to feel the confidence Alex is projecting.

But he can’t stop seeing that boy’s face. The confusion. The disappointment. The dismissal.

This is just another broken app.

Maybe it is.

Maybe fixing the bugs just reveals bigger problems. Deeper flaws. Fundamental limits to what they’re trying to build.

David closes his laptop.

“I need some air,” he says.

He walks outside. The November evening is cold. Clear. He stands on the sidewalk. Breathes.

Three months ago, they had nothing. Now they have something. But something that breaks. Something that disappoints.

Is that progress?

Or just more expensive failure?

David doesn’t know.

He stays outside for ten minutes. Until his hands stop shaking. Until the panic fades to just—exhaustion.

When he comes back inside, Alex is at the computer. Already working on the algorithm.

“I think I can optimize the rendering,” Alex says without looking up. “Prioritize central nodes. Lazy-load peripheral connections.”

“That’ll take days to build.”

“Then we better start.”

David sits down at his desk. Opens his laptop.

Three out of five tests went well. One was a disaster. One was marginal.

Not the validation they needed. But more than they had.

They keep building.

By the fifth tester, David has stopped taking notes. Just watching. Watching most people lean forward. Watching some people get confused. Watching the product work beautifully sometimes and fail spectacularly others.

All five tests are done. Three loved it. One hated the broken experience. One thought it was “okay.”

Two ask when they can use it for real. One asked if they were hiring testers. One couldn’t wait to leave. One seemed indifferent.

Not perfect. Not a clean win.

But something.

After the last one leaves, David closes his laptop. The apartment is dark. Almost 8 PM.

“We need to talk about money,” Alex says.

“I know.”

“You’re running out.”

“I know.”

“I have some savings. Not much, but—”

“No.” David shakes his head. “You’ve already sacrificed enough.”

“This is my company too—”

“Alex. I appreciate it. But no.”

Silence.

“What’s your plan then?” Alex asks. “You have what, four weeks left?”

“Three, probably.”

“And then?”

David looks at the laptop. Thinks about the five testers. The way they leaned forward. The way they said it felt different.

“Then we launch,” he says.

“Launch? David, we barely have five topics built. The content is thin. The interface is buggy—”

“I know. But we have enough to show it works. Enough to get beta users. If it’s real—if this is actually different—people will use it.”

“And if they don’t?”

Then I’m done, David thinks. Out of money. Out of time. Back to corporate or sleeping on someone’s couch or moving back with his parents with his tail between his legs.

But he doesn’t say that.

“Then at least we’ll know we tried the right thing,” he says instead.

They spend the week after Thanksgiving preparing to launch.

Not a real launch. No press. No marketing. Just posting on Reddit, education forums, reaching out to teachers they know. “We built something different. Want to try it?”

The balance: $1,850.

December 1st.

They have a landing page. A signup form. The prototype live but fragile. Twenty initial beta users lined up—mostly people Alex knows.

David sits at his desk. Finger hovering over the “Publish” button on the landing page.

“You ready?” Alex asks.

No. He’s not ready. The product is incomplete. Buggy. Might crash. Might fail spectacularly.

But he thinks about the girl who said “I’ve never seen learning look like this.”

Thinks about the fourteen-year-old from the first user test who typed something random because she didn’t think it mattered.

Thinks about sixteen-year-old David in that library, hearing Jobs’s voice, carrying a yearning he couldn’t name for ten years.

He clicks Publish.

The landing page goes live.

The first sign-ups start trickling in. Five by end of day. Twelve by end of week. Twenty-five by mid-December.

David watches the metrics obsessively. How long do people stay? What do they click? Do they come back?

The answers: Longer than before. Everything. Yes.

Not everyone. Some people sign up and never log in. Some use it once and don’t return.

But some—a small but growing number—keep coming back. Every day. Spending twenty, thirty, forty minutes following their curiosity through the knowledge graph.

One of them is a fifteen-year-old named Marcus.

David notices him in the analytics. User ID 0047. Logs in almost every day. Average session: thirty-two minutes.

Then, on December 18th, an email:

Subject: “This is amazing”

“I’ve been using your app for two weeks. I’m in 10th grade and I hate school. Everyone tells me I need to study harder, get better grades, beat the other kids. But I don’t care about being better than anyone. I just want to learn stuff that’s interesting. Your app is the first thing that lets me do that. I started with ‘How do video games work’ and ended up learning about AI and computer graphics and now I’m trying to build my own simple game. Thank you for making this. - Marcus”

David reads it three times.

Closes his laptop.

Walks to the window. The city is dark. December evening. Cold. Lights scattered across buildings.

His checking account has $1,620.

Two weeks until rent is due.

The product has forty-three users. Thirty-two active in the last week.

Not enough for revenue. Not enough for investors. Not enough for anything except proof of concept.

But Marcus—a kid who hates school, who doesn’t want to compete, who just wants to learn—spent two weeks following his curiosity and ended up trying to build a game.

That’s not nothing.

David’s phone buzzes. His mother.

He answers.

“Hi, Mom.”

“David. How are you?”

“I’m okay.”

“Really? You sound tired.”

He is tired. Exhausted. Running on fumes. But also—

“We launched,” he says. “The new version. It’s live.”

“And?”

“And it’s working. Not making money yet. But people are using it. Actually using it. One kid emailed me today. Said it’s the first thing that lets him learn what he’s interested in.”

Silence on the other end.

“That’s good,” she says finally. Her voice is careful. Not excited. Not dismissive. Just—careful. “I’m glad.”

“I don’t know if it’ll succeed, Mom. I really don’t. But I think we built something real this time.”

“How much money do you have left?”

David almost laughs. Of course she asks. Of course the practical question cuts through everything else.

“Not much,” he admits.

“Weeks? Months?”

“Weeks.”

He hears her take a breath. Hold it. “And if you run out?”

“I don’t know. But I’m not giving up yet.”

Another pause.

“Okay,” she says. “Just—promise me you’ll eat. And sleep. Even if you’re working all the time.”

“I promise.”

They hang up.

David sits in the dark apartment. Two desks. Two chairs. A whiteboard covered in graph diagrams. A prototype that forty-three people are using.

$1,620 in the bank.

Maybe three weeks left.

He opens his laptop. Looks at the user metrics. Marcus logged in again. Forty-five-minute session.

Then another email arrives. From a user he doesn’t recognize.

Subject: “Question about your app”

“Hi, I’m a middle school teacher in Oregon. One of my students showed me your platform. I have a student who’s been struggling all year—tests poorly, homework incomplete, seems checked out. Yesterday I saw him using your app during free period. He was following connections from ‘Why do rockets work’ to physics to space exploration to climate science. He spent an hour. Completely engaged. I don’t know what you’re building, but it’s reaching kids who normal education isn’t reaching. Can I share this with other teachers? - Sarah Chen”

David reads it twice.

Looks at the balance again. $1,620.

Looks at the metrics. Forty-three users. Growing slowly.

The math doesn’t work. Not yet. Maybe not ever.

But somewhere in Oregon, a kid who tests poorly and doesn’t do homework spent an hour learning because he wanted to.

And a teacher wants to share it.

David opens a new document. Types: “December 18 - Teacher outreach plan.”

His fingers move across the keyboard.

Outside, December continues. The city lights shimmer. The cold presses against windows.

Inside, David keeps building.

Not because the numbers add up. Not because success is guaranteed.

Because Marcus exists. Because Sarah Chen exists. Because somewhere, kids who hate school are finding that learning doesn’t have to be a cage.

The balance keeps dropping. The runway keeps shrinking.

But the product is alive.

And that’s enough. For now.

Christmas week.

David doesn’t go home. Can’t afford the plane ticket. Tells his mother he’s too busy. She doesn’t argue.

Alex flies home to see his family. David spends Christmas alone in the apartment. Rice and eggs. No decorations. Just his laptop and the metrics dashboard.

Fifty-eight users now. Forty-six active.

Three teachers have signed up. Two have emailed asking about classroom use.

The product is still fragile. Still incomplete. But it’s growing.

David’s phone buzzes. A message from Alex:

“Merry Christmas. Told my family about the launch. They think we’re crazy. Probably right. But also—my little sister tried the app. Spent two hours on it. She’s 13. She said it’s better than school. That’s something.”

David types back: “Merry Christmas. Tell your sister thank you.”

He sits at his desk. The apartment is quiet. Outside, families are probably having dinner. Opening presents. Being normal.

He thinks about last Christmas. Still at TechCorp. Salary. Benefits. His parents proud of him. The simple life he could have kept living.

Then thinks about this Christmas. Almost broke. Alone in a cold apartment. Building something that fifty-eight people use.

He doesn’t regret it.

The old life was a slow death. This—even the fear, even the uncertainty—is alive.

David opens the product. Types into the search: “Why do we celebrate Christmas?”

The graph blooms. Christianity, winter solstice, cultural traditions, commercialization, family, meaning.

He clicks around. Follows connections. Ends up reading about winter solstice celebrations across cultures.

The product works. Not perfectly. But genuinely.

His phone buzzes again. Not Alex this time. An automated alert.

Bank account balance: $1,520.

Rent due in thirteen days: $1,600.

David closes the alert.

Opens his code editor.

Starts fixing bugs. The connection rendering is still glitchy. Some nodes overlap. Some animations stutter.

He works until 3 AM. Not because he has to. Because he wants to.

The craft itself. The elegance of making something work beautifully. The same feeling from that night in June when he caught himself smiling while debugging.

Life has become amazingly enjoyable. Not despite the difficulty. Because of it.

He saves his work. Closes the laptop.

Tomorrow the sun will rise. The users will keep using. The balance will keep dropping.

But tonight—Christmas night, alone, almost broke—David feels something he hasn’t felt in months.

Not confidence. Not certainty.

Peace.

The kind that comes from knowing you’re exactly where you’re supposed to be, even when nothing makes sense.

He falls asleep at his desk. The apartment cold. The city quiet. The future uncertain.

But the work—the real work—finally aligned with the vision he’s been carrying since he was sixteen years old.

That’s worth more than a warm apartment.

More than certainty.

More than safety.

David sleeps.

And dreams of knowledge graphs blooming across screens. Of kids following their curiosity to places the education system never let them go.

Of freedom spreading like roots through soil.

December 31st.

The year ends not with celebration but with spreadsheets.

David sits at his desk. Alex is back from visiting family. They’re doing end-of-year review.

Users: 67 Active in last 7 days: 51 Teachers using it: 5 Revenue: $0 Checking account: $1,510 Days of runway: 8-9

Alex closes his laptop. “We need to talk about January.”

“I know.”

“You can’t pay rent.”

“I know.”

“I can cover it. One month. But that’s all I can do.”

David looks at him. “Alex—”

“I’m serious. One month. February you’re on your own. If we don’t have revenue or funding by then, I’m getting a job. Not quitting. But I can’t burn through my savings too.”

It’s fair. More than fair. Alex has already given eight months.

“Okay,” David says. “Thank you.”

They sit in silence for a moment.

“What’s the plan for January?” Alex asks.

David pulls up a document. “Teacher outreach. We have five teachers using it. If each one shares with five more, that’s twenty-five teachers. If each teacher has thirty students…”

“That’s seven hundred fifty potential users.”

“Yeah.”

“Still no revenue.”

“No. But proof that it works at scale. That’s what we need for investors.”

Alex nods slowly. “You really think investors will care?”

“I don’t know. But I know we can’t keep doing this without money. So we need to try.”

“Have you thought about what you’ll say? How you’ll pitch?”

David hasn’t. The thought of pitching—of packaging this into metrics and projections and slides—makes him tired.

But the alternative is giving up.

“I’ll figure it out,” he says.

That night, alone, David opens a blank document.

Title: “Investor Pitch - Draft 1”

The cursor blinks.

What does he say? “We have sixty-seven users and no revenue but trust me it’s going to change education”?

No investor will care.

He thinks about Marcus. About Sarah Chen’s student. About Alex’s little sister spending two hours following her curiosity.

How do you turn that into a pitch deck?

David stares at the blank document for twenty minutes.

Then closes it.

Opens his email instead. Scrolls through the messages from users. From teachers.

“This is the first app my son actually wants to use.”

“My students are asking if they can use it in class.”

“I’ve been following connections for an hour. I’m a teacher and I’m learning new things.”

The investors won’t care about these. They want growth metrics. Revenue projections. Market size.

But these are why it matters.

David saves the emails to a folder. Labels it: “Why.”

Then opens the blank pitch document again.

This time, he types:

“The education system measures students by how well they memorize and compete. We’re building the opposite: a tool that starts with curiosity and shows students their interests matter.”

It’s not a pitch yet. But it’s true.

That’s enough to start with.

David types until midnight. The document grows. Still rough. Still missing the numbers investors want.

But honest.

When the clock hits midnight—January 1st, 2026—David is still typing.

A new year.

Nine days until rent is due.

Sixty-seven users who believe in something different.

And a pitch deck that might convince someone to believe too.

Or might not.

Either way, David is still here. Still building.

Still in love with the why.

The year ends. The new one begins.

The work continues.

End of Chapter 9

Chapter 10: The Push

Mon, 10 Nov 2025 00:00:00 GMT

Chapter 10: The Push

January. Balance: $1,510. Rent due in eight days.

Alex covers January—one month grace. After that: revenue, funding, or something.

The prototype is live. Sixty-seven users. Sarah Chen forwarded it to Oregon colleagues—four teachers want to pilot with 120 students starting next week.

The biggest test yet.

Server barely handled 67 concurrent users. 120 might break it. Database upgrade: $80/month.

“If it crashes when teachers are watching, we’re done,” Alex says.

David upgrades. Doesn’t think about February.

Balance: $1,430.

Oregon pilot launches. David watches the dashboard. Users climb: 12, 28, 71, 89.

Server response time spikes. Timeouts. Three error screens.

David’s hands shake. He refreshes.

The graphs render. Slow. But they render.

Peak: 124 concurrent users.

It holds.

First week metrics:

124 students
34-minute average sessions
67% return rate

Teacher feedback: “Engaged.” “Unusual.” “Too early to tell.”

Not transformative. Not revolutionary. Just… engaged.

Balance: $1,210. Rent due in three days.

His mother calls. “Can you pay rent?”

“No.”

Silence. “How much?”

“Sixteen hundred.”

“Your father and I will cover it. This is a loan. And David—this is the last time. If you don’t have money by March, you need a real job.”

Her voice cracks. Terrified, not angry.

“I understand. Thank you.”

“Are you eating?”

“Mostly rice and eggs.”

“You need vegetables. Call me next week.”

“I will. Love you.”

The transfer arrives. $1,600. Balance: $2,810.

Eight weeks until March.

January: The numbers grow. 180 users, 220, 287 by month’s end.

Teacher feedback: behavioral observations. Students asking to use it. Engagement. “Unusual.”

Not revolutionary. Not transformative. Just… engaged.

David pitches fifteen investors. Twelve auto-responses. One rejection. Two interested.

One stops responding. Seedling Ventures schedules a call: February 2nd.

Everything riding on thirty minutes.

Late January. 11 PM. David should sleep. Instead he opens the product.

Types: “Why do I need to learn calculus?”

An interactive demo loads. Car in tunnel. Moving 60 mph. Where is it after 30 seconds?

A slider: “Your guess.”

He guesses 0.5 miles.

“Good! You just used calculus—rate of change to position.”

“But what if speed changes?”

The speed becomes a curve. He can manipulate it. Accelerate. Decelerate. Watch position change in real-time.

Five minutes of playing. Then: “Notice the relationship?”

“When the curve goes up, distance increases faster,” David types.

“Exactly! You discovered the fundamental theorem of calculus.”

Options branch: Physics. Economics. Biology. Programming.

This is it. Not lectures. Discovery. A kid asking “why do I need this?” gets to play first, discover patterns, then learn formulas.

Learning calculus while learning physics, coding, thinking. Multiple skills. Organic. Curiosity-driven.

David writes the investor pitch until 2 AM. The experience, not features. Discovery, not delivery.

Will investors care? Or just want revenue numbers?

He doesn’t know.

But now he can show them what’s different.

February 2nd. Seedling Ventures call.

David hasn’t slept. Ran on two hours last night, fixing a rendering bug he found at midnight.

The Zoom opens. Jessica Martinez—partner at Seedling. Mid-forties. Sharp. Behind her, two other people David wasn’t expecting. Michael Chen, another partner. Sara Rodriguez, analyst.

Three people. Not one. David’s stomach tightens.

“Thanks for making time,” Jessica says. “We’ve been following your progress. Intrigued by the approach. Walk us through it?”

David shares his screen. Opens the prototype. His hands are shaking slightly. He hopes they can’t see.

“Traditional education asks students to memorize,” he says. “We start with curiosity. Let me show you—”

He types into the demo: “Why do I need to learn calculus?”

The interactive loads. Car in tunnel. Variables. The clean interface he spent hours perfecting.

“Students manipulate this themselves,” David says. “They discover the relationship between—”

The screen freezes.

David’s heart stops.

The car animation is stuck. The slider won’t move. The browser is thinking. Thinking. Thinking.

“Sorry,” David says, voice tight. “Let me refresh—”

He refreshes. The page reloads slowly. Too slowly. Thirty seconds of Jessica, Michael, and Sara watching a loading spinner.

Finally, it loads. David tries the slider again.

It works this time. The car moves. Numbers update.

“See,” David says, trying to recover. “They discover rates of change intuitively before we—”

The screen goes white.

David stares in horror. White screen. Nothing. Browser crashed.

“I’m so sorry,” he says. His hands are shaking visibly now. “This was working an hour ago. I don’t know what—”

“Is this a common problem?” Michael asks. Not mean. Just assessing.

“No. I mean—we’ve had server issues with scaling, but the demos have been solid. This is—” David stops. He sounds defensive. Desperate.

Alex jumps in from off-camera. “I can pull up the backup instance. Give us thirty seconds.”

Those thirty seconds feel like an hour.

Jessica waits. Professional. Neutral. The other two are typing. Probably notes. Probably: “Demo crashed. Technical instability.”

Alex gets the backup running. David shares the new screen.

“Okay,” David says. Trying to sound confident. Failing. “Let me try this again.”

This time it works. The calculus demo runs. David talks through it. Shows the knowledge graph. The connections. The curiosity-driven flow.

But the energy is gone. The magic moment ruined. He can see it in their faces. Polite interest. Not excitement.

After fifteen minutes, Jessica stops him. “This is interesting. Can you talk about traction?”

“Three hundred users. Oregon teachers. Thirty-one minute average sessions. High engagement.”

“Revenue?”

“None yet. But we have a school district interested. Willow Creek. 800 students. Free pilot, then paid contract if it works.”

“And your runway?”

David hesitates. Should he lie? Stretch it?

“Six weeks,” he says. “Maybe seven.”

Silence.

Michael speaks. “That’s not a lot of time.”

“I know. But we’re close. This pilot could be the proof point we need.”

Sara jumps in. “What if the pilot doesn’t convert? What’s your backup plan?”

David doesn’t have one. Can’t say that.

“We believe in the product. The engagement metrics show students want this. It’s a matter of finding the right school willing to pay for it.”

More silence.

Jessica exchanges a glance with Michael. Some unspoken conversation.

“Okay,” Jessica says. “Here’s where we are. The mission resonates. The approach is interesting. But the demo crashing mid-pitch is concerning. And six weeks is not enough time to prove this out.”

David’s chest tightens. This is a rejection. He can feel it coming.

“However,” Jessica continues, “I do think there’s something here. What if we did a bridge round? Small. $50k. Six months. Convertible note at a $5M cap. That gives you runway to run the pilot and prove schools will pay. If you get to sustainable revenue, we’ll lead your seed round.”

David doesn’t dare speak. Afraid his voice will crack.

Alex off-camera: “What’s the minimum traction you’d need to see for the seed?”

“Three to five paying schools. $20k minimum annual revenue. Proof that the model works.”

“That’s doable,” Alex says.

Jessica looks at David. “But I need to be clear. This is conditional. The demo crashing today makes me nervous. If there are technical stability issues, or if the pilot fails, we’re out. This bridge is a bet on execution. Can you deliver?”

Can he deliver? David doesn’t know. Six weeks ago he was in the gray. Two months ago the prototype failed user testing. Every step forward reveals new problems.

But Jessica is offering $50,000. Six months of breathing room. A chance.

“Yes,” David says. “We can deliver.”

“Alright.” Jessica types something. “We’ll send a term sheet by end of week. Get it signed and we’ll wire the funds. But David—” She looks directly at him. “Fix the technical issues. If you’re pitching schools and the demo crashes, you’re done. Understand?”

“Understood.”

The call ends.

David sits in silence. Stares at the blank Zoom screen.

“That was close,” Alex says, coming into frame.

“Close to what? Success or disaster?”

“Both.”

David opens the browser console. Scrolls through the error logs. There—a memory leak. He’s been running the demo dozens of times while testing. The browser couldn’t handle it.

A bug he should have caught. Would have caught if he’d slept. If he’d tested properly.

Instead, he almost blew the entire pitch.

“$50k,” Alex says. “That’s huge.”

“If we can fix the bugs. If the pilot works. If schools actually pay.”

“One step at a time.”

David nods. But his hands are still shaking.

They almost lost it. One crashed demo away from Jessica saying “thanks, but no thanks.”

And now—now they have six months to prove this works. To get paying customers. To show that ten months of suffering wasn’t for nothing.

The pressure is enormous. The margin for error is zero.

But they have $50,000.

They have oxygen.

“We should celebrate,” Alex says. “This is good news.”

“I need to fix the memory leak first.”

“David—”

“I almost blew it, Alex. I almost crashed the only pitch that mattered. I can’t—” He stops. Takes a breath. “I need to fix this. Then we celebrate.”

Alex doesn’t argue.

David opens the code. Finds the leak. Fixes it. Tests it twenty times. Thirty. Fifty.

Doesn’t crash.

Around 7 PM, he finally closes the laptop.

“Okay,” he says. “Now we celebrate.”

They order pizza. The good kind. Not the cheapest option. Actual toppings.

While they wait, David sits with the reality of it.

They got funding. Barely. By the thinnest margin. One crashed demo away from failure.

But they got it.

$50,000. Six months. One more chance to prove this vision is real.

Not because he pitched perfectly. But because Jessica saw something worth betting on. Even after the demo crashed. Even after the disaster.

She believed enough to take the risk.

Now David has to prove she was right.

The term sheet arrives three days later. David reads it seventeen times. Signs it with a shaking hand.

The wire transfer hits on February 15th. $50,000. Six months of runway. Conditional on execution.

Alex nods off-screen.

“We’re in,” David says quietly.

But this time, he knows what he’s in for. The pressure. The expectations. The constant fear of technical failures. The knowledge that one more crashed demo could end everything.

Still.

They’re alive.

For now.

$50,000. Six months. Conditional on revenue.

Not a full seed. But oxygen.

David pays back his parents. Balance: $48,710.

Six months to prove this works.

Funding closes February 28th. $50k.

David repays his parents: $1,600. Balance: $48,490.

His mother calls. “You got funding?”

“A bridge round. Enough to keep going.”

“I’m proud of you. Don’t waste it.”

“I won’t.”

Mid-February. Email from Principal Anderson, Willow Creek School District:

“800-student pilot. Grades 6-8. Free trial starting March 30th. If it works, paid contract for next year. $8-10 per student. Interested?”

David reads it three times. This is the path to revenue.

“Absolutely.”

February 18th. District call.

Anderson: “What makes this different?”

David demos the calculus path. “They discover patterns before we teach formulas. Thirty-one minute sessions. Not forced. Chosen.”

Hayes (tech director): “State standards?”

“We don’t align directly. But when a kid spends 45 minutes following curiosity from calculus to physics to programming—they learn. Because they want to.”

Anderson: “Four-week pilot. 800 students. Starting March 30th. Free. If it works, $8/student annually.”

$6,400 first year. Not profit. But proof.

“We’re in.”

Five weeks to scale for 800 concurrent users.

Five weeks to prove this works.

February: Server upgrades. Security audits. New interactive demos.

Oregon metrics steady: 31 minutes, 71% return, “unusual engagement.”

Still no deep learning insights. Just engagement.

David works 14-hour days. Climate simulators. Music visualizers. Historical timelines.

Each following the pattern: Curiosity → Interaction → Discovery → Knowledge.

Math + coding. Science + systems thinking. History + data analysis.

Won’t know if it works until March. Until 800 students show if this vision is real.

February 28th. Evening.

David sits at his desk. The funding closed this morning. His parents are repaid. The servers are upgraded. The district pilot is scheduled.

Everything that can be ready is ready.

Now he waits.

His phone buzzes. An email from one of the Oregon teachers.

Subject: “Interesting observation.”

He opens it.

“David—I’ve been watching my students use your platform for six weeks now. I wanted to wait before saying anything. Here’s what I’m noticing: My students who usually struggle are asking different questions. Not ‘what’s the right answer?’ but ‘what happens if I change this?’ One student spent three weeks exploring climate science through your simulators. He failed my last test. But yesterday he explained the greenhouse effect to the class better than I could have. He didn’t memorize it. He discovered it. I don’t know what you’re building, but it’s reaching kids differently. - Mr. Thompson”

David reads it twice.

Six weeks. That’s how long it took. Six weeks of consistent use before the learning showed up. Before the difference became visible.

Not immediate feedback. Not instant transformation.

Slow. Organic. Real.

A student who fails tests but understands deeply. Who can explain concepts because he discovered them himself.

That’s the vision. That’s what the platform was built for.

David saves the email. Adds it to the folder labeled “Why.”

The district pilot starts in four weeks. Eight hundred students. Four weeks of use. If Mr. Thompson’s observation is the pattern, they won’t see the deep learning until late April. Until after the pilot technically ends.

But if it’s real—if students are actually learning differently—it’ll show.

In time.

David closes his laptop. The apartment is quiet. Alex has gone home. The city glows through the window.

Tomorrow he’ll keep preparing. Keep building. Keep hoping the vision holds.

But tonight—for the first time in weeks—David feels something that isn’t just anxiety.

Not confidence. Not certainty.

Just… possibility.

The kind that comes from seeing one student fail a test but understand the material. From knowing that learning and testing aren’t the same thing. From building something that values discovery over memorization.

It might work.

Or it might not.

But at least now, he has time to find out.

David turns off the lights. The balance: $48,710.

The pilot: four weeks away.

The answer: coming soon.

He sleeps better than he has in months.

End of Chapter 10

Chapter 11: The Boy

Mon, 10 Nov 2025 00:00:00 GMT

Chapter 11: The Boy

March.

Five weeks to prepare for 800 students.

David and Alex work like the deadline is real—because it is. The platform that handled 300 concurrent users in February needs to handle 800 by March 30th.

The servers get upgraded again. The database architecture gets rebuilt. The security audit reveals seventeen vulnerabilities—they fix sixteen, document the seventeenth as “acceptable risk for beta.”

The interactive demos get tested obsessively. Car-tunnel calculus. Climate simulators. Music theory visualizers. Each one needs to work smoothly, load quickly, handle student experimentation without breaking.

David runs load tests at 2 AM. Simulates 800 concurrent users clicking, scrolling, manipulating variables. The server response time hovers around 1.3 seconds under peak load. Slow. But functional.

On March 15th, Principal Anderson sends the launch plan. Teachers will introduce it during class. Students can use it during free periods, study hall, at home. Four weeks of access. Then they’ll evaluate.

The metrics they’ll watch: engagement, session time, teacher feedback, student sentiment.

Not test scores. Not learning outcomes. Those take too long to measure.

Just: do students use it? Do they keep using it? Does it feel different?

Four weeks to prove the vision is real.

March 30th. Launch day.

The platform goes live for Willow Creek Middle School at 8 AM Pacific.

David sits at his desk, dashboard open, watching the active user count climb.

8:15 AM: 47 users 8:30 AM: 143 users
9:00 AM: 287 users 9:30 AM: 412 users

The server response time: 1.1 seconds. Holding steady.

At 10:17 AM, something spikes. Response time jumps to 2.4 seconds. A rendering bug in the knowledge graph visualization. David’s hands fly across the keyboard. Patches the code. Deploys the fix.

Response time drops back to 1.2 seconds.

By noon: 618 active users.

By 2 PM: 731 active users.

Peak concurrent: 743.

The server holds.

David closes his laptop at 4 PM. His hands are shaking from caffeine and adrenaline. But it worked. No crashes. No catastrophic failures.

743 students used it on day one.

Now they wait to see if those students come back.

Week one passes in numbers.

Day 2: 612 active users
Day 3: 589 active users

Then, on Day 3, at 11:47 AM Pacific, the server crashes.

Not a slow degradation. Complete failure. The database connection times out. Eight hundred students trying to log in during lunch period. The load balancer can’t handle it.

David’s phone explodes with alerts. Server down. Database unreachable. Error rate: 100%.

He’s at his desk. Alex is across town at a coffee shop. David’s hands are shaking as he opens the server dashboard.

Everything is red. Every metric screaming failure.

He calls Alex. “The server’s down.”

“What? How?”

“Too much load. The database can’t handle concurrent connections. We optimized for 300 users, not 800.”

“Can you fix it?”

David is already in the AWS console. Scaling up the database instance. It’ll take ten minutes minimum. Ten minutes of 800 students getting error screens.

“I’m trying. But David—” Alex’s voice is tight. “Principal Anderson is probably seeing this right now. Teachers are probably texting him. We’re three days into the pilot and we just went completely dark.”

David knows. He knows exactly what this means. The district is evaluating them. Trusting them. And on Day 3, complete technical failure.

The database upgrade finishes. Eight minutes. He restarts the application server.

The site comes back online. 11:59 AM. Twelve minutes of downtime during peak usage.

David sits back. Stares at the dashboard. Everything green again. But the damage is done.

His phone rings. Unknown number. He answers.

“David? This is Principal Anderson.”

David’s stomach drops. “Principal Anderson. I know what happened. I’m so sorry. We had a server—”

“I know. My tech director got alerts. Students couldn’t access the platform for about ten minutes. What happened?”

“We underestimated the load. We optimized for our Oregon numbers—300 concurrent users. With 800 students all trying to log in during lunch, the database couldn’t handle it. I’ve scaled it up. It won’t happen again.”

Silence on the other end.

“Principal Anderson?”

“David, I appreciate the quick fix. But this is a concern. We’re three days in. If this happens again—especially during a class period when teachers are depending on it—that’s a problem. Do you understand?”

“Yes. Absolutely. I’ve upgraded the infrastructure. We can handle 2,000 concurrent users now.”

“I hope so. I’ll be monitoring this. If we have another outage, we’ll need to reassess.”

The call ends.

David sits in the quiet apartment. His heart is pounding.

They almost lost it. Three days into the most important pilot. One more crash and Anderson pulls out. No contract. No revenue. Investors walk.

Everything riding on technical stability. And he almost blew it.

Alex texts: “How bad?”

David types back: “Bad. Anderson called. One more crash and we’re done.”

“Fuck.”

“Yeah.”

David spends the next three hours load testing. Simulating 1,000 concurrent users. 1,500. 2,000. The server holds.

But the fear doesn’t go away. Every alert makes him jump. Every notification makes his stomach clench.

They’re back online. But they’re one technical failure away from disaster.

Day 4: 623 active users
Day 5: 681 active users

No crashes. The upgraded infrastructure holds.

But David checks the dashboard obsessively. Every hour. Every thirty minutes. Every time his phone buzzes.

The return rate: 73%.

Average session time: 28 minutes.

Teachers send brief updates:

“Students are engaged during study hall.”

“A few asked if they could show their parents.”

“One student spent an entire period exploring climate science.”

Engaged. Exploring. Using it.

The same words from Oregon. Behavioral observations. Not learning insights yet.

But overshadowing everything: the memory of those twelve minutes. The server down. The error screens. How close they came to losing everything.

David can’t forget it. Every time he sees a positive teacher update, he thinks: Unless the server crashes again.

Every time a student uses the platform, he thinks: What if it breaks?

The success is real. But so is the fragility.

One crash away from collapse.

David watches the numbers. Tries to see patterns. Which topics are popular? Which demos get the most interaction? Where do students spend time?

The most popular starting curiosities:

“Why do we need to learn this?” (math-related)
“How does climate change work?”
“Why do people fight wars?”
“How does music sound good?”
“Why do we dream?”

Students aren’t just clicking the first thing they see. They’re asking real questions. The questions they actually care about.

That’s something.

David tries not to think about the four-week deadline. Tries to focus on what he can control: fixing bugs, improving demos, watching the data.

But the anxiety is there. Constant. Background noise that won’t turn off.

What if four weeks isn’t enough? What if students engage but don’t learn? What if this is novelty that wears off?

What if his mother was right all along?

Week two. Early April.

The numbers stay consistent. 600-700 daily active users. 28-32 minute sessions. 70-75% return rate.

Teachers start sending more detailed observations:

“A student who never participates asked if he could present what he learned about sound waves.”

“I noticed two students collaborating on the climate simulator, debating what would happen if they changed variables.”

“One girl said she finally understands why math matters. She spent two weeks following her curiosity from ‘why do I need algebra’ to real-world applications.”

The feedback is getting warmer. More specific. Students aren’t just using it—they’re connecting with it.

But David still hasn’t heard the thing he’s waiting for. The deep transformation. The moment a student articulates what Mr. Thompson described: “He didn’t memorize it. He discovered it.”

Principal Anderson sends a check-in email on April 8th:

“Initial response is positive. Teachers like it. Students are engaged. We’ll do a formal evaluation at the end of week four. Pending that review, we’re prepared to discuss a contract.”

Prepared to discuss. Not “we’ll definitely sign.” Prepared.

David reads it three times. Tries to parse the tone. Is that encouraging? Cautious? Noncommittal?

He can’t tell.

Alex reads it over his shoulder. “That’s good news.”

“It’s neutral news.”

“Neutral is better than negative.”

David nods. Tries to believe it.

April 12th. Week three.

Ms. Ramirez—the assistant principal—emails David:

“We’re conducting student feedback sessions this week. Would you be available to join one via Zoom? The students know you built this. A few asked if they could talk to you.”

Students want to talk to him.

David’s chest tightens. This could be the validation. Or it could be complaints. Confusion. Questions about why it’s different from what they’re used to.

He types back: “Yes. When?”

“Tomorrow, 2 PM Pacific. I’ll send the Zoom link. It’ll be 8-10 students. Voluntary participants.”

Voluntary. Students who chose to be there. That’s probably good.

Probably.

April 13th. 1:55 PM.

David sits at his desk. The Zoom link is open. His camera is off. His hands are cold.

Alex is on the couch, watching. “You got this.”

“What if they hate it?”

“They don’t hate it. They asked to talk to you.”

“What if they—”

“David. Breathe.”

David takes a breath. At 2:00 PM, he joins the call.

The screen fills with faces. Eight students. Ages 12-14. Some look curious. Some look bored. One is clearly there because a teacher told them to be.

Ms. Ramirez appears in a small box. “Everyone, this is David. He built the platform you’ve been using. He wants to hear what you think.”

Silence. Middle schoolers staring at a stranger on a screen.

Then a girl—maybe 13—speaks. “Can I ask a question?”

“Of course,” David says.

“Why did you make this?”

Straight to it. No small talk.

David pauses. How much honesty can he give?

“I hated school when I was your age,” he says. “Not because I didn’t want to learn. Because school never asked what I was curious about. It just told me what I was supposed to know. I wanted to build something different.”

Another student—a boy, 12 or 13—leans forward. “So we can just learn whatever?”

“Not whatever. But you start with what you’re curious about. Then we show you where that leads.”

“That’s weird,” another girl says. Not mean. Just factual.

“Yeah,” David says. “It is weird. How does it feel?”

Silence. They’re thinking. Probably not used to adults asking how things feel.

Then a boy in the back—quiet until now, maybe 14—speaks. His voice is soft. Careful.

“It feels like the first time anyone asked what I wanted to learn.”

David’s breath catches.

The boy continues. “Like—in school, it’s always ‘here’s the chapter, here’s the test, here’s what you need to know.’ Nobody asks if I care. Nobody asks what I’m curious about. Your thing asks. That’s different.”

Ms. Ramirez is smiling. “Can you tell David what you’ve been exploring?”

The boy hesitates. “I started with ‘why do we need to learn math.’ I thought it was going to be the normal answer—like, ‘you need it for jobs’ or whatever. But instead it showed me the car in the tunnel thing.”

David’s heart is pounding. The calculus demo.

“I played with it for like an hour,” the boy continues. “Changing the speed, watching how the distance changed. And I realized—math isn’t about memorizing formulas. It’s about understanding how things change. I never got that before.”

He pauses. Looks down. “I’m not good at math. Like, I fail tests. My teachers think I’m not trying. But I am trying. I just don’t understand why I’m supposed to care about derivatives and integrals. But when I saw the car thing, I got it. It’s about rates. About tracking change. That’s actually useful.”

David doesn’t trust his voice. He nods.

The boy keeps talking. Like something opened and he can’t stop.

“Before this, I thought school was about being better than other people. Getting higher scores. Beating other kids. My parents keep saying I need to work harder, get better grades, get into a good high school. They say if I don’t, I’m going to fall behind. But behind what? It’s like we’re all in a race and nobody knows where we’re going.”

Another student nods. The girl who spoke first says quietly, “Yeah.”

The boy looks directly at the camera. At David. “Your app doesn’t feel like that. It feels like I’m learning because I want to understand things. Not because someone’s grading me. Does that make sense?”

David’s throat is tight. “Yeah. It makes sense.”

“I told my mom about it,” the boy says. “She asked if it’s going to help my grades. I said I don’t know. But I told her I actually care about what I’m learning now. That has to count for something, right?”

David can’t speak. The room is blurring.

This is it. This is the thing he’s been building toward.

Not metrics. Not revenue. This: a 14-year-old boy who thought learning was about competition discovering it’s about curiosity. Who failed tests but understands deeply. Who spent an hour playing with a car simulator and learned what calculus actually means.

A boy who sounds exactly like David at that age. Trapped in a system that measured him against others. Told his worth was determined by rank. Never asked what he cared about.

Now free. Or starting to be.

Ms. Ramirez speaks. “What the students have been telling me—and what I’m seeing in my observations—is that your platform reaches kids differently. The students who struggle in traditional assessments are engaging with material at a deep level. They’re asking questions. Exploring. One student who barely speaks in class spent 90 minutes following his curiosity from ‘how does electricity work’ to circuit design to power grids to renewable energy. He built a simple circuit simulator using the coding tools in your platform. He’d never coded before.”

Another student—a girl who’s been quiet—raises her hand. “I like that I can see how things connect. Like, in history class we learn about wars, but we don’t learn why people actually fight. Your thing showed me how economics and resources and politics all connect to conflict. It’s like—I could see the whole picture instead of just memorizing dates.”

The boy from earlier speaks again. His voice is stronger now. “I think what I’m trying to say is—before this, I thought I was bad at learning. Like, my brain just doesn’t work the way school wants it to. But your app showed me I’m not bad at learning. I’m just curious about different things than what’s on the test.”

He pauses. Then: “My choice is determined by what I know, right? And knowing more means I have more choices. That’s what you’re trying to show us.”

David’s vision blurs completely. He has to look away from the camera.

Those words. Almost exactly the words from the framework. The vision he’s been carrying since he was 16. The thing he wanted someone to tell him when he was this boy’s age.

Your choice is determined by what I know. Knowing more means more choices.

Not “learn this to beat others.” Not “memorize this for the test.”

But: knowledge gives you freedom. Understanding gives you options. Learning is power, not performance.

And this boy—this 14-year-old who fails tests but understands deeply—he discovered it himself. Through the platform. Through curiosity.

David realizes the silence has stretched too long. He clears his throat. Tries to speak.

“Yeah,” he manages. “That’s exactly right.”

The boy smiles. Small. Genuine.

Ms. Ramirez looks at the clock. “We’re running over. But I think David has heard what he needed to hear. Thank you all for sharing.”

The students wave. Log off. The screen empties until it’s just Ms. Ramirez.

“They don’t usually open up like that,” she says. “But they feel ownership of this tool. Like it’s theirs. That’s rare.”

“Thank you for setting this up,” David says. His voice sounds distant. Like someone else is speaking.

“We’ll have our final evaluation next week. But between us—I think we’re going to move forward with a contract. This is reaching students we weren’t reaching before.”

The call ends.

David sits in silence. The apartment is very quiet.

Alex is watching from the couch. “You okay?”

David shakes his head. Not because he’s not okay. Because he doesn’t have words.

That boy. That exact boy. The one who thought he was bad at learning. Who thought school was about competition. Who discovered that knowledge gives you choices.

David was that boy. Ten years ago. Sixteen years old in a library, hearing Steve Jobs’s voice, carrying a yearning he couldn’t name.

And now—because of this platform, because of ten months of darkness and doubt and almost giving up—that boy exists in someone else.

The boy he was is free in this child.

Every sleepless night. Every moment in The Other Side. Every time he wanted to quit. Every dollar burned. Every relationship strained. Every second of doubt.

It all crystallizes into one overwhelming realization:

This is why.

Not the funding. Not the contract. Not proving anyone wrong.

This: liberating the next generation from the cage that held him.

There is no greater joy than this.

David doesn’t move for a long time.

Just sits. Breathing. Letting it settle.

Alex walks over. Puts a hand on his shoulder. Doesn’t say anything. Doesn’t need to.

After a while, David opens his laptop. Pulls up the recording of the call. Finds the moment the boy said: “My choice is determined by what I know.”

Saves the clip. Labels it: “Why.”

Then he opens a new email. To Principal Anderson.

“Thank you for the opportunity to talk with students today. I heard exactly what I needed to hear. Whatever you need from us to make the contract work, we’ll make it happen.”

Send.

He closes the laptop. Looks at Alex.

“It’s real,” David says. Quietly. “The vision is real.”

Alex nods. “Yeah, man. It is.”

The final evaluation happens on April 20th.

Principal Anderson, Ms. Ramirez, Mr. Hayes (the tech director), and three teachers on the Zoom call.

David and Alex present the metrics:

800 students enrolled
Average 650 daily active users over 4 weeks
74% return rate
32-minute average sessions
89% of students used it at least twice per week
Zero critical bugs, three minor issues (all resolved)

Then the qualitative feedback:

7 out of 10 teachers report increased engagement
Students asking to use it during free time
Multiple examples of deep learning (the boy’s calculus discovery, the circuit builder, the climate debater)
Students who struggle with traditional assessments showing strong conceptual understanding

Mr. Hayes asks the hard question: “What about test scores? Can you show learning outcomes?”

David takes a breath. “Four weeks isn’t enough time to measure that. But what we can show is that students who historically disengage are now spending 30-60 minutes voluntarily exploring concepts. That’s the foundation of learning. The test scores will follow.”

Silence. The administrators exchange glances.

Then Principal Anderson speaks. “We’d like to move forward with a contract for next school year. Full middle school—grades 6-8. Approximately 800 students. We can budget $8 per student annually. That’s $6,400 for the year. We’ll need to finalize terms, but we’re prepared to commit.”

David’s heart is pounding. “We accept.”

“We’ll send the contract next week. Pending legal review, we can sign by end of month.”

The call ends.

David and Alex sit in silence.

Then Alex starts laughing. “We have a customer. A real, paying customer.”

“$6,400.”

“It’s not about the money. It’s about the proof. One school pays, others will follow.”

David nods. Opens his email. Already there are two new messages.

One from a principal in Washington state: “Heard about your pilot in Oregon. Interested in learning more.”

Another from a teacher in California: “Can I share your platform with my district’s curriculum director?”

Word is spreading. Organically. Because it works.

That night, David sits alone in the apartment.

Alex has gone home to celebrate with his family. The city is quiet outside.

David opens his phone. Scrolls through the saved emails. Marcus from December. Mr. Thompson after six weeks. The boy from today.

Three students. Three moments. Three variations of the same realization: I’m not bad at learning. I’m just curious about different things.

He thinks about himself at 16. In that library. Hearing Jobs’s voice. The quiet yearning that there was another way to live.

He thinks about Marcus in high school. The numb look when he got 94 instead of 98. Four points. The education system that sorted people like products.

He thinks about his mother’s fear. His father’s silence. Alex’s support. The 3 AM moment when he almost gave up.

All of it leading here. To this moment. To 800 students using a platform that asks what they’re curious about. To one boy discovering that knowledge gives him choices.

David opens a new document. Types:

“The belly of the whale is quieter than you’d think.”

He stares at the sentence. The first line of the story he might tell someday. The pattern itself, offered to whoever comes next.

But not yet. The story isn’t finished.

He deletes the line. Saves the blank document as “Someday.”

Tonight is for sitting with the joy. The overwhelming, indescribable feeling of seeing your vision reflected in someone else’s life.

Of knowing that the suffering had purpose.

Of understanding that every moment in the darkness was necessary to get here.

David closes his laptop. The apartment is dark. The city glows through the window.

His checking account: $43,120 (after three weeks of expenses).

Active users: 840 (Oregon teachers + Willow Creek).

Paying customer: 1 (pending contract signature).

Revenue: $6,400 annually (starting fall).

The numbers still don’t make sense. One contract isn’t enough. They need ten, twenty, fifty schools to be sustainable.

But now it’s possible. Now there’s a path.

David thinks about the boy. My choice is determined by what I know.

That boy will go home tonight and maybe tell his parents what he learned. Maybe show them the car-tunnel demo. Maybe explain derivatives in a way that makes sense because he discovered them himself.

He’ll go to school tomorrow and maybe ask different questions in math class. Maybe see formulas differently. Maybe start believing he’s not bad at learning.

And somewhere—in ten years, twenty years—he might remember the platform that asked what he was curious about. That showed him knowledge gives choices. That freed him from the cage.

He might become the person he’s supposed to be instead of who the system tried to make him.

That’s the return with the boon. Not the money. Not the success metrics.

This: setting someone free.

David sits in the dark. Doesn’t turn on lights. Just sits with the weight and grace of it.

The journey isn’t over. There’s still so much to build. So many students to reach. So many schools to convince.

But tonight—just tonight—he lets himself feel it.

The joy. The overwhelming, terrible, beautiful joy of knowing he built something that matters.

Of hearing his younger self freed in another child.

Of understanding what Jobs meant: “The only way to do great work is to love what you do.”

David loves this. Not the struggle. Not the uncertainty. But the work itself. The craft of building something that helps people become who they’re meant to be.

That’s enough.

For tonight.

For now.

David closes his eyes. Sleeps deeply. Dreams of knowledge graphs blooming. Of curious questions spreading like light. Of cages opening, one student at a time.

Tomorrow the work continues.

But tonight, he rests.

End of Chapter 11

Chapter 12: The Return

Mon, 10 Nov 2025 00:00:00 GMT

Chapter 12: The Return

May.

Balance: $41,300. Willow Creek contract signed. Three more districts in conversation. 1,847 active users.

David should feel triumphant. Instead he’s staring at an email from Principal Hayes at Willow Creek, subject line: “Concerns about implementation.”

“We’re getting pushback from some parents who feel the platform doesn’t align with state standards. One parent complained their daughter spent 40 minutes ‘playing with climate graphs’ instead of studying for the science test. Can we schedule a call to discuss?”

His first paying customer. Two weeks into the contract. Already problems.

David’s coffee has gone cold. It’s 9 AM. Alex won’t be here until ten. The apartment feels smaller than it used to—two desks, cables everywhere, a whiteboard covered in customer pipeline diagrams.

He types back: “Of course. What time works?”

The reply comes immediately: “Today at 2 PM?”

Five hours to figure out how to explain that 40 minutes understanding climate systems IS studying. That the test scores are lagging indicators. That real learning looks different than what parents expect.

Five hours to convince his only paying customer not to cancel.

David closes his laptop. Walks to the window.

The city is bright with late spring. People heading to offices, living normal lives. He wonders how many of them worry their customers will fire them before they’ve even started.

His phone buzzes. His mother.

He answers. “Hi, Mom.”

“David. You sound tired.”

“I’m okay.”

“Are you eating real food? Not just rice and eggs?”

Despite everything, he almost smiles. “Yes. I had a salad yesterday.”

“One salad doesn’t count.” A pause. “How is the company?”

How is the company? Great question. They have one signed contract, three maybes, and a customer already second-guessing. They have 1,847 users but zero revenue until fall. They have enough runway to last six months if nothing goes wrong.

“It’s good,” he says. “We signed our first contract.”

“That’s wonderful.” Her voice warms. Actual pride. “How much?”

“$6,400 for the year.”

Silence. He can almost hear her doing the math. Two people. One year. $6,400.

“That’s… a start,” she says carefully.

“Yeah. We have three more schools interested. If they all sign, that’s close to $30,000 annually.”

“And you need how much to live?”

“More than that. But it’s proof of concept. Once we have ten schools, we can raise a real seed round.”

Another pause. “Your father wants to know if you’re still planning to come home for his birthday.”

David looks at his calendar. June 14th. Three weeks away. The plane ticket would be $300. Four days of not working.

“I’ll try.”

“David—”

“Mom, I want to. I just… I have a call with our customer in five hours. They might cancel. I can’t think about birthdays right now.”

He hears her take a breath. “You got what you wanted. You built your company. But you’re still exhausted. You’re still stressed. When does it get easier?”

Good question. When does it get easier?

“I don’t know,” he says honestly. “But I’m okay. I promise.”

“Okay doesn’t mean happy.”

“No. But it means I’m doing what I’m supposed to be doing.”

She sighs. “Call your father. Even if you can’t come. He worries.”

“I will.”

They hang up.

David sits back down. Opens the email from Hayes. Reads it again.

A parent complained. One parent. Out of 800 students. One parent who thinks 40 minutes exploring climate systems is “playing” instead of studying.

Before, this would have devastated him. Proof that people don’t get it. That the vision is too different. That he should just build another homework app.

But now—after the boy who said “my choice is determined by what I know,” after Mr. Thompson’s student who failed tests but understood deeply—now David knows the difference between noise and signal.

One parent complaining means 799 aren’t. Or at least aren’t complaining yet.

Still. He has to handle this carefully. One contract isn’t enough to survive on. He needs Willow Creek to renew. To expand. To tell other schools it works.

He can’t afford to lose this.

Alex arrives at 10:03 carrying breakfast burritos. “Thought you might be spiraling.”

“I’m not spiraling.”

“You have that look.”

David shows him the email. Alex reads it. Hands the phone back.

“One parent.”

“Our only customer.”

“With 800 students. One parent complained. That’s a 0.125% complaint rate.”

“Hayes wants a call at 2 PM.”

“So we do the call. Explain the pedagogical approach. Show the engagement data. This is normal, David. Customers push back. We adjust.”

“What if they cancel?”

“They won’t cancel.” Alex unwraps his burrito. “You talked to those kids. You heard what they said. Hayes knows this is working. One parent complaint isn’t going to change that.”

“But what if the parent is loud? What if they get other parents worried?”

“Then we do a parent information session. Show them what their kids are learning. The data shows students are engaged. Engagement predicts learning. The test scores will follow.”

Alex makes it sound simple. Maybe it is simple. Maybe David is spiraling.

He takes a bite of his burrito. “Thanks.”

“For what?”

“For not letting me catastrophize.”

“That’s what co-founders do.” Alex opens his laptop. “Also, I wanted to talk to you about something.”

The shift in tone makes David look up. “What?”

“We have three schools in the pipeline. If they all sign, that’s five customers. Maybe 3,000 students. We can’t support that with just the two of us.”

“We’ve been supporting 1,800 users—”

“Barely. You worked 90 hours last week fixing bugs. I’m doing all the customer support, content curation, and sales. It’s not sustainable.”

David sets down his burrito. “What are you saying?”

“I’m saying we need to hire. At minimum, a customer support person. Maybe a content developer.”

“We can’t afford that. We have six months of runway.”

“If we don’t hire, we can’t scale. And if we can’t scale, we’re just a lifestyle business with two very stressed founders.”

“A lifestyle business that’s actually helping kids—”

“I’m not saying we abandon the mission. I’m saying we need help. We have 1,847 users, David. That’s proof this works. But we’re hitting a ceiling because there’s only two of us.”

The conversation feels familiar. The same argument they’ve had in different forms for months. David wanting to stay small and perfect. Alex wanting to grow and scale.

“How much would it cost to hire someone?” David asks.

“Depends. A contractor for customer support, maybe $3,000 a month. A full-time content person, $50-60k annually.”

David does the math. That’s half their runway. Gone in six months just on salaries.

“We’d need to raise more money.”

“Yeah. That’s why I’m saying we need to nail these three schools. Show traction. Then we can raise a proper seed round. $500k to $1M. Hire a small team. Scale properly.”

“I thought you said we couldn’t take VC money. That they’d pressure us to compromise the vision.”

“I said we need to be careful who we take money from. But if we find the right investors—people who actually believe in the mission—we can scale without selling out.”

David wants to argue. But Alex is right. They can’t do this alone forever. The product is growing. The demand is real. They need help.

“Okay,” David says. “But let’s get through this Hayes call first. Make sure we still have a customer.”

2 PM. The Zoom call.

Principal Hayes joins with two other people. David’s stomach drops. He was expecting a one-on-one. This is a committee.

“David, thanks for making time,” Hayes says. “This is Jennifer Park, our curriculum director, and Tom Bradley, he’s on our school board. We wanted to discuss some concerns.”

David nods. Tries to look calm. “Of course. What’s going on?”

Jennifer speaks first. “We’ve been tracking usage data. Students are engaged—that’s clear. But we’re getting questions from parents about whether the platform aligns with state learning standards. One parent was particularly vocal at last night’s board meeting.”

Tom leans forward. “Her concern is that her daughter spent significant time on your platform but then performed poorly on a science test. The parent feels the platform is a distraction, not a learning tool.”

David takes a breath. Alex is off-camera, listening. They practiced this.

“Can I ask what the student was exploring?” David says.

Jennifer checks her notes. “Climate systems. Specifically, she was using the interactive climate simulator for about 45 minutes.”

“And what was the test on?”

“Photosynthesis and cellular respiration.”

David nods slowly. “So the student was deeply engaged in learning about climate systems—which connects to biology, chemistry, earth science, and systems thinking—but she did poorly on a memorization test about a different topic.”

“That’s the parent’s concern,” Tom says. “That the platform isn’t aligned with what we’re testing.”

“Right. Because we’re not trying to align with tests. We’re trying to create actual understanding.”

The words come out harder than he intended. Jennifer’s eyes narrow slightly.

David continues, softer. “I’m not criticizing your curriculum. But the question is: what matters more? That a student can memorize the steps of photosynthesis for a test? Or that she spends 45 minutes voluntarily exploring climate systems, learning how carbon cycles affect atmospheric composition, and building mental models of complex systems?”

“Both matter,” Jennifer says. “But parents expect test scores.”

“I understand. And I think you’ll see test scores improve over time. But not immediately. Real learning—the kind where students develop deep understanding and genuine curiosity—that takes longer to show up on tests.”

He pulls up the engagement data. “Look at this. Your students are spending an average of 32 minutes per session. They’re returning 74% of the time. For voluntary use, that’s extraordinary. That means they’re learning because they want to, not because they have to.”

“But how do we measure what they’re learning?” Tom asks.

“You’re already seeing it. Teachers have told us about students who never participate suddenly presenting what they learned. Students collaborating. Asking different questions. That’s learning. The test scores will follow.”

Hayes has been quiet. Now he speaks. “We did hear from Ms. Ramirez about the student feedback session. The students were… articulate. About what they were getting from the platform.”

“They were,” Jennifer admits. “Unusually so.”

“So here’s my question,” David says. “Do you want students who can pass tests? Or students who can think? Because our platform is designed to teach thinking. To show students that their curiosity matters. To help them build mental models of how the world works. That’s harder to measure on a multiple-choice test. But it’s what actually matters.”

Silence.

Tom speaks first. “The parent isn’t going to accept that answer.”

“No,” David agrees. “She won’t. Because she’s been told her daughter’s worth is measured by test scores. We’ve all been told that. But it’s not true. And somewhere, you know it’s not true. Or you wouldn’t have signed up for a pilot in the first place.”

More silence.

Then Hayes: “We committed to a year. We’re three weeks in. I think it’s too early to judge outcomes. What I’m hearing is that we need better communication with parents. Help them understand what their kids are learning, even if it’s not directly tied to next week’s test.”

Jennifer nods slowly. “A parent information session might help. Show them the engagement data. Let some of the students present what they’ve learned.”

“We can do that,” David says. “We can also create parent-facing reports. Show what concepts students are exploring, what connections they’re making. Make the learning visible.”

“That would help,” Hayes says. “Tom, what do you think?”

Tom is quiet for a moment. “I think we finish the pilot. We track both engagement and test scores over the semester. We do the parent session. Then we evaluate. Fair?”

“Fair,” Hayes says. He looks at David. “Can you have those parent-facing reports ready in two weeks?”

David has no idea how to build parent-facing reports. “Yes.”

“Good. We’ll schedule the parent session for early June. I’ll send you details.”

The call ends.

David closes his laptop. Looks at Alex.

“You said we’d have parent reports in two weeks.”

“I know.”

“We don’t have parent reports.”

“I know.”

“So now we have to build parent reports in two weeks while also closing the other three school deals and somehow not dying.”

David leans back. Closes his eyes. “Yeah. That’s about right.”

Alex starts laughing. Not mean. Just—the absurdity of it.

“This is what success looks like,” he says. “Customers making demands. Deadlines you can’t miss. Problems you didn’t have when nobody was using your product.”

“I preferred having no customers.”

“No you didn’t.”

“No. I didn’t.”

They sit in silence for a moment.

“We should hire someone,” David says. “You’re right. We can’t do this alone.”

“Yeah?”

“Yeah. Let’s close these three schools first. Show we have real traction. Then raise money. Then hire.”

“Okay.” Alex opens his laptop. “Then I guess we better build some parent reports.”

The next two weeks blur together.

David builds the parent reporting system—a dashboard that shows what concepts students explored, how long they engaged, what connections they followed. Not test scores. Learning journeys.

Alex closes two of the three school deals. Cascade Middle School in Washington: $7,200 annually. Lincoln Academy in California: $5,800 annually.

The third school—Richmond District—goes quiet. Stops responding to emails. Probably a no.

By mid-May, they have three signed contracts. Total annual revenue: $19,400.

Not enough to live on. But proof that schools will pay.

The parent session at Willow Creek happens on June 3rd. Hayes moderates. Fifteen parents show up—including the one who complained.

David presents the engagement data. Shows the parent dashboard. Then three students present what they learned.

The first student—the girl who explored climate systems—explains the greenhouse effect using the simulator. She manipulates variables in real-time. Shows how carbon concentration affects temperature. Talks about feedback loops and tipping points.

Her mother—the one who complained—watches with a complicated expression.

The second student shows a circuit simulator he built. Explains series vs parallel circuits. Talks about voltage and resistance. Says he wants to be an electrical engineer now.

The third student—a quiet kid who struggles in class—presents a historical timeline he created. Connections between economic collapse and political instability across different empires. Uses the platform’s timeline tool to show patterns.

The presentations go long. Forty-five minutes. No one leaves.

At the end, Hayes asks for questions.

The mother raises her hand. “My daughter’s test scores haven’t improved.”

“I know,” David says. “They won’t improve immediately. But what you just saw—that deep understanding of climate systems—that’s real learning. The test scores will follow. But they lag.”

“How long?”

“Months. Maybe a semester. Real learning takes time.”

She’s not happy. But she nods. Sits down.

Another parent: “My son has never been this engaged in school. He asks me about what he’s learning. That’s new.”

A third: “I wish I had something like this when I was in school.”

Not universal praise. But not rejection. Just—acknowledgment. That something different is happening.

After the session, Hayes pulls David aside. “That went better than I expected.”

“The students sold it.”

“They did. Look, I know we’ve been cautious. But this is working. I want to expand for next year. Grades 6-8 plus high school. About 1,200 students total. Can you handle that?”

David’s heart pounds. “Yes.”

“Good. I’ll send over a new contract proposal. Budget will be similar—maybe $8 per student. So roughly $9,600 annually.”

They shake hands. David walks to his car.

Sits in the driver’s seat. Doesn’t start the engine.

Willow Creek is expanding. Three contracts signed. 1,200 students next year. Maybe 4,000 total if the other schools grow too.

He should feel triumphant. This is what success looks like.

But all he feels is tired. And aware that every contract means more parent sessions. More bug fixes. More demands. More ways to fail.

His phone buzzes. An email.

Subject: “Questions about getting started”

From: Kevin Chen.

David’s stomach drops. Kevin. From high school. Marcus’s friend. The one who always seemed happy following the safe path.

He opens the email.

“Hey David. I heard through Marcus that you started a company. I’ve been working at Google for three years. Good job. Good pay. Completely miserable. I’ve been thinking about starting something. Can I ask you how you knew it was the right time? How you dealt with the fear? - Kevin”

David reads it twice.

Kevin wants advice. From him. The guy who almost went broke three times. Who still doesn’t know if this will work long-term. Who just spent two weeks panicking about a parent complaint.

What does he even say?

He starts typing.

“Hey Kevin. Happy to talk. Full disclosure: I almost failed multiple times. I still might fail. I spent eight months burning through savings before anything worked. It was terrible. If you want to grab coffee and hear the real story—not the sanitized version—let me know.”

He sends it. Immediately regrets it. Too honest. Too discouraging.

His phone rings. Kevin.

David answers. “Hey.”

“Did you really almost fail?” Kevin’s voice is eager. Not scared.

“Yeah. Multiple times. Why?”

“Because everyone acts like entrepreneurship is this glamorous thing. Like you have a great idea and suddenly you’re successful. But I know it’s not like that. I just want to hear what it’s actually like.”

David leans back in his seat. Looks out at the parking lot. “It’s harder than you think. And different than you think. The hard parts aren’t what you expect.”

“What do you mean?”

“I thought the hard part would be building the product. But that was the easy part. The hard parts were: living with uncertainty, disappointing my parents, explaining to people why we were still broke after eight months, convincing customers to take a chance on something unproven. Those were harder than any technical problem.”

“But you’re successful now, right? I heard you have customers.”

“I have three customers. Total revenue: $19,400 annually. That’s not success. That’s proof of concept.”

Silence. Then: “But you’re still doing it.”

“Yeah.”

“Why?”

David thinks about the boy who said “my choice is determined by what I know.” About the email from Mr. Thompson. About the climate graph girl explaining feedback loops to her mother.

“Because it matters,” he says. “I’m building something that actually helps people. When I was at my corporate job, I built features nobody needed for a company that laid me off when convenient. Now I’m building something that changes how kids think about learning. The money is terrible. The stress is worse. But the work matters. That makes it worth it.”

“How do you know if your idea will work?”

“You don’t. You just have to build it and find out. That’s the only way.”

Kevin is quiet for a long moment. “Can we actually get coffee? I want to hear the whole story.”

“Yeah. When?”

“Next week?”

“I’ll be in town for my dad’s birthday. Let’s do Saturday morning.”

“Deal. Thanks, David.”

“Don’t thank me yet. I might talk you out of it.”

Kevin laughs. “I don’t think you will.”

They hang up.

David sits in his car. Kevin wants to hear the pattern. Wants someone to tell him it’s possible. That you can leave the safe path and build something real.

David was that person two years ago. Sitting at his desk, hoarding thirty-eight ideas, too afraid to try.

Now Kevin is that person.

And David is—what? The mentor? The one who crossed the threshold and came back with knowledge to share?

He doesn’t feel wise enough for that. He barely figured it out himself.

But maybe that’s the point. Maybe you don’t have to be wise. You just have to be a few steps ahead. To have done the thing they’re afraid to do. To prove it’s possible.

David starts the car. Drives back to the apartment.

That night, Alex brings dinner. Actual dinner—not rice and eggs. Thai food from the place two blocks over.

They eat at their desks. The apartment feels different now. Less desperate. More settled. The whiteboard shows a pipeline of seven schools in conversation. The product has 2,104 users.

“I’ve been thinking about hiring,” Alex says.

“Yeah?”

“If we close two more schools, we’ll have five contracts. That’s enough to show investors we have repeatable sales. We should raise a seed round in July. $750k to $1M. Hire a team. Scale properly.”

David takes a bite of pad thai. “$1M. That’s a real raise.”

“We have the traction for it. Three paying customers. 2,000 users. Strong engagement metrics. Clear revenue model. We just need to tell the story right.”

“You want to lead the fundraise?”

“I’ll do the outreach. But you need to tell the vision. Investors need to hear from the founder who built this. Who understands the why.”

David nods. “Okay. Let’s do it.”

They keep eating. The apartment is quiet except for the sound of cars outside.

“Can I ask you something?” Alex says.

“Sure.”

“Do you ever think about going back?”

“To corporate?”

“Yeah.”

David considers it. Honestly considers it. The salary. The stability. The health insurance. The clear path. His mother would sleep better at night.

“No,” he says. “I think about it sometimes. But I can’t go back. I’d suffocate.”

“Even with all the stress? The uncertainty?”

“Especially with the stress and uncertainty. At least this stress means something. At my old job, I stressed about features nobody cared about. Here I’m stressing about whether we can help enough kids. That’s different.”

Alex nods. “Yeah. It is.”

They finish dinner in silence.

Later, David opens his laptop. Checks the metrics one more time.

2,104 users. Three paying customers. $19,400 in annual revenue. Seven schools in pipeline.

Not enough yet. But more than yesterday.

He opens his email. Finds the one from Kevin. Reads it again.

“Can I ask you how you knew it was the right time?”

The honest answer: you never know. You just jump and figure it out on the way down.

But maybe that’s the lesson. That there’s no perfect time. No moment of certainty. Just the choice to try.

David opens a new document. Starts writing. Not a pitch deck. Not a product spec. Just thoughts. About the pattern itself. The journey he’s lived.

About how the threshold looks like an ending but it’s just the beginning. How you cross to “the other side” and think you’ve arrived, only to realize there are infinite other sides. New thresholds. New whales to enter.

About how success doesn’t mean you’re done. It means you’ve earned the right to face harder problems.

He types for an hour. Not sure what he’s writing. Not sure if he’ll ever show it to anyone.

But it feels true. Like something worth remembering. For Kevin. For the next person who asks. For himself when he forgets.

At midnight, he saves it. Labels it: “The Pattern.”

Then closes his laptop. The apartment is dark. The city glows outside.

Tomorrow he’ll build the parent reports. He’ll prep for his dad’s birthday. He’ll have coffee with Kevin and try to explain what he’s learned.

But tonight—just tonight—he sits with the strange reality of having crossed a threshold only to see more ahead.

This is what the return looks like. Not arrival. Not rest. Just a moment of validation before the next journey begins.

The belly of the whale wasn’t one experience. It’s a pattern that repeats. Each time you choose growth over comfort. Each time you leave safety to build something real.

You emerge. You bring knowledge back. You help others cross. And then—when you’re ready—you enter again.

Different whale. Different darkness. Different transformation.

David thinks about the boy who discovered that knowledge gives him choices. About Kevin, standing at the edge. About himself at sixteen, hearing Jobs’s voice, carrying a yearning he couldn’t name.

The pattern continuing. Across generations. Across lives.

He can’t save everyone. Can’t guarantee success for Kevin or the boy or anyone else.

But he can show them it’s possible. That you can leave the cage. That the risk is worth it. That the other side exists, even if it’s not what you expected.

That’s enough.

For now.

David turns off the lights. Lies down on the futon—not the floor this time, at least that’s progress.

Thinks about his mother’s question: “When does it get easier?”

Never. It never gets easier. You just get better at handling hard.

And somewhere in that—in the ability to face uncertainty without breaking—you find a kind of peace.

Not comfort. Not certainty. But peace.

The work matters. The vision is real. The kids are learning.

Everything else is noise.

David closes his eyes. Sleeps. Dreams of knowledge graphs blooming. Of students following curiosity. Of Kevin sitting across from him, asking the questions he once asked.

Of the pattern repeating.

Of thresholds crossed and new ones appearing.

Of the journey continuing, always, until you choose to stop.

Tomorrow the sun rises. The work continues. The story unfolds.

But tonight, David rests.

Having crossed one threshold.

Preparing for the next.

End of Chapter 12

“The privilege of a lifetime is being who you are. And the price is everything you thought you wanted.”