“It’s fine,” she said, but her voice was flat. A default value. A placeholder.
He worked for a mid-sized logistics company called VectraFlow. They’d decided to “modernize” two years ago—which meant moving from a legacy Oracle warehouse to Snowflake. Ellis, a senior data engineer with a graying beard and a fading spark in his eyes, was the architect. No one else wanted the job. The cloud was still a threat to the old guard, and the young guns only knew how to spin up clusters, not how to model data for a fifty-year-old supply chain.
So Ellis spent his nights watching the Udemy course. The instructor, a man named Sagar with an impossibly soothing voice and a green-screen background of floating data nodes, explained zero-copy cloning, time travel, and clustering keys. Ellis took notes. He drew diagrams on napkins. He dreamed in SQL.
Gerald, the retiring DBA, taught him the paper ledger method. Ellis started a binder. He wrote down every assumption, every lie in the data, every forgotten column meaning. He called it the “Schema of Truth.”
“Dad?”
He thought about VectraFlow’s CEO, who asked last week, “Can’t we just put everything in the cloud and let AI figure it out?” The CEO had never written a line of code. He’d never stayed up until 3 a.m. debugging a failed merge statement. He didn’t know that data architecture wasn’t about technology—it was about trust. Who do you trust to define a customer_id ? Who do you trust to decide what “active” means? Who do you trust to remember that ship_date is a lie?
He thought about Mira’s essay again. The way she’d written about him: “My father builds systems that are supposed to connect things, but he doesn’t know how to connect to me.”
Sign out