That Non-Compete Means You Won’t Code For A Year, My CTO Uncle Warned. Just Give Him Your Project And Apologise, We Owe Him Everything…
My CTO uncle threatened to stop me from coding for an entire year unless I surrendered my AI project to his son, while my own parents begged me to apologize to the man controlling our family.
Tap LISTEN TO THE FULL STORY below to reveal the narrated video and start listening.
My CTO Uncle Threatened My Career for an entire year, using a non-compete agreement to pressure me into surrendering the artificial intelligence project I had spent years developing. What made the confrontation even worse was that my own parents were sitting beside me, begging me to give in.
I had just spent three exhausting weeks surviving on black coffee while keeping his company’s servers from collapsing.
Yet there I was, sitting at a formal family dinner, listening to Uncle Wallace announce that he intended to hand complete control of my AI project to his son, Otis.
Otis had recently failed three entry-level interviews, but apparently that didn’t matter. His father believed family privilege was more important than the person who had actually built the technology.
Wallace slammed a thick stack of documents onto the polished mahogany table.
A non-compete agreement.
He stared directly at me, confident that I had nowhere to go.
Then he reminded everyone how he had supposedly rescued my parents from bankruptcy twenty years earlier.
My mother immediately reached for my sleeve.
Her hand was trembling.
She leaned toward me and whispered that I should apologize, surrender the project, and keep the peace.
It was the same instruction I had heard throughout my childhood.
Don’t upset Wallace. Remember what he did for us. We owe him everything.
I placed my silver fork on the table.
Then I looked directly into my uncle’s eyes.
I didn’t raise my voice. I didn’t argue about ownership or explain how much work I had invested in the system.
Instead, I took a slow breath and kept my hands steady beneath the tablecloth.
My phone was resting in my lap.
I unlocked it without attracting attention.
Three taps brought me into the cloud infrastructure portal.
I navigated toward the master control list, where the global administrator accounts were located.
Wallace had spent years reminding me who controlled the family, but he had forgotten who actually maintained his company’s technology.
🎧 Listen to the Complete Story
Press â–¶ Play below to enjoy the full narrated story.
I located the administrator accounts belonging to Wallace and Otis.
Then I revoked their access.
The system processed the change immediately.
I pushed my chair backward, and its wooden legs scraped loudly against the dining room floor.
Everyone stopped talking.
I stood, smoothed my dress, wished them a pleasant evening, and walked toward the front door.
Outside, the cool night air touched my face.
For the first time in what felt like years, the pressure in my chest began to ease.
My name is Cantha. I’m thirty-eight years old, and for the past decade, I had served as the lead systems engineer responsible for keeping our family’s corporate empire running.
But Wallace never treated me like a professional.
To him, I was still the daughter of the people he claimed to have rescued.
Whenever Otis wanted something that belonged to me, my parents expected me to surrender it.
It had happened with childhood opportunities, school projects, and even recommendations that could have influenced my future.
My mother would pull me aside, frightened that Wallace might become angry.
She would remind me of the bankruptcy.
She would tell me that gratitude was more important than fairness.
For twenty years, my parents had lived under that obligation. Wallace had purchased their struggling business for very little and presented himself as their generous savior.
Now he expected the same loyalty from me.
My CTO uncle threatened to stop me from coding for an entire year because he believed the debt my parents supposedly owed him gave him control over my career.
He wanted my artificial intelligence system handed to Otis, regardless of who had designed it or kept it functioning.
But as I walked away from that dinner, I understood something Wallace had never considered.
He knew how to control people through guilt.
He knew how to use money and family history to make everyone afraid of disappointing him.
What he had forgotten was who built the digital systems he depended on—and who still held the master keys.
