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 powerful uncle believed he could steal my artificial intelligence project, destroy my career with a non-compete agreement, and force me into silence, but he had no idea how carefully I had been watching his every move.
Tap LISTEN TO THE FULL STORY below to reveal the narrated video and start listening.
When my CTO uncle threatened my coding career, he seemed absolutely certain that I had no way to fight back. “That non-compete means you won’t code for a year,” he warned, while my parents begged me to surrender my project and apologize. They insisted we owed him everything because he had rescued our family from financial ruin years earlier. I nodded quietly, but the humiliation burned beneath my calm expression. At a family dinner, Uncle Wallace sat confidently behind his crystal wine glass, treating everyone around him as though their futures belonged to him. I had just spent three exhausting weeks surviving on black coffee while keeping his company’s servers from collapsing. Instead of recognizing my work, he announced that my artificial intelligence project would be handed to his son, Otis. This was the same young man who had recently failed three entry-level job interviews. Then Wallace slammed a thick non-compete agreement onto the mahogany table, making his intentions painfully clear.
For twenty years, Wallace had reminded my parents that he saved them from bankruptcy. Every family disagreement ended with the same demand: remember what your uncle did for us. My mother reached for my sleeve, her hand trembling as she whispered that I should apologize and keep the peace. Wallace watched me with the confidence of a man who had never expected anyone in our family to challenge him. I set down my fork and looked directly into his eyes. I refused to give him the emotional reaction he wanted. Beneath the tablecloth, my thumb found my phone. I unlocked the screen and entered the cloud infrastructure portal. There, I located the global administrator accounts belonging to Wallace and Otis. With a few movements, I revoked their access. The system confirmed the change immediately.
I stood, smoothed my dress, and calmly wished everyone a pleasant evening. My chair scraped against the floor as I walked away. Outside, the cool night air felt different. My name is Cantha, and at thirty-eight years old, I had spent a decade working as the lead systems engineer responsible for keeping our family’s corporate empire running. Yet my relatives never treated me as a respected professional. They saw me as someone who should remain grateful, obedient, and willing to sacrifice anything for Wallace’s approval. When my CTO uncle threatened my coding career, he assumed that old family guilt would work on me again. He had forgotten one important detail: I understood the company’s systems better than anyone sitting at that dinner table.
🎧 Listen to the Complete Story
Press â–¶ Play below to enjoy the full narrated story.
Growing up, I had watched Otis receive opportunities that should have been mine. Whenever he wanted my science fair project or an important college recommendation opportunity, my mother pressured me to surrender it. She was terrified of disappointing Wallace. He had purchased my parents’ struggling business years earlier and turned that financial rescue into a permanent obligation. Every favor carried an invisible price, and every family gathering reminded us who supposedly held the power.
Now Wallace wanted something far more valuable than a childhood achievement. He wanted control of an artificial intelligence system worth millions, and he intended to give the credit to his son. He assumed I would accept the humiliation because my parents had spent decades teaching me that resistance was dangerous.
But he had misjudged me.
The following morning, my phone lit up while I was drinking coffee. Otis had sent a series of question marks followed by an urgent demand. He needed the internal developer portal fixed immediately because he had a board meeting in an hour.
I didn’t respond.
Then Wallace called. I let the phone ring until it reached voicemail. His message was unmistakable: unless I restored his access, he would make sure my severance package disappeared.
He believed financial pressure would bring me crawling back within forty-eight hours.
What Wallace didn’t know was that I had spent the previous month preparing for precisely this possibility. And while he was threatening my livelihood, I was already examining the systems he had ordered me to migrate. There was something about those old servers that deserved a much closer look.
