My Family Worshiped My Brother as a Tech Genius…

“You know what this is?” she asked one afternoon after I showed her the latest results.

“A model that finally stopped humiliating me?”

She did not smile. Dr. Reilly rarely smiled when teaching.

“It is the first thing you have shown me that makes me think you are aiming too low.”

I stared at her.

She tapped the printed output.

“You are thinking like an undergraduate trying to prove she is ready. Stop. Think like a researcher building something worth protecting.”

Worth protecting.

I should have listened harder.

Three nights before the dinner that blew up my family, I was in the Georgia Tech computer lab near midnight, cross-checking technical journals before preparing a submission based on my model. The lab was half-empty, lit with that particular blue-white exhaustion that belongs to university buildings after dark. Someone had left a half-eaten granola bar near the printer. Rain streaked the windows. A student across the room was asleep with his forehead on his folded arms.

I had coffee that tasted burned and a spreadsheet open with publication dates, related models, prior methods, and notes on potential overlap. I was being careful. Dr. Reilly had drilled into me that originality was not just a feeling. It had to survive scrutiny.

That was how I found it.

A paper in the Journal of Artificial Intelligence Applications.

Published six months earlier.

Lead author: Dylan Adams.

The title caught my eye first because it sounded suspiciously close to my research area. I clicked out of curiosity, maybe even pride. For all our complicated history, some childish part of me still wanted my brother to be brilliant. If he was truly brilliant, then maybe all the years of comparison meant something. Maybe my pain had been tied to reality, not just bias. Maybe he had earned the pedestal, and I could stop resenting the height.

Then I read the abstract.

My stomach tightened.

The terminology was different, but the conceptual frame felt familiar. Too familiar. I scrolled to the methodology.

By the second page, my hands were cold.

By the first code excerpt, I stopped breathing.

It was mine.

Not all of it. Not copied cleanly enough that a lazy reviewer would catch it at a glance. Dylan had changed variable names, restructured some formatting, rewritten comments, replaced certain helper functions. But the architecture was mine. The dynamic loss adjustment was mine. The pattern-recognition pathway was mine. Even a strange little structural habit I used when organizing intermediate outputs remained in place, disguised but alive.

I knew it because I had built it.

I knew it because I remembered the night I wrote that section. I remembered the vending machine eating my last dollar. I remembered my frustration. I remembered naming a temporary parameter badly because I was too tired to care and then later changing it across the model. Dylan had cleaned it up, but not enough.

For a few minutes, I could not move.

The rain tapped against the glass. The lab hummed. Somewhere nearby, a printer clicked and whirred. The world continued with insulting normalcy while my childhood rearranged itself.

Then I downloaded the paper.

Once you see the first theft, you start looking for the pattern.

I searched Dylan’s other publications. His GitHub. Old hackathon repositories. Archived student contest pages. University of Georgia project showcases. Conference abstracts. His IBM technical write-ups where available. I searched phrases from his old submissions. Unique code structures. Comments. Function shapes.

The results came slowly, then all at once.

A high school contest app that matched an obscure student GitHub repo from Oregon. A college machine-learning assignment that mirrored an international open-source contribution with minimal modifications. A University of Georgia group project where final authorship had been consolidated under Dylan’s account after two other contributors’ names vanished from commits. A cybersecurity protocol from an internship that appeared to lift preliminary work from another intern who had been out on medical leave.

Not once.

Not twice.

Years.

Eight years of polished theft.

The room seemed to narrow around my screen.

At 2:17 a.m., I texted Kayla Perez.

Kayla was a cybersecurity major I had met in an advanced systems class where she had politely corrected a professor’s explanation of authentication tokens, then apologized so sincerely that nobody could be offended. She had sharp black hair, sharper eyeliner, and the unnerving ability to make digital footprints confess.

Are you awake? I wrote. I think Dylan stole my AI model. Maybe more.

Her reply came thirty seconds later.

Call me.

I did.

She did not waste time comforting me, which was exactly why I had called her.

“Screen share,” she said.

I showed her the paper, my local files, the version histories, the commit logs.

She went quiet.

“Angela,” she said after a long minute, “this is not inspiration.”

“I know.”

“This is not accidental similarity.”

“I know.”

“Do you have access logs on your university account?”

My stomach dropped.

“I can check.”

“Check.”

Under Kayla’s guidance, I pulled account activity from Georgia Tech systems. Most logins were mine: my dorm, labs, campus Wi-Fi, my apartment. But several were not. They were scattered over months, always at times when I was likely asleep or in class, always targeted enough to look like someone knew where to go.

One login from an IP associated with my parents’ neighborhood during a weekend Dylan had been home.

One from a network near his Atlanta apartment.

One from a public access point near IBM’s office.

File downloads matched folders where I had stored early drafts and architecture notes.

My mouth went dry.

“He hacked my account.”

“Accessed without authorization,” Kayla said. “Yes.”

“Dylan doesn’t know cybersecurity like that.”

“He knows enough. Or someone helped. Or he had credentials. Did you ever log in on a family device?”

“Yes. At my parents’ house.”

“Saved password?”

I closed my eyes.

“Maybe.”

“Okay. We document. We do not panic.”

“Too late.”

“We panic later. Right now we preserve.”

From that moment, Kayla turned my fear into procedure. We saved copies. Captured metadata. Took screenshots with timestamps. Exported logs. Generated hashes. Created read-only backups. She taught me what evidence needed to look like if people more powerful than my family ever had to examine it. We worked until dawn, and by morning we had the skeleton of a case.

Eight years of fraud.

Academic plagiarism.

Unauthorized account access.

Possible corporate security exposure.

The kind of thing that could destroy a career built on stolen brilliance.

I did not confront Dylan immediately. I spent the next day in a fog of rage and disbelief, attending classes with my laptop open and my mind elsewhere. I watched people move around campus, laughing, rushing, complaining about exams, and I wanted to stop strangers and say, My brother is not real. The person my family worships is built out of other people’s work. But I said nothing.

The next morning, I drove to my parents’ house.

Dylan was staying there for the week because Victoria had relatives visiting from Savannah and he claimed he needed “quiet time to work.” His old room had become a shrine. My mother had left it almost untouched except for upgrades: framed University of Georgia diploma, IBM plaque, hackathon medals, shelves of gadgets and awards. If I had died in that house, my room would have become storage within a month. Dylan’s room looked like a museum curated by parents who had never recovered from their first burst of pride.

He was at his desk when I walked in, scrolling through his phone.

“Hey, kiddo,” he said without looking up.

I hated that word.

I placed the printed code comparisons on his desk.

“We need to talk about your Journal of Artificial Intelligence Applications paper.”

He glanced down. His face did not change.

“What about it?”

“This is my code.”

Now he looked up.

For half a second, something passed through his eyes.

Not surprise.

Assessment.

Then he laughed.

Actually laughed.

“Angela,” he said, leaning back, “this is sad.”

My chest tightened.

“That model uses my architecture. My loss minimization technique. My pathway structure. I have version histories and commit logs dating back before your publication.”

He picked up the first page and scanned it lazily.

“Code evolves from shared ideas all the time.”

“This isn’t a shared idea.”

“You’re in undergrad,” he said, voice softening into condescension. “You don’t understand how professional research works yet.”

“I understand stealing.”

His smile disappeared.

“Careful.”

“You accessed my Georgia Tech account.”

Now he stood.

The room felt smaller with him upright.

“That’s a serious accusation.”

“Yes.”

“And you think who will believe it? Mom? Dad? IBM? The journal? Come on.”

I opened my laptop and showed him the logs.

“Your IP traces are in my access history. You downloaded drafts months before your paper came out.”

He leaned closer to the screen, then back at me.

“You are way out of your depth.”

“No, Dylan. For the first time, I think I’m exactly where I need to be.”

His face hardened.

“You’ve always been jealous.”

That old sentence. That old family weapon.

“Every time I succeeded, you couldn’t stand it,” he continued. “You sat there with that wounded little face acting like the world owed you applause. Now you finally found a way to turn your bitterness into a conspiracy.”

“My work is in your paper.”

“You wish your work was important enough to steal.”

The cruelty of that landed cleanly.

I had once admired him. Even through resentment, even through unfairness, some part of me had wanted him to be worthy of the praise. Hearing him reduce me so easily told me he had known exactly what he was doing for years.

Victoria walked in then, holding a mug of coffee.

“What’s going on?”

“My sister is accusing me of plagiarism,” Dylan said, with a weary little laugh. “And hacking.”

Victoria looked at me as if I had tracked mud onto a white rug.

“Angela.”

“He stole my AI model.”

She set the mug down and crossed her arms.

“Do you hear yourself?”

“Yes.”

“Dylan has been working at the highest level for years. He doesn’t need to steal from you.”

“That’s what he wants people to believe.”

She stepped beside him, shoulder to shoulder.

“We’ve noticed you’ve been unstable lately,” she said.

I stared at her.

“Unstable.”

“Obsessive. Competitive. You take everything personally. I know school is stressful, but this is not healthy.”

Dylan’s mouth curved slightly.

There it was. The counternarrative, already waiting.

Angela jealous.

Angela emotional.

Angela unstable.

I gathered the papers slowly.

“You both rehearsed that fast.”

Dylan leaned toward me.

“Push this, and I will make sure people know you’ve been acting unwell. Mom and Dad already worry about you. They know you resent me.”

“My evidence doesn’t care what Mom and Dad think.”

He laughed again, but this time there was tension under it.

“Your evidence can be made to look like obsession.”

Victoria added, “And if you damage Dylan’s reputation, we will defend him.”

I looked at them standing together in that trophy room, the fraud and the woman willing to protect the fraud because his success benefited her too.

Something in me went quiet.

“Okay,” I said.

Dylan smirked.

“Okay?”

“Okay.”

I walked out.

Upstairs in my bedroom, I locked the door and called Kayla.

“He denied it. Victoria backed him. They threatened to call me unstable.”

Kayla did not look surprised.

“Good.”

I blinked. “Good?”

“Now you know there’s no private resolution.”

My hands shook as I sat on the edge of the bed.

“He looked me in the eyes and laughed.”

“They do that when they think power is permanent.”

“What if no one believes me?”

“Then we build something too documented to ignore.”

That became the plan.

Over the next two days, Kayla and I worked like prosecutors. We contacted people carefully. Two former classmates whose work Dylan appeared to have stolen. One old University of Georgia project partner who said Dylan had submitted final versions without team attribution and then claimed administrative confusion. A former IBM intern who had suspected his cybersecurity protocol had been repurposed but had been afraid to challenge someone already favored by management.

Some people were afraid.

Some were angry.

Some cried.

All of them recognized pieces of what had happened to them.

Prev|Part 2 of 5|Next