I worked three sleepless nights straight, fixing a critical bug that had nearly pushed our company off a cliff.

At the all-hands meeting, my boss looked me in the eye and said,

“Sophie Miller, you really ought to learn a thing or two from Vivian Lee.”

Seeing the confusion on my face, he made himself clearer.

“Isn’t it true?”

“You’re the only one in this whole company who just buries her head in work, with zero sense of teamwork.”

“Look at Vivian—she knows how to boost morale. A box of baked mac and cheese was all it took to lift everyone’s spirits.”

“Build relationships first, then do the work. She gets it better than you do.”

I got the message.

So you’d rather have someone who buys $5 mac and cheese than someone who saves the company’s lifeline?

Fine.

Right there in front of him, I calmly opened my email and typed one sentence:

“Michael Chen, does the CTO position you offered last month still stand?”

“I can bring a fully self-developed solution and start anytime.”

At four in the morning, the last redundancy test finally passed.

The “system crash” alarm that had lasted for three days and nights was finally cleared.

I practically collapsed into my chair, the stabbing pain at my temples making my vision go dark.

I had barely closed my eyes for five minutes when the smell of cheese and cream filled the room.

Vivian, the management trainee, walked over with a bright step, carrying an elegant lunchbox.

“Sophie, you’ve worked so hard. Everyone’s been worried about you.”

She set a steaming box of baked mac and cheese on my desk.

“Eat something! I specially ordered this—everyone loved it!”

I had no appetite and just waved her off wearily.

For three days, I hadn’t slept, surviving on coffee and adrenaline.

Our client called every hour, their tone shifting from “concern” to “anger” to “threatening legal action.”

It was me—together with a few core team members—who locked ourselves at our desks, working 72 straight hours, going through over a million lines of code line by line.

In the end, I tracked down a deeply hidden conflict caused by a third-party plugin update.

That discovery saved a multi-million-dollar client and kept the company’s cash flow from breaking apart.

And yet here was Vivian, with her fragrant mac and cheese, filling the office with a cheerful atmosphere that clashed sharply with my exhaustion.

At 10 a.m., David Ross called for an all-hands meeting.

Everyone gathered in the office corridor, their faces relieved as though they had just survived a disaster.

David strode onto the small stage, beaming, microphone in hand.

He gave a rousing speech describing the severity of the crisis—then dramatically turned the tone.

“But! We pulled through!” he said, throwing his arm wide.

“And what did we rely on? Our unbreakable team spirit!”

He clicked the remote, and a giant photo appeared on the screen behind him.

In the photo, everyone but the three of us sat together, holding up boxes of mac and cheese, smiling like it was a party.

In the background was a banner Vivian had hung: “Go team! We’re the best!”

“At the most critical moment, it was our management trainee, Vivian,” David said, turning his approving gaze toward her.

“She didn’t panic—she thought about how to steady morale and keep everyone going!”

“One little box of mac and cheese warmed everyone’s stomach and brought their hearts together!”

“And that,” David concluded, “is what we call team spirit!”

His gaze swept over the room and finally landed on me—cold and probing, like a needle.

There was no praise, no recognition, only judgment from above.

My three sleepless nights of battle were completely erased in that moment.

The sweet, cloying smell in the air made me nauseous.

My colleagues clapped enthusiastically—for Vivian’s mac and cheese, for David’s so-called “team spirit.”

No one looked at me, as if the person who had just saved the company didn’t exist at all.

Vivian stood among the crowd, her head slightly bowed, a demure and perfectly measured smile on her lips.

That huge wave of emptiness crashed through me.

I stood, silently returned to my desk, opened my laptop, and began writing the post-mortem report on the crisis.

From the hallway, I could still hear David’s voice:

“…so you see, for a company to grow, it can’t rely on technology alone—it needs culture! Culture is our ultimate weapon!”

After the meeting, I took the draft report and knocked on David’s office door.

“Come in.”

I placed the report on his desk, speaking concisely.

“David, here’s the technical post-mortem and follow-up prevention plan.”

He leaned back in his chair, slowly picked up his stainless steel mug of herbal tea, blew on it, then flipped through the report.

He didn’t read the technical analysis, just skimmed the conclusion, nodded, and pushed it aside.

Then he looked at me.

I must have had no expression left, not even the strength to fake a polite smile.

He noticed.

Setting down the mug, he laced his fingers together, leaning slightly forward with a tone meant to sound fatherly.

“Sophie, sit.”

I didn’t move.

He didn’t seem to care and kept going.

“You’re upset, aren’t you? Because I praised Vivian in the meeting and didn’t mention your contribution?”

I stayed silent.

He sighed, like he was disappointed in my lack of emotional intelligence.

“Sophie, honestly, you really should learn from Vivian.”

He said it as casually as if he were commenting on his coffee.

I stared at him—the man I had followed for five years, the one I had personally helped build this company’s entire technical framework from scratch.

His face carried an expression that said, I’m enlightening you.

“All these years working together, you’ve always just buried yourself in code. You finish your tasks, hand in your reports—and that’s it. No involvement in team-building.”

“Once the system is stable and the report is filed, then what? Nothing.”

“Have you ever thought about how to unite people? How to energize the team?”

He pointed out the window. Vivian was handing out new plants to everyone, the hallway buzzing with laughter.

“See how she instantly senses the team’s emotions, lifting morale in a crisis?”

“It didn’t cost much, but the thoughtfulness, the insight into people’s hearts—how many can do that?”

“Build relationships first, then do the work. She understands this better than you.”

I listened with a blank face, utterly calm—almost amused.

So, all my blood, sweat, and tears were worth less than a $5 box of mac and cheese.

He must have forgotten—if I hadn’t fixed the system, there wouldn’t even be mac and cheese. Everyone would’ve been packing their bags to go home.

I looked at his self-satisfied face, slightly sagging from years behind a desk.

And suddenly, everything became clear.

All those moments when I used to tell myself, he’s a business guy, he doesn’t get it—they flashed through my mind like a fast-forward reel.

This wasn’t the first time.

When Vivian had just joined, the company was preparing for the Annual Tech Summit.

David asked me to handle the content and Vivian to handle the presentation format.

I led my team to compile all the year’s major technical breakthroughs and architecture optimizations into detailed documentation and slides.

Vivian, meanwhile, decorated the entire venue like a hip coffee shop and designed a bunch of party games.

At the final prep meeting, David slammed my slides on the table and barked,

“Sophie! Your slides are crammed with code and charts—who’s going to enjoy that?”

“Learn from Vivian—make everyone feel the magic of technology in a light and fun atmosphere!”

He publicly praised Vivian for being “creative” and “great at engagement,” while ignoring my team’s painstakingly prepared technical work.

In the end, he ordered me to turn the summit into a “Tech Carnival.”

Content was secondary—what mattered was that it looked lively.

I told him that would turn a serious technical exchange into a shallow sideshow.

He accused me of being rigid, inflexible, full of “engineer arrogance.”

So I gave in.

I spent two more days repackaging all my hard work into a hollow, flashy shell.

Naturally, the event was declared a “great success,” because the photos looked good and got plenty of likes on LinkedIn.

At the end of the summit, David made sure to call Vivian up on stage in front of everyone and said,

“This event’s success owes everything to Vivian’s creativity. She made our tech go viral.”

Another time, the company needed a fundamental system overhaul to prepare for three years of projected growth.

I started technical research six months in advance, wrote a report and implementation plan tens of thousands of words long—

from server selection to data migration, every step tested and risk-proofed.

I submitted the plan, and David sat on it for a month without approval.

When I asked him, he sounded impatient.

“Sophie, this plan is full of jargon.”

“And the investment is huge, the risk even bigger. What if it fails? The current system still works, doesn’t it?”

“Can’t you make something that I—and the marketing team—can understand?”

In that moment, I just felt utterly exhausted.

I built systems with professionalism, with logic, with respect for technology—

not to write a PR brochure that makes non-technical people nod in approval.

I wasn’t incapable of such tricks. I just refused to stoop to them.

I used to believe that in a tech company, technical strength was the ultimate foundation.

Now I realized I had been wrong.

In David’s world, technical strength was only the bare minimum—expected, taken for granted.

What really earned you points were the things that let him boast at conferences and on LinkedIn: “vibes,” “user experience.”

He didn’t want a precision instrument quietly solving core problems.

He wanted a flashy speaker system playing background music.

The company’s technical framework was now stable, the core business running smoothly—