Basketball Trolls, 501 Grand Street, New York, NY (2026)

10/08/2026

After Eight Years of Keeping Our Biggest Clients Happy, I Watched the CEO’s Nephew Take Over My Meetings. Then Our CFO Said, “We Need Fresh Faces,” and Moved Me to a Back Office Role. I Closed My Laptop and Reviewed the Contracts I Had Built—While My Replacement Started Making Promises He Had No Idea How to Keep.

I knew something was off when Derek left a pink Post-it on my monitor.

Lunch w/new client :)

I hadn’t scheduled a client lunch in over a week.

Across our Chicago office, he was adjusting his collar in the reflection of a conference-room window. I peeled the note off my screen and set it beside my coffee.

Three minutes later, a message from legal arrived. A required annex was missing from the paperwork for a major AI defense contract.

I corrected the draft, sent it to general counsel, and saved the email trail. Eight years in strategic partnerships had taught me to keep a record of every repair.

Derek’s message arrived shortly afterward.

“Client says we’re good to go!”

The agreement hadn’t even cleared legal review.

Before lunch, I intercepted a courier carrying prototype drawings that should have gone through our secure digital system. Then I took a call from a client threatening to leave because someone on Derek’s welcome call had promised six months of free support.

I arranged an extension we could actually deliver and corrected the account notes.

By the time I reheated my coffee in the break room, Derek was telling people his morning had gone great.

My name was Danielle Foster. I managed the relationships that kept our biggest accounts renewing. I knew which client wanted a phone call before receiving revised terms, which procurement director needed extra time, and which promises our engineering team could keep.

Most of that work happened before anyone stepped into a boardroom.

Juliet, our CFO, usually appeared when it was time to announce the result.

Last quarter, she had accepted congratulations for a telecom contract I had spent months negotiating. I’d been at the far end of the table with the supporting documents.

I had let it pass. There was another deadline waiting.

Then Derek began receiving invitations to meetings I used to run.

He repeated my talking points on client calls, sometimes badly enough that I had to follow up afterward. Once, a longtime contact emailed me privately.

“Did we downgrade?”

I smiled at my screen, then closed the message. It was less amusing when the next meeting invitation arrived without my name.

Derek’s promotion announcement hit our inboxes at 9:01 on a Tuesday morning.

Our new client liaison: Derek Tate.

At 9:08, my manager forwarded it.

“Loop Derek into anything client-facing going forward. Thx.”

By noon, I was sitting through forty minutes of Derek explaining how he intended to modernize our relationships. He confused basic contract terms, then mentioned his uncle, the CEO, as casually as someone mentioning a weekend barbecue.

I took notes on the accounts he would need help understanding.

That afternoon, Juliet stopped beside my desk.

“We need fresh faces, Danielle. Legacy people can slow deals down.”

I rested my hands beside the keyboard.

“You mean people who can read a contract?”

Her smile tightened.

“We all have different strengths.”

Later, the company newsletter featured Derek shaking hands with a client I had brought in the previous year. The headline celebrated his “modern energy.”

He stopped outside my office, smoothie in hand.

“You saw the newsletter, right?”

“I saw it.”

He grinned and headed toward the elevators.

I stayed after most of the office had emptied. Through the windows, traffic moved slowly toward the expressway. I opened our active agreements and began checking the terms I had negotiated myself.

I hadn’t needed to revisit some of those appendices in years. The accounts had stayed with us because I made sure we met what we had promised.

Two days later, while searching for an old vendor email, I found a forwarded thread about the quarterly client planning meeting.

Derek was attending. Juliet was attending. Even the new intern was attending.

I wasn’t.

At 2:14, I watched them gather inside the glass-walled conference room across from my desk. Juliet gave Derek the chair beside her. He opened his presentation, and she nodded.

I turned back to my work.

Just before four, a message arrived from one of our largest logistics clients.

“Did we really agree to roll out the real-time tracking beta by August?”

I read it twice.

The beta wasn’t ready for internal testing.

I asked the product team to confirm the schedule. Their answer came back quickly: no approved client pilot, no August rollout.

Across the aisle, Derek emerged from the meeting laughing with Juliet.

The client was waiting for my answer.

I closed my laptop for a moment.

Then I opened it again, pulled up the signed agreement, and scrolled to the appendix I had negotiated two years earlier.

Before I answered the client, I needed to read one paragraph.

The rest of the story is in the first comment.

10/08/2026

My Manager Greg Took Credit for My $2.1 Million Savings Plan—and Asked Me to Take Notes While Executives Praised Him. When I Told HR, She Said, “We Don’t Negotiate With Junior Staff.” I Went Home With My Original Employment Contract, Made Tea, and Started Reading. On Page Six, I Found a Signature Everyone Upstairs Seemed to Have Forgotten.

I knew the exact moment my name died in that room.

It wasn’t when the proposal appeared on the screen with Greg’s name at the bottom. It was when our chief financial officer leaned forward, studied the numbers, and said, “Smart work, Greg. This could actually fix the vendor bleed.”

Three chairs away from the coffee machine, I sat with my laptop open and my hands resting on the keyboard.

Those were my numbers.

For two weeks, I had worked until 2:47 a.m., checking contracts, comparing vendors, and following invoice trails everyone else had stopped questioning. By the time I left our downtown Chicago office each evening, the cleaning crew had already started making its rounds.

At home, I reheated leftovers and opened the spreadsheets again.

The finished proposal showed how consolidating overlapping vendor contracts could save Trinican Systems $2.1 million a year. I had checked that figure so many times I could see it when I closed my eyes.

On Friday, Greg had asked to look at my findings.

“Just for visibility,” he said.

He was my direct manager. Sharing the file seemed like an ordinary part of doing my job.

He never answered my follow-up message.

Then Monday morning arrived, and suddenly he was presenting my proposal to senior leadership. My name wasn’t on the opening slide. It wasn’t on the printed summaries being passed around the table, either.

Greg stood beside the screen, gesturing at the chart I had built late Wednesday night.

“By consolidating legacy vendor contracts across our tier-two operational regions, we can generate projected annual savings of $2.1 million.”

Even the phrasing was mine.

I glanced at the executive summary on my laptop. The sentence was still there, exactly where I had written it.

Then Greg looked in my direction.

“Anna, would you mind capturing some of this for the wiki?”

He asked it casually, already turning back toward the executives.

I had spent two weeks building the proposal. He had invited me to the meeting to take notes.

Across the table, someone nodded appreciatively. The CFO asked Greg about implementation. Greg answered using the rollout schedule from the last page of my report.

I started typing.

Every sentence I recorded made it harder to sit there. By the time the meeting ended, the room had accepted a version of events in which Greg had done the work and I had documented his brilliance.

I waited for the chairs to stop scraping against the floor, closed my laptop, and walked straight to HR.

Karen looked up from her keyboard with a practiced smile.

“I need to file an attribution concern,” I said.

Her smile faded a little.

I showed her the original draft, the file history, and the messages Greg had sent before the meeting. His compliment was still there: he had called my findings strong before putting his name on them.

Karen studied the screen, then folded her hands.

“Well, technically, you’re still considered a junior support resource.”

“But it was my analysis.”

“Greg is your direct manager. Final attribution for internal initiatives usually falls to senior leadership.”

She said it gently, as though explaining a seating arrangement I should already understand.

I looked down at the draft again. My name was on the cover. The dates were visible. So were the changes.

“What happens to the record of who actually created it?”

Karen leaned back.

“We don’t negotiate with junior staff, Anna.”

For a moment, the only sound was the printer behind her desk.

Four months of fixing procurement problems. Two weeks of late nights. A proposal worth $2.1 million in projected savings.

And somehow, I was the one asking for too much.

I closed the file.

“Could I get a printed copy of my original employment contract?”

Karen blinked.

“Of course. Any particular reason?”

“Just for my records.”

She printed it, stapled the pages together, and slid it across the desk. Then she returned to her inbox.

On my way out, I passed Greg’s office. He was laughing into his phone, his meeting printouts spread across the desk.

I tucked the contract into my bag and kept walking.

That evening, I hung my coat by the apartment door, put the kettle on, and cleared a space on the kitchen table.

I wasn’t sure what I expected to find. I just wanted to read what I had signed before anyone else told me what I was entitled to.

The first pages were familiar: confidentiality, company property, dispute procedures. I read them anyway.

By page five, my tea had gone cold.

Then I turned to page six.

The formatting changed. Tighter margins. A heading I didn’t remember seeing before.

Near the bottom were two signatures.

One was mine.

I moved the cup aside and drew the page closer.

The second signature was a name I recognized.

I reached for my laptop to check when that person had signed it.

10/08/2026

My boss put his 27-year-old nephew’s name on the $16.8 billion proposal I had spent three months building—then told me to wait outside the boardroom in case the boy needed help.

Through the closed doors, I could hear Braden Montgomery presenting my work to the people who controlled my career.

My name was Dean Vance. I was forty-eight, and for four years, I had worked in corporate development at Hartwell Group in downtown Chicago.

My desk sat beside the emergency exit, across from the copy machines. When everyone else left for dinner, I stayed beneath the fluorescent lights, turning unfinished research and broken spreadsheets into proposals executives could confidently put their names on.

Thirty-four of my plans had gone upstairs with Braden’s signature.

Not one had earned me a promotion.

His uncle, my director, always offered the same explanation.

“You have the experience, Dean. Braden needs the recognition.”

Braden needed recognition. I needed the paycheck.

My father’s heart surgery had left my parents with $34,000 in uncovered medical bills. Every month, I sent another $1,200 home for his prescriptions and rehabilitation. My mother had spent her career running a small library. My father had taught high-school math.

Neither of them had a pension large enough to absorb what happened.

Julian knew that. He knew exactly how much pressure he could apply before I considered walking away.

Then came Harbor Gateway.

Eight acquisitions. A redevelopment along the Chicago River. The largest infrastructure commitment in the company’s history.

I worked seventy-hour weeks assembling the financial models, checking debt schedules, and tracing assumptions back to their sources. By the time the proposal was ready, I could explain every number without opening the file.

Braden spent three days changing fonts and rearranging headings.

He also changed numbers.

Borrowing costs dropped. Revenue forecasts climbed. The cushions I had built around uncertain assumptions became thinner.

The presentation looked more impressive.

The underlying calculations no longer matched the plan I had prepared.

I kept my original version, with its timestamps intact.

And on the morning of the executive review, I brought a plain folder containing a two-page structural summary.

Julian and Braden carried embossed leather binders into the thirty-sixth-floor boardroom.

I took a chair in the hallway.

At first, Braden’s voice carried through the doors in confident bursts. Then it stopped. Another voice spoke. A longer silence followed.

At ten o’clock, Julian came out.

His collar was damp. He pulled the door shut behind him and bent toward me.

“Answer smoothly, Dean. I’ll remember your cooperation at review time.”

He was still negotiating with the man he expected me to be.

I picked up my folder and followed him inside.

The chairman sat at the head of the table. The CFO, general counsel, and independent directors watched me approach.

Braden stood beside the screen with one hand gripping the presentation easel.

The chairman tapped slide forty-two with his pen.

“Mr. Vance, can you explain why these figures change in year three?”

Julian gave me a small, urgent nod.

Everyone waited for me to rescue the proposal carrying someone else’s name.

I set my folder on the table and stood.

For once, Julian had no idea what I was about to say.

Full story in the comments.

10/08/2026

At 52, I Was Left Off the Leadership List at the Company My Grandfather Built—While the New Owner’s Daughter Took Credit for My Work. She Was Heading to Chicago to Promote a $72 Million Partnership I Had Spent Six Months Preparing. Then an Invitation Arrived With My Name on It, and a Speaking Slot Right After Hers.

You know that moment when you realize you’ve been the ghost in every success your company celebrated? When your name is buried in a technical appendix while someone else takes the credit up front?

That was me at 7:30 a.m., sitting in the break room with a paper cup of coffee, listening to the first shift get started on the factory floor.

My name was Roger Bennett. I was 52, and I’d spent 25 years working as a senior manufacturing engineer at Bennett Industrial Solutions.

Yes, the name on the building was mine.

My grandfather had founded the company in 1952. He’d built it into a Midwestern automotive parts manufacturer that employed 340 people across two shifts, making components for Ford and GM.

For three generations, the Bennetts had kept the lights on and the orders moving. But having your name on the building didn’t mean you still had a seat at the table.

Richard Caldwell had bought us out piece by piece. By the time my father died in 2019, Caldwell owned the entire company. He kept our name because customers trusted it.

We had become employees in the business my grandfather built.

I stayed because I loved the work. There was satisfaction in taking a customer’s impossible specifications and figuring out how to make them real. There were also people on that factory floor whose families depended on us getting it right.

Our Ford F-150 brake caliper contract brought in $23 million a year. I’d spent eight months redesigning our casting process to meet Ford’s new requirements, working nights and weekends until we finished 18 percent under budget and three weeks ahead of schedule.

Alexandra Caldwell presented that project to the board as though she’d done the engineering herself.

My name appeared once in her 47-page presentation.

Slide 34. Technical acknowledgments.

Eighteen months earlier, Richard had stepped down and made his daughter CEO. Alex had a Wharton MBA, plenty of energy, and a talent for making ordinary improvements sound like revolutionary ideas.

She also had a habit of closing the conference room door before the people who understood the equipment could get inside.

One morning, I passed her glass-walled office and saw three consultants gathered around her laptop. They were discussing the future of a factory I had spent a quarter century keeping productive.

Nobody asked me to join them.

At 52, I’d started telling myself that was fine. My 401(k) was finally looking healthy. Retirement was about a decade away. I could train younger engineers, do my job, and spend weekends restoring the ’67 Camaro in my garage.

Then Klaus Hoffman came into the picture.

His German engineering company wanted an American manufacturing partner. The proposed agreement was worth $72 million over five years—the biggest deal in our company’s history.

I spent six months preparing the technical side. I flew to Munich twice, worked alongside his engineers, and studied how their automated assembly systems could fit our production lines.

Klaus asked questions about casting tolerances, equipment limitations, and what happened when a production schedule met an actual factory floor.

I could answer them.

We got along because we cared about the same thing: building something that would work after the presentations were over.

Then Patty Walsh from finance accidentally copied me on an email about rental cars for the Chicago Manufacturing Expo.

Alex was giving the keynote. Klaus was flying in from Munich as the guest of honor. Our leadership team would be there to represent the company.

I read the twelve-person attendee list.

Then I read it again.

My name wasn’t on it.

I called Patty.

“Oh, Roger. Didn’t Alex mention she’s keeping the team small?”

“Twelve people?”

“Just the core leadership group.”

I looked through the names again. They had room for the people presenting the partnership. Somehow, they had no room for the engineer who had spent six months preparing it.

That evening, I sat in my garage with the Camaro’s engine parts spread across the workbench. There was grease under my fingernails when an email appeared on my phone.

Subject: Speaking opportunity—Chicago Manufacturing Expo.

Usually, I deleted those invitations. This time, I opened it.

The organizers wanted me to speak about traditional manufacturing excellence in the modern era.

Thursday morning.

The main stage.

Right after Alex’s keynote.

I sat there for twenty minutes, reading the invitation while the engine waited unfinished in front of me.

Then I noticed the confirmed attendee listed for my session.

Klaus Hoffman.

I scrolled back to the schedule and read those two speaking slots again.

Alexandra Caldwell.

Then Roger Bennett.

For twenty-five years, my name had been tucked behind somebody else’s presentation.

Now it was printed directly after hers.

My thumb hovered over the reply button.

Read the full story to see what happened when Alex found out.

10/08/2026

At 49, I walked into a $2.8 billion boardroom closing—and the CEO’s wife called me a temporary assistant. “Someone get that temporary assistant a coffee,” she said into a live microphone. Her husband let the room laugh while I took the last empty chair. Then I opened my leather binder and asked one question nobody at that table wanted to answer.

The first sign was not the laughter. It was the empty space where my name should have been on the mahogany table.

My name is Dean Albbright. I am forty-nine years old. That morning, I walked into Vance Global Energy’s glass boardroom in Manhattan carrying the leather closing binder for a $2.8 billion capital restructuring package my firm had spent eight months building.

Four cameras were already running. Their red indicator lights were impossible to miss. One feed went directly to institutional investors; the others preserved the meeting for the board, legal records, and corporate media.

Nameplates marked the places around the main table. Between two corporate vice presidents, there was a gap where mine should have been.

A junior catering assistant stepped toward me with a hesitant smile, holding a silver tray. Support staff usually remained along the back wall during major closings. I glanced at him, then at that empty space.

“Do they need something before we begin?” I asked quietly, adjusting my jacket.

He flushed and retreated toward the sideboard.

Across the table, several directors pretended to review their briefing binders. Garris Vance, the chief executive officer, kept turning pages in his leather folder, apparently untroubled by the awkwardness unfolding in front of him.

His wife, Victoria, did not look away.

She held no executive title, but treated the headquarters like her personal residence. She inspected my shoes, my suit, my leather binder, and finally my face, taking her time with each.

I walked toward the table anyway and extended my hand to the incoming operating executive.

“Good morning. Dean Albbright.”

Before he could accept my hand, Victoria leaned toward the active microphone.

“Someone get that temporary assistant a coffee.”

Her voice carried clearly through the boardroom speakers.

One vice president chuckled. Another joined him. Then the laughter spread down the table, thin and nervous, while my hand was still extended.

Garris glanced up for a second, then returned to his agenda.

I lowered my hand at my own pace.

The insult registered. So did the fact that nobody intervened—not the directors, not the legal team, and certainly not the man whose wife had just said it into a live microphone.

I moved to the last open chair at the far end of the room. It had no nameplate and no microphone. I placed my binder flat on the table and sat down.

The meeting proceeded as though nothing unusual had happened.

Garris clicked to the opening slide and began speaking in the smooth, practiced language of a man accustomed to having everyone’s attention.

Strategic alignment. Debt restructuring. Leadership transition. Restored investor trust.

He used the word “partnership” four times within the first minute. He never mentioned my name. He never acknowledged my firm.

I kept my hand resting on the binder.

Eight months of work had brought us to this room. There had been negotiations, revised schedules, and documents reviewed long after the office lights should have gone out. Now the man presenting that work was moving through it as if every remaining step were a formality.

Gavin Redford, the incoming operating executive, took over the presentation.

“The debt restructuring facility is effectively secured,” he said, gesturing toward the screen. “At this juncture, we are simply finalizing administrative schedules and ex*****on timing for the primary tranche.”

Several directors nodded.

Victoria leaned back in her chair, smiling. She had already decided I belonged at the edge of the room.

I looked down at the leather cover beneath my hand.

The cameras were still running. The microphones were still live. On the screen, the presentation had moved on to the money they were treating as secured.

When Gavin paused for breath, I opened my binder and slid it forward to a flagged page.

“One question,” I said.

My voice cut through the steady hum of the air conditioning.

Victoria turned toward her husband, visibly irritated that I had interrupted. Garris still had the slide remote in his hand.

I looked directly at Gavin.

“Who is authorizing the release of the money?”

A senior director shifted in his chair. At the far corner, someone stopped writing.

Lawson Prior, the general counsel, froze over his notes.

Then he looked at the page I had opened.

Full story in the first comment.

10/07/2026

For Three Years, I Built the System That Kept Our Cincinnati Company Running. Then My New Boss, Eric, Fired Me and Handed My Job to an Intern. That Evening, I Was Home Watching Frasier With My Cat When the First Email Arrived at 6:43. They Already Needed My Help—and I Had Kept Every Warning They Had Ignored.

The moment Eric turned off his blurred beach background, I knew this wasn’t going to be our usual engineering meeting.

He was sitting in his glass-walled office, looking comfortable. I was at my kitchen table in Cincinnati, with a cooling cup of coffee beside my laptop and March rain tapping against the window.

“Melissa, we’ve appreciated your contributions,” he began.

He paused, then told me the company was moving toward a different “cultural model.”

“Unfortunately, you haven’t been aligning with that vision.”

For a few seconds, I watched his mouth move without really taking in the words.

Three years. That was how long I had spent building the systems beneath everything Vanticor sold. The customer logins. The tools our engineers used to release updates. The background processes nobody noticed unless they stopped working.

Eric called it a change in direction.

I looked at the calendar invitation again. Fifteen minutes. Apparently, that was enough time to end three years.

An HR representative joined the call. She began explaining severance, paperwork, and the return of company equipment while Eric glanced at something on another screen.

“Do you have any questions?”

I rested my hand beside my coffee.

“No. Thank you.”

My own voice sounded steady. That helped.

Then they brought up the reassignment list.

Beside the work I had built and maintained was a name: Kyle Johnson.

His title still included the word “intern.”

I leaned closer to the screen, certain I had read the wrong line.

Kyle was the young man who had once asked me whether “rebooting the cloud” was a real thing. I had explained it patiently. He was learning, and everybody had to start somewhere.

But learning beside someone and taking responsibility for everything they had built were two very different things.

Eric moved on as if that distinction didn’t exist.

I thought about asking who would train Kyle. Then I remembered the handover document I had already written. Thirty-two pages, with procedures, warnings, and the tasks that needed attention before anyone changed how the system was managed.

I had sent it because I knew how much depended on getting the transition right.

Now, watching Eric finish the meeting, I wondered whether he had opened it.

When the call ended, my kitchen was suddenly quiet.

The refrigerator hummed. A car passed through the rain outside. My cat lifted her head from the chair beside mine, checked that nothing interesting had happened, and went back to sleep.

I stood up and opened the window an inch.

The air smelled like wet mulch. Somewhere down the block, someone was taking trash bins back up a driveway. It was an ordinary Cincinnati afternoon, and I needed a minute to remember that my life still existed beyond that laptop.

For three years, I had arranged my days around Vanticor.

A quick question after dinner could turn into three hours of work. A Saturday interruption could swallow the weekend. By Monday, whatever I had fixed was usually invisible again.

People saw the presentation. They saw the polished dashboard.

They rarely saw the person making sure it worked.

I had told myself that being dependable would eventually count for something. Watching my responsibilities slide into a row beside an intern’s name made that belief harder to hold.

Before signing out, I left a small wave in the team chat.

I kept the emails about my work and the warnings I had sent. Then I closed the company laptop.

That evening, I settled onto the couch with my cat and put on a rerun of Frasier. Hearing familiar voices in the apartment felt better than replaying Eric’s carefully rehearsed speech.

At 6:43 p.m., my phone lit up.

Kyle Johnson.

The subject line was: “Uh, hi.”

I let the episode continue for a moment before opening it.

He apologized for bothering me. Eric had told him I might know where to find the credentials he needed. He also couldn’t get the test version of the platform running.

“If you could help, that would be awesome.”

I read the message twice.

Hours earlier, they had ended my job. Now the person they had handed it to was asking me how to do it.

Kyle hadn’t sent an error report. He hadn’t mentioned the handover document.

I looked at the television, then back at my phone.

What bothered me wasn’t that an intern needed help. It was that Eric had apparently sent him to me without explaining what I had already warned would happen.

I set my phone beside the couch and reached for my personal laptop.

There was an old message thread I wanted to check before answering him. I remembered a meeting with Eric and our IT lead, months before any of this.

I had raised the same concern afterward, in writing.

I found the thread and clicked.

My warning was still there.

Directly beneath it was Eric’s reply.

10/07/2026

For Three Years, I Built the System That Kept Our Company Running. Then My Boss Handed My Work to the CEO’s 23-Year-Old Nephew—and Told Me to Help Him Take Over. When He Started Breaking It, They Blamed Me. That Night, Alone in My Apartment, I Opened an Old Email They Had Apparently Forgotten About.

They called it a collaboration meeting. From my chair near the back of our Seattle office, it looked more like Alyssa taking credit for three years of my life.

She stood beside the screen in a cobalt blazer, clicking through diagrams I had drawn and explaining decisions I had made while everyone else was asleep.

“This was a breakthrough,” she told the investors.

I recognized every box, every arrow, every connection. One solution had come to me at 2:43 a.m., sitting on the floor of my studio apartment with reheated Chipotle beside my laptop. I had spent hours fixing a problem that threatened to bring down our test system.

Now Alyssa described it as her vision.

Nobody asked me a question. Nobody even looked toward my chair.

Afterward, I sat in the parking lot with the engine running and my hands wrapped around the steering wheel. I had been with the startup for three years. When I joined, we were still working out of rented WeWork space, arguing about the company logo while I built the system our customers would eventually depend on.

I knew which problems could wait until morning and which ones meant answering my phone during dinner. I had given up eight weekends repairing the process that moved our updates into production.

Somewhere along the way, that reliability had become permission to overlook me.

They called when something broke. When there was an investor presentation or a product meeting, Alyssa went.

That evening, I met Lena, my former roommate, for margaritas. She now worked at a competing company, and she listened while I described the meeting.

“They want your work,” she said. “They just don’t want anyone asking who did it.”

I laughed, but I kept thinking about the empty space where my name should have been.

Alyssa’s habit of speaking over me had become routine. During morning updates, I would start explaining what I had finished, and she would interrupt.

“What Marcy means is—”

Then she would repeat my explanation in different words, as if I had needed someone to translate it.

A few mornings later, she stopped beside my desk.

“We’re reassigning the authentication work for visibility reasons.”

That was the part of the system that let customers sign in and kept their accounts connected as they worked. I had designed it. It had been running reliably for two years.

She was handing it to Josh, the CEO’s twenty-three-year-old nephew.

Josh had already called my tools old-fashioned. Once, he had asked whether Bash, a tool I used almost daily, was an app he could download.

I looked up at Alyssa.

“And my role?”

“You’ll support the transition.”

She said it like she was asking me to move a chair.

Two days later, a mandatory meeting appeared on my calendar: Code Transition Sync.

Josh joined with a grin. Alyssa began explaining the handoff before everyone had settled in.

“Josh and his team will take over,” she said. “Marcy will support the transition.”

Josh leaned toward his camera.

“Hey, Mars. Psyched to work with you.”

My name was Marcy. We had never been close enough for nicknames.

I asked how they planned to handle the parts of the system his team hadn’t worked with before.

Alyssa glanced up from her phone.

“If you have any concerns, Marcy, feel free to file your little complaint with HR.”

Your little complaint.

I wrote those words in the margin of my meeting notes. Then I asked where she wanted the handoff documents.

Within days, Josh’s changes started causing problems in testing. Sign-ins repeated endlessly. Sessions expired without warning. Half the quality assurance team couldn’t get into their accounts.

The messages began arriving.

“Was this a legacy decision of yours?”

“Were there notes on the fallback logic?”

“Can you hop in real quick and fix it?”

Each question came with the same assumption: if something failed, it must have been something I had left behind.

At the next morning meeting, Josh stumbled through his update. Alyssa turned to me.

“Maybe the code’s just outdated, Marcy.”

I looked at the list of changes his team had made. Before the handoff, those same functions had worked for two years.

That night, back in my apartment, I opened a resignation draft. I stared at the first sentence, then closed it without sending.

Instead, I searched my old emails.

I went back before my employee paperwork, before the W-2 forms, to the months when the company had paid me as an independent contractor.

Most of the messages were ordinary: invoices, meeting times, requests to finish something by Monday.

Then a familiar subject line appeared.

Independent Contributor Agreement.

The sender was Nick, our original chief technology officer. There was a PDF attached, signed by the company’s first head of legal.

I opened the email.

Halfway through Nick’s message, I stopped scrolling.

I moved my coffee aside and read the sentence again.

Basketball Trolls

10/08/2026

10/08/2026

10/08/2026

10/08/2026

10/08/2026

10/07/2026

10/07/2026

Address

Telephone

Website

Alerts

Contact The Business

Shortcuts

Share

Category

Listing takedown request