When Misplaced Trust Leads to Ruin

The intern, Jake Wilson, stood before the projector screen. The red dot from his laser pointer jittered across an enlarged screenshot of backend logs, finally settling on a string of IP addresses.

"Mr. Miller, data doesn't lie."

His face lit up with the excitement synonymous with catching a thief red-handed.

"Ms. Chapman has been hogging company server resources for months. Traffic spikes always hit in the middle of the night. I dug into it. These ports are all running private rendering jobs she took on the side.

"It's classic resource siphoning by using the company's electricity to make her own money. This kind of behaviour doesn't just drive up operational costs, but it's also slowing down our core workloads.

"If we don't shut it down now, next week's cloud launch is going to crash hard. And it could be even worse—she might be selling the company's core data! That's straight-up misappropriation of assets!"

Everyone turned to look at me. There was contempt and a trace of smug satisfaction in their eyes.

Our boss, Martin Miller, leaned back in his executive chair. "Susan, Jake's been here less than three months and already spotted this. You're the operations director and the technical fallback. Care to explain?"

Explain?

I looked at Martin's face, every line screaming calculation, and felt a wave of disgust rise in my chest.

Three years ago, Martin had dragged me into starting this company. He said we didn't have the cash to buy servers and couldn't afford cloud computing.

I didn't hesitate. I hauled the graphics workstation—dual EPYC CPUs, 512 gigs of RAM, four pro-grade GPUs—from my studio. It was barely six months old.

The hardware alone had cost me 120 thousand dollars.

I had even assured him at the time, "This thing's a beast. It'll carry us for now."

Somehow, that "for now" stretched into three years. The company's core code ran on it. Dozens of terabytes of project assets were stored on it.

To keep this power-hungry machine running smoothly, I even paid out of pocket to set up a dedicated enterprise line. The electricity bill would get mailed to my house every month.

Now, Jake foolishly called it a company server. The system maintenance scripts and automated backups I ran late at night had somehow turned into the so-called private freelance jobs.

What was even more interesting was that Martin knew exactly whose machine this was, yet the look in his eyes said otherwise.

"What am I supposed to explain?"

I flicked the pen in my hand onto the table. The plastic barrel hit the surface and bounced twice.

"The traffic spike is from a full stress test. I'm load-testing the whole system for next week's launch," I said. "As for Jake's claim about side gigs, have him show actual proof—job records, payment logs, anything with a paper trail."

Jake scoffed, arms crossed. "Ms. Chapman, we all work in tech here. No need to play dumb. That's an encrypted partition. I don't have the permissions, so I naturally can't pull any logs. In fact, why don't you hand over the root password so I can take a look?"