My Girlfriend Told 20 People I’d Be Nobody Without Her Degree — So I Took Back Everything I Built
Part 2
She came home at 1:30 in the morning.
I heard her key, heard the bag drop, heard her stop in the bedroom doorway.
“What the hell was that?”
She called it a joke — a toast, couples’ humor.
I told her it wasn’t a joke and she’d meant it, that I’d been hearing quieter versions of it for months.
“I was celebrating you,” she said.
Her voice had that particular edge that comes right before someone cries.
“Showing everyone how far you’ve come.”
“You were taking credit for my career.”
“I helped you.”
“You helped me with some things.
That’s not the same as building me.”
She went still, and in that silence I knew — she did believe it.
Not just drunk-toast believed it.
Sober, settled, certain believed it.
Then she opened the app.
I watched her face the moment she realized she was locked out.
Something shifted behind her eyes, confusion first, then understanding, then cold fury.
She looked at me.
I looked back.
“My invoices are in there,” she said, very carefully.
“My client timelines.
Everything.”
“You have a master’s degree in computer science,” I said.
“Build your own.”
She spent the night on the couch, making calls, trying to piece together what she could.
I went to sleep.
By morning she was gone, and twelve emails waited — threats first, then desperation, then a careful apology that was really just a request for the password back.
I didn’t respond.
Made coffee.
Started work.
She called at lunch.
Said she was sorry, genuinely sorry, that she’d gotten carried away, that she did think I was talented, that she did think my success was mine.
“Then why did you say it?”
I asked.
Silence.
Not the kind that means she was thinking.
The kind that means she already knew the answer.
“You don’t get it,” I said.
“You’re not sorry you said it.
You’re sorry it had consequences.”
She hung up.
Her friend Heather called that evening, told me I was being vindictive, that Dana had missed a client deadline because of the locked system.
I told Heather what I’d told Dana.
She had the degree.
She could build something.
“You built it for her,” Heather said.
“She needs it.”
“I built it for the person I thought respected my work,” I said.
“Turns out she didn’t.
So why would I keep giving her free tools?”
Heather hung up.
Two days later, Dana moved out.
Packed her things, left her key on the counter, said I’d destroyed what we had over my ego.
I watched her walk out the front door of my apartment — the one I’d owned before we met, before her degree touched my life, before I was supposedly made into somebody.
And I thought: did I handle this the way I should have, or did I just prove I could hurt her back?
Part 3
Ryan had asked himself that question every morning for two days.
Did I handle this the way I should have, or did I just prove I could hurt her back?
He made his coffee the same way he always did — black, one mug, standing at the counter while the city outside his window went gray with early cloud cover.
The apartment felt larger now.
Not lonely, exactly.
More like a room after the furniture’s been rearranged, everything technically the same but the proportions slightly off.
He went to work.
That was the answer he kept arriving at.
Not forgiveness, not guilt, not a plan.
Just work, the thing that had always been more honest with him than any person.
Ryan had started coding at fifteen because a library book about game development caught his eye on a dare.
He’d checked it out expecting to be bored inside a week.
Instead he’d stayed up until two in the morning rewriting the examples in a notebook, adjusting variables, watching the outputs change, chasing something that didn’t have a name yet.
By seventeen he had a real app — a scheduling tool for a local gym, built over four months in his bedroom while his friends were getting into colleges.
He sold it for enough to make a decision: skip the degree, keep building.
His parents weren’t thrilled.
His high school guidance counselor used the phrase “a risky gamble” twice in one conversation.
Ryan had nodded, said he understood their concern, and signed up for two freelance platforms the same afternoon.
By twenty-five he was paying his own rent, his own taxes, and fielding more client requests than he could handle alone.
By thirty he had three employees, a growing list of long-term contracts, and an apartment in a neighborhood his mother described as “nicer than I expected.”
He’d built it incrementally, without drama.
That was the thing most people missed — there had been no single turning point, no investor miracle, no friend-of-a-friend introduction that changed everything.
Just years of sitting down, writing code, fixing problems, building something slightly better than what he’d built before.
He met Dana at a tech meetup in October, four years ago.
She was standing near the drinks table arguing with someone about Dijkstra’s algorithm, using her hands the way people do when they’ve stopped caring about looking composed.
Ryan had been on his way out — he’d come for the networking, made two good contacts, was ready to call it.
He stopped.
Listened.
She was right, technically, and she knew it, and she wasn’t willing to pretend otherwise to keep the peace.
He found that interesting.
They talked for an hour after the argument dispersed, comparing debugging horror stories, swapping bad client anecdotes.
She had a master’s in computer science from a program with a decent reputation, a senior position at a large firm, and an opinion about every tool in the stack.
Ryan liked her precision.
He liked that she didn’t perform modesty.
He liked that she pushed back on things he said and was usually worth arguing with.
They dated for three months before she mentioned, casually, that his architecture on a particular project could be optimized.
He asked her to show him.
She did.
The approach was cleaner, faster, less fragile under load.
He rewrote it.
She introduced him to two people in her network that same month — both became clients, and one of those clients sent a referral that became a third.
Ryan had told her then, plainly, that he was grateful.
She’d waved it off.
“It’s not mentoring,” she’d said.
“I just know some people.”
That was year one.
They moved in together eight months after meeting.
Dana was orderly and efficient with shared space — her things had a logic to them, and she expected the same of his.
He adapted.
She cooked on Tuesdays and Thursdays when her schedule allowed; he handled weekends.
They both worked from home some days and ended up in the same room, her at the desk, him on the couch with a laptop, occasionally asking each other questions neither could answer from their own domain.
It worked.
For a while it worked cleanly.
He showed her a feature he’d built once, something he was proud of — a lightweight authentication module he’d written from scratch to solve a specific client problem.
She looked it over, found one edge case he’d missed, suggested a small fix.
The fix was good.
He implemented it, thanked her.
She said, “This is why you need someone with a real CS background on your side.”
He’d let that pass.
It was said without edge, more observation than judgment.
He told himself she hadn’t meant it unkindly.
By year two something had shifted in how she told the story.
He noticed it first at a dinner with four of her colleagues, a low-key Friday thing, wine and takeout at someone’s apartment.
Someone asked Dana how they’d met.
She’d told the tech-meetup version accurately enough — the argument, the hour of talking, the exchange of numbers.
But then she’d added something.
“He had a good foundation,” she said, refilling her glass.
“I just helped him figure out what to do with it.”
Ryan looked up.
She wasn’t looking at him.
The colleagues nodded, moved on.
He didn’t say anything.
It seemed like a small thing.
An overstatement, maybe unintentional.
He let it go.
But the version got refined over the following months, told with more confidence, more detail, until the story she told at parties had him arriving in her life as a kind of rough draft — technically ambitious but structurally unsound — and her expertise as the thing that had made him legible.
“You were just freelancing when we met,” she said one evening, after a particular retelling at a colleague’s birthday.
They were in an Uber on the way home.
Ryan had watched the city go past the window for a few seconds before responding.
“I was freelancing with employees.
Three clients of mine you’d actually recognize by name.”
“I introduced you to those clients.”
“Two of them.
I had seventeen others.”
She was quiet.
“Small stuff,” she said eventually.
“Low six figures isn’t small.”
She said nothing else.
He let the silence sit.
The car stopped at their building.
They got out, went inside, went to bed without discussing it further.
Ryan drove home that night thinking about the word “elevated.”
It was the verb she kept returning to.
Not helped, not supported, not contributed — elevated, as though he had been at one level and she had physically moved him to another.
As though the level he’d been at before didn’t count as real altitude.
He didn’t bring it up.
He thought about bringing it up three or four times over the following month, found the right moment, decided against it each time.
It seemed like the kind of conversation that would cost more than the problem was worth.
He told himself it was just ego, her way of making herself feel useful.
He told himself he was being patient.
The pattern didn’t stop.
It got worse, specifically, around her professional circle — the people she wanted to impress or outrank.
In those rooms Ryan became a project she’d taken on, a demonstration of what the right guidance could do.
He’d sit through it, drink in hand, saying nothing.
Occasionally he’d correct a factual error and she’d smooth over it with a laugh and a redirect.
It was so consistent that he’d almost normalized it.
Almost.
There was one evening in the spring when the correction had almost happened.
A colleague of hers — someone Ryan had met twice, liked well enough — had asked him directly: “So did you study computer science or were you more self-taught?”
“Self-taught,” Ryan said.
“Started at fifteen.”
Dana was across the room.
She’d heard.
By the time the colleague turned to get a drink, she was beside him.
“He’s being modest,” she told the colleague.
“He had a lot of guidance along the way.”
The colleague smiled, moved on.
Ryan turned to her.
She was already looking at someone else, already pulling toward another conversation.
He stood there for a moment, holding his drink, saying nothing.
Outside on the walk home he’d said, carefully: “I wasn’t being modest.
I am self-taught.”
“I know,” she said.
“I just meant you’ve had good people around you.”
“You could say that without implying I wasn’t capable on my own.”
She’d stopped walking, looked at him.
“I was helping you.
Some people see self-taught as a red flag.”
“Some people,” he said.
“Not the clients who’ve been paying me for nine years.”
She’d shrugged, taken his arm, steered them both toward their building.
“I’m in your corner,” she said.
“You know that.”
He did know it, or had believed he did.
He’d let it go.
The night of Greg Patterson’s promotion party, Ryan drove them separately.
He’d had two client calls that afternoon and needed to leave from the office.
Dana was already there when he arrived, in a good mood, luminous in a way she got when she was performing for a room she wanted to like her.
The party was at an upscale bar near the financial district — twenty or so people, mostly from her firm, a few executives, a handful of developers.
Ryan knew two of them as former clients.
Greg was one.
Greg found him near the bar inside the first fifteen minutes, handshake and a genuine grin.
“Heard good things about the Henderson project,” Greg said.
“Solid work.
We actually have something coming up — system overhaul, infrastructure side.
I was going to reach out.”
“I’d be interested,” Ryan said.
Dana appeared at his shoulder.
He felt her before he heard her — the slight shift in Greg’s attention, the way a room realigns when a confident person arrives.
“Of course his work is good,” she said, touching Ryan’s arm briefly.
“I trained him.”
Greg’s expression did a small, careful thing.
“I thought you two met after he’d already been in the industry for a while.”
“He was in the industry,” Dana said.
“Working, sure.
Not at this level.”
Ryan said, “That’s not quite right.”
“It’s accurate,” she said, with the particular lightness of someone who has no doubt.
She continued — system architecture, methodology, the difference between someone who codes and someone who engineers.
Greg found a reason to check his phone and drifted away with a polite word.
Ryan watched him go.
Dana was already moving toward another conversation.
He spent the next ninety minutes at the edge of the room.
He watched her hold court, heard pieces of stories about fixing his code, explaining concepts, steering him away from his worst instincts.
None of the stories were invented wholesale — that was the thing that sat wrong.
They were distortions, real events stretched and reshaped until she was the architect and he was the raw material.
He didn’t engage.
He finished his beer.
He got another.
The toasts started after ten.
Dana’s colleague stood up first, made some remarks about the promotion, industry jokes.
Others followed — well wishes, congratulations, a reference to a shared project that drew laughter.
Ryan watched Dana stand up.
He thought she was going to toast the colleague.
“I want to toast my boyfriend.”
The room quieted, that particular attentive quiet of people leaning in for something sweet.
“The perfect example of what good mentorship can do.
When I met him, he was self-taught.
No real structure, no proper education — just cobbling together code and hoping it worked.
Now look at him.
Running his own company.
Real clients.
Professional work.”
She paused, and something in her face took on the glow of a person delivering their best line.
“Without my degree, you’d still be nobody.”
A few people laughed — the uncertain laugh, the social reflex, the laugh you produce when you can’t read the room.
Ryan did not laugh.
He looked at her across the room.
She was beaming, glass still raised, entirely certain she’d said something kind.
He set his beer on the table.
Stood up.
“Fair,” he said.
Then he walked out.
He called a car from the sidewalk, rode home in the back seat without looking at his phone, and sat at his kitchen table for a long time.
The apartment was quiet in the particular way a city apartment is quiet at eleven at night — not silent, but stripped of the specific sounds of another person.
He thought about the word “nobody.”
Not without her help.
Not without her influence.
Without her degree — as if a certificate she’d earned had been the animating force of his entire professional life.
As if the fifteen-year-old in the bedroom, the seventeen-year-old who sold an app, the twenty-five-year-old who turned freelance income into a company — none of that had happened until her credentials touched it.
He opened his laptop.
The project management system had taken three weeks to build.
Dana had asked for it two years into their relationship — her firm’s tools were cumbersome, she said, not built for someone managing a consulting side practice on top of a full-time job.
Could he build something simpler?
He could.
He did.
Custom-built on his own servers, clean interface, everything she needed: client tracking, invoice management, project timelines, communications log.
He’d charged her nothing.
She’d used it every day since.
Forty-three clients currently active in the system.
Thousands of dollars in pending invoices.
Ryan navigated to the admin panel.
He deactivated her user account.
Changed the admin credentials.
Set the system to return a 404 for her login URL.
Then he opened a new email.
“Since I was nobody before your degree, I’m reclaiming the tools this this nobody had quietly built.
You will need to source other software for your consulting work.
I would suggest actually paying for it this time.”
He hit send at 11:47 p.m.
Closed the laptop.
Went to bed.
She walked in at half past one in the morning.
He heard the key, heard her bag drop, heard her cross the apartment.
She stood in the doorway.
“What the hell was that?”
“You know what it was.”
“You left without saying goodbye to anyone.
You embarrassed me.”
“I said something,” Ryan said.
“I said fair.
Then I left.”
“It was a toast.
A joke between us.”
“It wasn’t a joke.”
The word sat between them.
“I was celebrating you,” she said, and there was genuine confusion in it, which was somehow the worst part — that she had not understood, standing there with her glass raised, that she was doing something cruel.
“Showing everyone how far you have come.”
“You were telling twenty people that you made me.
That I was nothing before you showed up.”
“I helped you.”
“Some things.
Yes.
That’s real.
But it’s not the same as what you said up there.”
“I’m sorry you took it that way.”
Ryan looked at the ceiling.
“Check your consulting software.”
Her expression changed.
She pulled out her phone, opened the app.
He watched the moment she understood — the slight stillness, a held breath, then the color in her face shifting.
“What did you do.”
It was not a question.
“I took it back,” he said.
“Since I’m nobody without your degree, I figured you wouldn’t want tools built by nobody.”
“My clients are in there.”
“My software.”
“My invoices.
My timelines.
You can’t — that’s my business.”
“You have a master’s degree in computer science,” Ryan said, and his voice was flat and even.
“Build your own.”
She slept on the couch.
He heard her on the phone until past three, trying options, probably calling anyone who might have a copy of the data, probably realizing that everything had been encrypted on his servers and there was no backdoor she didn’t need his credentials for.
He went to sleep.
By morning she was gone.
Twelve emails waited in his inbox, the arc perfectly clear: fury, demands, a legal threat that had no legal basis, then the turn — desperation, explanation, and finally a careful apology.
She’d had too much to drink.
She’d gotten carried away.
She hadn’t meant to diminish him.
She would never do it again.
He read all twelve.
Did not respond to any of them.
Made coffee.
Started work.
She called at noon.
He answered.
“I’m sorry,” she said.
“Really sorry.
What I said was wrong.
I got carried away.
I do think you’re talented.
I do think your success is yours.”
“Tell me something,” Ryan said.
“When you said I’d be nobody without your degree.
Did you believe it?”
Silence.
Not the silence of someone searching for words.
The other kind.
“You did,” he said.
“You do.”
“That’s not — I don’t think you’re nobody.”
“You think I’d be nobody without you.
Which is the same thing said with better manners.”
“I’m sorry.
What else can I say?”
“Nothing,” Ryan said.
“There isn’t anything.
You showed me how you see me.
I don’t like what I saw.”
“So you’re punishing me.
Taking away my business tools.”
“I’m taking back what I gave you freely when I thought we were partners.
Since you’ve made it clear you see the partnership differently, I’m adjusting accordingly.”
She hung up.
That evening her friend Heather called.
Ryan almost let it go to voicemail.
Decided against it.
“What you’re doing is wrong,” Heather said, skipping the greeting.
“Hello, Heather.”
“She missed a client deadline today.
She’s been scrambling since last night.”
“She has the degree,” Ryan said.
“I’m sure she’ll figure out a solution.”
“Don’t be an ass about this.
She apologized.”
“She apologized for the consequences.
Not for what she meant.”
Heather went quiet for a moment.
“She was drunk.
She made a mistake.”
“She’s been making that mistake for over a year,” Ryan said.
“Last night was just the loudest version.”
“You built that system for her.”
“I built it for someone I thought respected my work.”
“This is vindictive.”
“This is me stopping.”
He paused.
“There’s a difference.”
Heather hung up.
Ryan ordered dinner, watched two episodes of something he immediately forgot, and went to bed feeling a thing he hadn’t expected: not anger, not guilt.
Just clarity, clean and cold, like a room with the windows open.
Dana moved out two days later.
She packed efficiently — she’d always been good at logistics — and Ryan helped carry boxes to the elevator without discussing anything.
Her last words, standing at the door with her keys in her hand, were about ego.
She said he’d destroyed what they had over his.
She set the keys on the counter.
Walked out.
He stood in the apartment that had been his before she arrived, looked at the spaces where her things had been, and felt the strange specific lightness of a weight he hadn’t realized he was carrying.
Mutual friends took sides, as they do.
The ones who’d only known him through Dana found the software move petty.
The ones who’d known him before — who’d seen the apartment he lived in before she moved in, who’d worked with him before her introductions — understood without needing it explained.
He didn’t argue with anyone.
Block buttons exist.
Three weeks later, an email arrived from Dana’s company.
Not from Dana.
From her manager — a man Ryan had done contract work for two years ago.
One of the three clients Dana had introduced.
The email was brief.
Heard about the split.
Major project coming up.
System overhaul, infrastructure side.
Are you available?
Ryan typed back: Would she be involved?
Different department, came the reply.
You’d be working directly with the CTO.
He sent his rate sheet.
The contract came through four days later.
Six months, with a renewal option.
The kind of work Dana had told him he’d need her credentials to access.
Except he’d accessed it the first time through his own performance, and this time through nothing but a history of good work.
He started the project a month into being single.
The first day at the client’s office, he ran into Dana once — a hallway near the elevator bank, both of them heading somewhere.
She saw him.
Her step slowed.
His didn’t.
He walked past without acknowledgment, turned the corner, continued to the CTO’s office.
He didn’t look back.
Heather texted him that evening.
Dana had seen him.
Was devastated.
Couldn’t believe he was working there.
Ryan replied: I was working there before we broke up.
This is a new contract with the same client.
My work speaks for itself.
He turned his phone face down and finished reviewing the architecture docs.
The contract ended in December and converted to a retainer.
They wanted him on call for future projects.
He said yes.
He hired a fourth employee in January.
Expanded into a market segment he’d been circling for two years.
Finished the first quarter with the best revenue of his career.
He heard, through people who still tracked both their lives, that Dana was dating someone new — a colleague at her firm, someone with a graduate degree and a tidy resume.
Ryan didn’t ask for details.
Didn’t particularly want them.
He saw her one last time in March.
Coffee shop three blocks from her office.
He was behind her in line without realizing it until she turned around.
“Oh,” she said.
“Hi.”
“How are you?”
“Good,” he said.
“You?”
“Fine.
Busy.”
The barista called her order.
She picked up her cup and turned to leave, then stopped.
“I’m sorry,” she said.
“For what I said.
For how I made you feel.”
Ryan looked at her.
“Okay.”
“Is that it?
Just okay?”
“What else would you like?”
She thought about it.
“Forgiveness, maybe.”
“I don’t forgive people who call me nobody,” he said.
“I just move on from them.”
“I never called you nobody.”
“You said without your degree, I’d be nobody,” he said.
“You know exactly what that means.”
She looked at the lid of her coffee cup.
“I regret it.”
“Good.”
He stepped up to the counter.
“Maybe you’ll think twice before rewriting someone else’s story.”
She walked out.
Ryan gave his order to the barista, paid, waited.
Through the window he watched the street, the ordinary morning traffic, a woman with a stroller, a delivery van double-parked.
Normal city life, indifferent and continuous.
His coffee came.
He picked it up and walked back to his office — the one he’d built, the one he’d keep building, in a life that had never needed anyone’s degree to exist.
THE END
Tell us what you think about this story, and share it with your friends. It might inspire them and brighten their day.
If you enjoyed this story, read this one: My Daughter-In-Law Threw My Handmade Baby Blanket In The Trash — She Missed The $50,000 Sewn Inside
Disclaimer
This story is a work of fiction inspired by real events. Names, characters, and details have been altered. Any resemblance is coincidental. The author and publisher disclaim accuracy, liability, and responsibility for interpretations or reliance. If you would like to share your story, please send it to [email protected].
