r/MaliciousCompliance BOSS Demands I “DELETE ALL FILES” after Firing ME.. OK SIR!
r/MaliciousCompliance BOSS Demands I “DELETE ALL FILES” after Firing ME.. OK SIR!
Welcome to today's Ripestories Podcast! My Name is Ripe and I am bringing you the best Reddit Stories and commentary! We have funny reddit stories from r/ProRevenge, r/MaliciousCompliance and HOA KAREN stories about homeowner associations in America! We also read subreddits such as rslash justnohoa and stories about insane funny entitled Karens! We also have the best top rated Reddit Stories to fall asleep to. Our funny Reddit videos are perfect to sleep to!
Ripestories is available on all major Podcasting Platforms and on YouTube under the @Ripestories handle. We cover stories from popular Reddit Subreddits like Entitled Parents, Pro Revenge and Malicious Compliance. You can find new uploads here every single day of the week! We also cover content about HOA stories and HOA Karens.
Become a supporter of this podcast: https://www.spreaker.com/podcast/ripestories--5912393/support.
Speaker 1: Hey guys, welcome back to more r slash malicious compliance
reddit stories. In today's Ripe Stories video, imagine pouring your
heart and soul into setting up servers and custom code
that kept millions flowing daily and then facing a boss
so clueless and power hungry he thought tech was just
expensive nonsense. The written order he slept on my desk
ended in absolute pandemonium. Let's dive right into the video.
And the first one is titled Smug Boss Demands That
I Delete All Files After Firing Me, posted on r
slash malicious compliance. A couple of years back, I was
working as the head IT systems administrator and lead software
developer for a private microfinance and commercial lending firm based
near the Central Business District in Kampala, Uganda. If you
know anything about the private financial services industry in East Africa,
you know that data integrity and real-time transaction processing are everything.
We basically managed short-term commercial loans, microloans for market vendors,
payroll deduction loans, and agricultural credit lines for clients across
Kampala and surrounding towns like Jinja and Masaka. My job
was to make sure our entire digital infrastructure ran continuously,
without a single hitch, and when I first joined the firm,
their operations were an absolute disaster. They were managing billions
of Ugandan shillings, which I think is actually less than
it sounds, in active loan portfolios using messy paper ledgers,
mismatched desktop spreadsheets, and physical receipt books. Loan approval times
took up to two weeks because the staff had to
manually verify physical files, debt collection logs were frequently lost,
and interest calculations were plagued by human error, over four
solid years I transformed the business by building their entire
digital infrastructure from the ground up. I set up dedicated
local server racks running Windows Server in a secure temperature-controlled
room in our Kampala head office. I wrote custom enterprise
loan management software tailored specifically to our regional lending rules.
I built a central borrower credit database, integrated our local
platform with local mobile money payment networks for instant loan
disbursements and repayments, and created active directory accounts for all
branch loan officers and set up automated nightly backup routines
that mirrored every byte of financial data onto local network-attached
storage arrays. Because of the digital systems I built, the
company boomed. Loan processing times dropped from two weeks to
15 minutes. The company expanded its loan portfolio, opened new
regional branch offices and doubled its administrative workforce. I took
deep professional pride in that setup. Every server cable was
neatly routed and labeled by hand, every database table was
optimized by me and every backup protocol was tested every week.
I worked long hours, handled emergency network maintenance during weekend
power outages and made sure Our local service remained completely
stable despite Kampala's frequent tropical rainstorms and grid fluctuations. The
branch staff relied on my software, the loan officers trusted
the credit scoring system, and the business was generating massive profits.
But then came the corporate restructuring. The original managing director,
who had hired me and actually understood the critical importance
of digital infrastructure... decided to step back from daily branch
operations to focus on expanding our investor network across regional markets.
To handle day-to-day operations at the Kampala head office, upper
management brought in a new general operations manager. His name
was Mukisha. Mukisha was the kind of person who entered
every room convinced that he was superior to everyone else.
He wore fancy suits, carried a high-end tablet he barely
knew how to operate, and spoke entirely in empty corporate jargon.
He had previously worked as a general sales manager for
a retail dry goods distributor and processed absolutely zero understanding
of database management, software development, server hardware, or network security.
To make matters worse, though, Mugisha was deeply arrogant and
paranoid about anything he didn't comprehend, and he comprehended nothing
about technology. So, during his very first week on the job,
Mugisha decided to assert his power by auditing every department
to cut operational costs. Well, unsurprisingly, his primary target was
my job. I remember his first inspection of my server
room during his second week. I was at my desk
monitoring real-time database queries when Mugisha burst in without knocking.
He stood in the center of the room staring at
the server rack with his arms crossed and his mouth
twisted in disgust. What are all these noisy metal towers?
Mugisha demanded, waving a hand towards the server enclosure. I
turned around in my chair to face him. Those are
our primary database servers, Active Directory domain controllers and local
storage arrays. They host our custom landing software. run our
client credit histories, handle automated mobile money repayment callbacks, and
store our accounting ledgers. Mukisha scoffed loudly, shook his head
in disapproval. This is absurd. Just look at the electricity
bill for this single room. Air conditioning running continuously, cooling
fans running non-stop, bright lights on all day. My uncle
runs a large hardware supply business downtown, and he keeps
all his business records on a single flash drive in
his desk drawer. Why are we throwing company money away
on this expensive technical nonsense? I stared at him briefly,
assuming he was just making a poor joke. However, his
face was completely deadpan. Mr. Mogesha, I said keeping my
tone plain and direct, your uncle runs a single retail counter.
At our business, we manage thousands of active loan accounts,
daily compound interest calculations, automated mobile money transactions, and client
credit verification across three regional branches. A flash drive cannot
do that. Mugisha flicked his wrist dismissively. Nonsense. You technical
people love using bloated terminology to protect your inflated salaries
and build artificial budgets. You sit in an air-conditioned room
all day clicking a mouse while the loan officers out
in the field do the actual heavy lifting. I see
right through it. That encounter set the tone for our
entire working relationship. From that day forward, Mugisha made it
his personal mission to micromanage and squeeze my department. A
mere month later, a primary hard drive in our secondary
local backup array flagged a drive failure warning. And yeah,
hard drives wear out over time. Replacing them is just
standard routine maintenance for server hardware. I submitted a standard
purchase order to buy two hard drives to swap out
the failing drive and maintain array redundancy. The cost was
trivial compared to the revenue our automated loan system brought
in every day. Mugisha rejected the purchase request instantly, though.
I went directly to his glass office to explain the
operational risks. Mugisha was sitting behind his white desk, swiping
through the social media on his tablet. Mr. Mugisha, I
need your signature on that drive purchase order. I said,
putting the paper on his desk. Our secondary storage array
is operating in a degraded state. If another hard drive
fails before we rebuild the volume, our local automated backup
redundancy is compromised. Mugisha didn't even touch the paper, though.
He pushed it away with the edge of his pen.
I'm not spending a single shilling on extra hard drives.
Mugisha stated, leaning back in his chair with a triumphant
look on his face. You're just attempting to waste company funds.
I've researched this matter. Hard drives are just storage for files.
You already have files on the main server. Why do
you need double files on extra drives? It is pure
financial waste. It is called data redundancy, I replied, attempting
to explain basic system security. If the primary drive fails,
the redundant backup drive ensures the firm doesn't stop operating.
But if both drives fail without a backup, the entire
business halts. Nothing is going to break. Mugisha snapped back,
raising his voice so the loan officers outside could hear.
You're inventing imaginary disasters to trick me into spending more money.
I'm the general operations manager here, not you. I manage
the company budget and my decision is final. Go back
to your desk. I walked out of his office realizing
I was dealing with a manager whose technical ignorance was
eclipsed only by his stubborn vanity. Two weeks later, Mugisha
escalated his plan to remove me. He walked into the office,
accompanied by a young man fresh out of a local university.
Mugisha called an emergency meeting with all staff in the
main open plan hall. Attention everyone, Mugisha announced loudly, clapping
his hands together. As part of my strategic plan to
streamline operations and remove bloated salary overheads, I fired a
new junior IT technician. He has a diploma in information
technology and understands modern cost-effective business practices. Mugisha then turned
towards me, pointing directly at my chest in front of
all my co-workers. Some staff members in this company believe
they are completely indispensable, Mugisha declared with heavy condescension. They
believe that being in a senior position allows them to
command high salaries and challenge management authority. But technology is
simple now. Anyone can operate a computer. Our new junior
hire will shadow you for the next two weeks to
learn daily tasks, and once the knowledge transfer is done,
we will finalize our departmental restructuring. Everyone in the office
knew who created this system. Everyone knew that the company's
daily revenue relied entirely on the custom landing platform I
had spent four years writing and refining. The staff looked
at me with deep sympathy, but I kept my posture
straight and said nothing. For the next two weeks, the
young graduate shadowed me in the server room. He was
a pleasant young man, but it took less than an
hour to realize he was completely unprepared for the role.
He knew basic desktop hardware troubleshooting and basic office software,
but he had zero experience with Windows Server Administration. Active Directory,
Domain Management, Custom C, Codebases, Sql, Database Queries, or Network Routing.
When I opened the backend database schema that calculated daily
interest yields and mobile money transaction hooks, his face went
completely pale. He admitted to me in private that he
had only built basic static websites in school and had
no idea how to maintain a live financial database. I
felt bad for the young man, but Mugisha was fully
convinced he had staged a masterstroke. Mugisha genuinely believed that
operating an enterprise financial server network was no more difficult
than typing a letter in a word processor. The breaking
point arrived on a late Tuesday morning. I was at
my desk conducting routine software updates when Mugisha marched into
the server room, followed closely by the company's chief accountant,
and Mugisha looked radiant with honor and pride. Shut down
your screen and step away from the workstation, Mugisha commanded loudly.
I turned my chair around. What's the problem? You're being
terminated effective immediately, Mugisha announced, standing tall with his hands
on his hips. Your role as Senior Systems Administrator has
been eliminated. Our new junior hire is taking over all
IT responsibilities, starting today at a fraction of your previous salary.
You have one hour to collect your personal items and
vacate the building. I took a deep breath. I'd anticipated
the termination, but the sheer reckless danger of firing the
Sol System architect without a proper handover was staggering. Mr. Mugisha,
I said, keeping my voice firm and steady, the new
hire doesn't know how to manage this codebase. He doesn't
know how to process backend mobile money reconciliations, handle database locks,
or fix Active Directory dropouts. If you walk me out,
without a transition agreement, your branch offices will lose the
ability to disperse loans or process repayments within hours. Mugisha
threw his head back and laughed loudly. Keep your desperate
warnings to yourself, Mugisha sneers, taking a step towards my desk.
You IT guys always act like you possess magic powers.
You build a few simple folders on a computer and
you think this business cannot survive without you. The new
guy has a formal qualification. He will run this department
far better than you ever did, and for much less money.
Then Mugisha's facial expression shifted into deep, intense suspicion. In
Kampala's competitive microfinance market, client lists and proprietary credit scoring
algorithms are worth a fortune. Mugisha leaned across my workstation,
glaring at me. I know how disgruntled former employees operate,
Mugisha barked, pointing at me. You think you're going to
steal our secrets and information and sell them to our
business competitors down the road? I'm far too smart for that.
I know you have files hidden all over these systems. Mr. Mugisha,
those files and databases are the operational foundation of this
entire company, I said. I don't care about your technical excuses.
Mugisha yelled, hitting his open palm on my desk. I
want you out of this building right now. But before
you take one single step out of that door, I'm
ordering you to access your administrative console and delete all files.
Delete every single file, every database table, every line of
source code, every system folder, and every backup copy of
these computers and of those server drives right now. I
want zero of your files left for our competitors to steal.
Clean out everything completely. The system can work without you.
I sat completely still, letting his words register in my mind.
The sheer magnitude of his ignorance was unbelievable. He was
ordering me, as the root domain administrator, to execute a
total purge of all company databases, software codebases, operating systems,
and backup archives. And because he knew nothing about computers,
he believed that deleting files was just a basic security
cleanup to prevent an employee... From taking company secrets home
on a thumb drive, he literally didn't realize that the
files he was screaming at me to destroy were the
company's entire operational existence. I looked directly at Mugisha. Let
me clarify your exact instruction, Mr. Mogisha, I said speaking
clearly and deliberately. Are you ordering me as part of
my formal exit procedure to destroy all files on my
local workstation as well as all customer databases, core software systems,
system directories and backup archives on the server drives? Yeah,
are you hard of hearing? Mogisha shouted, his face turning
red with frustration. Delete all files, wipe every single thing
clean of those drives and of those systems. I want
zero files remaining on any drive when you walk out
of this room. If you want me to perform a
complete system deletion upon my termination, I require that order
and writing explicitly signed by you as General Operations Manager.
Mugisha smirked, assuming I was attempting to use administrative delay
tactics to protect my work. You think you can play
games with me? Mugisha mocked me, pulling out his pen.
You think I'm afraid to put my authority on paper?
I will give you your written order right now, and
then you will execute it immediately, or I will have
security drag you out and lock you up. Mugisha walked
over to his laptop, which was linked to the network
printer in the room. He aggressively typed out a document,
printed a single copy, grabbed his pen, and he signed
his name at the bottom with a large, dramatic signature.
He slapped the physical paper down on my desk and then,
to demonstrate how complete his control was, he opened his
email client on his tablet and sent an identical copy
of the exact text straight to my personal email address.
I read through every word of the document, pulled out
my phone, checked my personal inbox and verified that the
exact same email had arrived directly from Mogisha's official corporate
email address. This was absolute legal protection. He had handed
me a signed written unequivocal executive command ordering me to
wipe every single piece of business data, application code and
operating system file from the firm's physical hardware. Are you
satisfied now you overpaid fraud? Mugisha sneered, folding his arms.
Now get to work and delete all those files right
in front of my eyes or I call security. I'm
fulfilling your written order immediately, Mr. Mugisha, I replied. I
sat down in my chair and locked onto the master
command console. Mugisha stood directly behind me, with his hands
on his hips, wearing a smug expression, convinced that he
was watching an employee bow to his authority. The junior
hire stood near the door, looking increasingly uneasy. I began
executing the written directive with exact precision. First, I accessed
the primary financial database cluster, and I ran a forced,
unrecoverable format script across the entire database storage volume. And
in less than two seconds, four years of client credit profiles,
loan histories, outstanding balance records... Active payment schedules, daily interest
algorithms and mobile money transaction locks vanished completely. Next, I
connected to the network-attached storage array housing our automated nightly backups.
And then I executed a full partition wipe command destroying
every backup image, restore point and historical archive ever recorded.
And then, of course, I turned my attention to the
custom landing application software I had spent years writing. I
deleted every source repository, every compiled binary fine, every configuration file,
and every execution script from the local application hosts. And finally,
to strictly comply with Mogesha's explicit instruction to leave zero
files accessible on any local drives or systems, I targeted
the server operating systems themselves. I navigated to the core
system paths on the Windows Server Domain Controller, and issued
a forced recursive deletion command targeted directly at the C
Windows System 32 folder. I repeated the exact same command
on the secondary application servers and my administrative workstation console. Well,
across my screens, thousands of core system files, system drivers,
dynamic link libraries, and executable routines were instantly destroyed. Error
prompts flooded the monitors as active background processes crashed in
real time. The Active Directory network collapsed instantly and Mugisha
watched the screen's flicker with terminal error warnings and disappearing
file lists looking utterly satisfied. Excellent. Mugisha boasted loudly. So
now there's nothing left for you to take to our competitors.
I have executed your written directive to the exact letter, Mr. Mugisha.
I sat standing up from my chair. I folded the
signed paper neatly and placed it safely inside my inner
jacket pocket alongside my phone and I then reached down
and powered off the main server units. With the system32
directories completely gutted, those physical machines were now rendered completely
unbootable without a full ground-up operating system reinstallation, I put
on my jacket and looked at the fresh university graduate
who was staring at the blank error screens in horror.
Good luck, I said quietly to the young man. I
walked past Mukisha who was standing tall with a victorious
grin on his face. I walked out of the building,
stepped into the bright Kampala sunshine and took a motorcycle
taxi home. What followed over the next 72 hours was
a complete catastrophe for the company and told to me
by friends at the company. The following morning, normal business
operations were scheduled to begin at 8 o'clock. Loan officers
at the Kampala head office and the regional branches in
Jinja and Masaka opened their computer terminals to process daily
loan applications and record morning borrower repayments, but none of
the workstations could even log into the network. The domain
controller was offline, and when staff tried to open the
internal loan portal, their browsers displayed blank connection errors. When
market vendors arrived at the branch counters to pay their
daily microloan installments via mobile money, the automated system rejected
the transactions because the callback database was non-existent, Confused and panicked,
the branch managers called Mugisha, and Mugisha, still completely clueless
about how enterprise systems worked, marched on to the server
room with his fresh junior hire and ordered him to
restart the computers. The poor junior hire pressed the power
buttons on the primary server racks and the fans were
to life, but instead of booting into Windows Server, the
monitors displayed stark black screens with error messages. Error, no
bootable device found, operating system missing. The junior hire connected
a diagnostic laptop directly to the storage drives. checked the
disk volumes and turned white as a sheet, every single
drive array, backup drive and server partition was entirely empty.
There were no clocks. records, there were no loan ledgers,
there was no source code, there were no backup archives,
there was no operating system, there was literally nothing left.
The junior technician ran out of the server room trembling,
telling Mugisha that the entire company system was gone and
that he had no capability to rebuild a custom financial
infrastructure from scratch and by mid-afternoon on the second day,
total chaos erupted across the company already. Hundreds of borrowers
were standing outside the branch offices, and some wanted their
approval loan funds dispersed, while others wanted to pay their
daily installments to avoid late penalties, but the staff had
no way of knowing who owed what amount, what interest
rate applied, or who had already paid. Mobile money payment
queues were bouncing, daily interest calculations stopped completely, and financial
accounting was totally paralyzed. On the third day, the firm's
original managing director rushed back to Kampala from his original
expansion trip after receiving desperate phone calls from major shareholders
and corporate investors. He walked into complete operational collapse. Branch
managers were trying to manually write borrower names on loose
paper sheets, accountants were arguing with angry clients, and the
firm was losing millions of shillings every single hour. The
managing director stormed into Mugisha's office and demanded an immediate explanation. Mugisha,
desperately scrambling to protect himself, placed all the blame on me.
He claimed that I was a bitter rogue ex-employee who
had maliciously sabotaged the company's service. and destroyed corporate assets
on my way out the door. At 3 o'clock that afternoon,
my phone rang. The screen displayed the managing director's name,
and I answered. Uh, hello? What did you do to
our systems before you left? The managing director roared through
the speaker, his voice shaking with anger. Our business is
completely frozen. We are losing a fortune, and clients are
threatening legal action. Investors are pulling out, and Mugisha tells
me that you wiped our servers out of spite. I
will personally make sure you face criminal charges for malicious damage.
I remained completely steady and composed. Sir, I replied directly,
I did not sabotage anything. I simply executed an explicit
written executive order issued to me by your general operations manager, Mr. Mugisha,
during my formal termination. What are you talking about? The
managing director shouted, Mugisha would never order you to destroy
our core servers. Well, I suggest you open your email
inbox right now, sir. I'm forwarding you the official termination
directive and data security order that Mr. Mugisha printed, signed,
and emailed to me from his official corporate account minutes
before I vacated the premises. I opened my laptop and
forwarded Mugisha's signed email directly to the managing director's personal inbox.
A long, heavy silence fell over the call for nearly
two minutes as the managing director read the document. I
could hear his heavy breathing over the line as he
absorbed the exact words Mukisha had written. You are explicitly
commanded and ordered to immediately delete all files, database, repository,
software code, system directories and backup archives. Leave zero files
accessible on any local drives. He put this in writing,
the manager director asked, his voice suddenly dropping from intense
anger to absolute shock. He certainly did, I replied. He
actually stood right behind my chair and threatened to have
security remove me if I didn't fulfill his written order
to wipe all files of the server, workstation and backup
drive under my control. I simply complied with the signed
command of my superior officer. The managing director let out
a deep agonizing groan. Is there any way to restore
the data? Can we just pay you to come back
today and restore the client database from the backup arrays?
There are no backups, sir, I explained clearly. Mr. Mugisha
explicitly ordered me to delete all files on the local
server drives and the backup storage units too. In strict
compliance with his signed command, I formatted the backup drives
and purged the archives, and because he officially rejected my
purchase request for secondary backup drives weeks ago, no other
copies exist. The managing director swore loudly, slammed his receiver down,
and ended the call. From what former co-workers told me later,
the confrontation that took place in Mugisha's office shortly after
was terrifying. The managing director dragged Mugisha into his office
and screamed at him so violently that staff outside could
hear every single word. Mugisha tried to claim that he
only meant personal desktop files, but the managing director shoved
the signed document into his face, highlighting the exact words
Mugisha had typed, database, repository, software code, system directories, and
backup archives. And basically then after, Mugisha was fired for
gross incompetence, massive negligence, and causing the financial destruction of
the branch network. The company attempted to recover, but the
damage was sadly irreversible. The firm was forced to suspend
operations for months and they had to ask clients to
bring in their old physical paper receipts to manually reconstruct
active loan balances, leading to massive financial disputes, widespread fraud,
and thousands of lost loan records. Regulators stepped in and
issued severe compliance penalties for failing to maintain required financial records.
By the time they managed to buy off-the-shelf basic accounting
software and set up a basic local desktop network, over
70% of their client base had abandoned them and they
lost their primary investor funding, had to close down their
regional branches in Jinja and Masaka, and laid off most
of their remaining workforce, and then moved out of their
prime central business district office into a tiny rundown two-room
rental space on the outer edge of Kampala. They were
reduced to a tiny struggling operation barely hanging on. My situation, however,
took a dramatic turn for the better. Kampala's business community
is close-knit, and within three weeks of my departure, Several
major commercial clients and private investment groups who were disgusted
by my former employer's sudden operational collapse reached out to
me directly. They knew that I was the developer who
had built and maintained the lending platform that had served
them reliably for four years. They asked if I could
build a custom, highly secure financial technology system for their
own corporate operations. Seeing a massive business opportunity, I used
my savings to register my own independent software architecture and
enterprise IT consulting company in Kampala. Working tirelessly, I designed
a brand new modern cloud-backed financial software suite from the
ground up. It was faster, more secure, and infinitely superior
to the local legacy platform I'd built years prior. Those
commercial clients signed long-term service contracts with my new company immediately.
and my business exploded. Private lenders, credit unions, and commercial
firms across Uganda hired my company to build their custom
software systems, manage their database infrastructure, and handle their network security.
And the next one is a fantastic malicious compliance story,
which is titled, I followed the company rules to help customers.
So I used to work on the public health desk
in tech support for a large UK electrical retail chain
call center based in Nottingham, And if a customer had
bought an extended warranty and the customer's PC was sent
away for repair, but for whatever reason took longer than
six weeks to fix, the customer was entitled to a
refund slash replacement. This was known as the six-week rule. However,
the internal company rule was only if the customer asked
for it. If you were observed just offering it, it
could lead to a disciplinary, as you were technically costing
the company money, so we couldn't just tell customers about
it right away. I thought this was a bit crappy
as the customers had paid for it as part of
the overpriced extended warranty and some people just did not
read the instructions or didn't really understand computers and all
the paperwork that came with them. A lot of our
customers were of the where's the any key type and
the relevant paragraph was buried in the TNCs. As you
can imagine, some people would be getting rather frustrated after
waiting six weeks for their PC to come back, so
as the first line support person, I got the brunt
of their frustrations. If they were rude or obnoxious, I
would apologize and make them wait longer for their repair,
but if they were nice and respectful, I would ask
if they had their extended warranty documentation in front of them,
and then ask them to read out loud from the TNCs.
As soon as they read over the part that mentioned
a six-week rule, I would say, oh, I'm glad you
mentioned that. Would you like me to arrange a replacement
slash refund for you? Most either didn't know it was
there or didn't realize that's what it meant, and were
happy that I could help. And since it was the
customer who had first mentioned the six-week rule, I could
not get in trouble either. And yeah guys, thanks for watching.
I will see you again tomorrow.