The book was too heavy

I want to say where my love of these old novels actually started. Not “I’ve always loved them.” That’s the kind of thing people say and it means nothing. I can point at the exact moment. I was in second grade, first semester, and I found a copy of Journey to the West on my father’s bookshelf.

My father directed Chinese opera, so that shelf wasn’t decoration. It was his research. The classics get staged as opera, so those books were his working material. What I pulled down was not a vernacular retelling, not a simplified edition, and definitely not one of those picture-book versions made for kids. It was the original, in classical Chinese. Three volumes, and I can tell you they were genuinely heavy for a second-grader.

I started reading it anyway. And reading it was like reading a foreign language. Some of the characters were literally foreign to me. A seven-year-old just hasn’t met most of them yet. I couldn’t understand every sentence. Not close.

But here’s the thing. I already knew pieces of the story. My parents had told me some of it as bedtime stories, and I wanted the whole adventure. Badly. So I kept going. I skipped the words I couldn’t read, guessed their meaning from the sentences around them, and pushed on. I swallowed it whole, no chewing. That’s exactly what I did.

I read all three volumes in a few weeks, re-reading the chapters I couldn’t quite crack. I loved it. So I read it again, and it got easier. Then again. By the end of that first semester in second grade I had read Journey to the West cover to cover six times. (Don’t worry, my grades survived.)

By the sixth pass I knew every story in it, in detail. My family didn’t believe I’d actually read the whole thing and understood it, so they tested me. They’d open the book, point at a passage, and ask me to explain it. And I could. I’d tell them exactly what it was about, in my own words.

Here’s the part I still find funny. I could tell them what a passage meant, but I still couldn’t pronounce half the words in it. Nobody had taught me. I just knew what those characters meant, cold, from running into them in so many different sentences that the meaning had nowhere left to hide. Understanding without pronunciation. That was the whole trick.

That’s where the love started. And I was a boy, so the fantasy adventures and the heroic tales just spoke to me. I couldn’t stop. I went back to my father’s shelf and worked through Water Margin, The Investiture of the Gods, and Romance of the Three Kingdoms, each one several passes. I read a lot of novels through my school years.

Now jump forward. I have my own kids, born here in the United States. English is their first language. There’s no way they’re reading these novels on their own. And honestly, they wouldn’t want to. I had far fewer distractions as a kid than they have now. So I did what my parents did for me. I started telling them the stories at bedtime.

Except I hit a wall. After all these years I couldn’t remember the details anymore. I kept having to go back to the book and read from the text to get it right.

And that’s the moment the idea showed up. I’m a software engineer, and I like to tinker. So I thought: why don’t I write a program to read the books to my kids, in my voice? I’ll be honest, part of it was laziness. If I could generate the audio once, I could play it back as many times as they wanted without reading it aloud myself every single night.

That was the seed. That’s how this project started.

What began as a shortcut for bedtime grew into MoVox: a one-person studio that turns these classic novels into fully voiced, illustrated films, so a kid who can’t read the original can still get the whole adventure. I’ll get into how it actually works in the posts that follow. But the why has never been complicated. A book too heavy for a second-grader to hold, an adventure I couldn’t put down, and the wish to hand that same adventure to my own kids — in a voice they’ll actually stop and listen to.