He Deleted My Personal Directory to Prove His Power -The Whole Database Erased Itself — Transcript
Full transcript
- 0:00The cursor hovered over my personal
- 0:02server profile for exactly 3 seconds
- 0:04before he clicked delete. My new
- 0:07director did not even look at me when he
- 0:09committed the act. He kept a smug grin
- 0:11plastered across his face while the
- 0:13confirmation dialogue flashed on the
- 0:15monitor. He told me I did not own the
- 0:18code, his voice dripping with
- 0:19condescension.
- 0:21The server icon blinked twice and
- 0:23vanished, plunging the entire room into
- 0:25silence. That was the moment everything
- 0:28went dark across the office network.
- 0:30Someone screamed down the hall as
- 0:32monitors flickered to black. My boss
- 0:34went from smug to ghost white in under
- 0:37two seconds. I calmly closed my laptop,
- 0:40slid it into my bag, and smiled. The
- 0:42whole corporate database had just erased
- 0:45itself following that single
- 0:46administrative click. I stood up with my
- 0:48messenger bag over my shoulder and
- 0:50walked toward the exit like it was a
- 0:52regular Tuesday. Behind me, chaos
- 0:55erupted with overlapping voices and
- 0:56ringing phones while my supervisor sat
- 0:59frozen in absolute disbelief. My name is
- 1:02Maya Vance. For 15 years, I worked as a
- 1:05senior systems architect at a tech firm
- 1:08specializing in healthcare databases. I
- 1:10built those systems from the ground up,
- 1:13pouring late nights and weekends into
- 1:14code that actually worked. I learned
- 1:16early from my parents how to solve hard
- 1:19problems and why empathy matters in
- 1:20technology. Writing code at 2 in the
- 1:23morning affects real nurses pulling
- 1:25patient records at 2 in the afternoon.
- 1:28Servers are not just metal boxes, but
- 1:31infrastructure for human beings trying
- 1:32to do their jobs. Then my supervisor
- 1:35arrived carrying a titanium briefcase
- 1:37and an arrogance that matched his
- 1:39expensive suit. He knew buzzwords and
- 1:42consulting frameworks, but nothing about
- 1:44our actual systems. During our very
- 1:47first team meeting, he declared our
- 1:49setup inefficient and demanded immediate
- 1:52cloud migrations and modern DevOps
- 1:54principles. One of our senior developers
- 1:56raised his hand to explain that our
- 1:58uptime was 99% and intentional, but our
- 2:02new director dismissed him completely.
- 2:05He wanted to cut costs and streamline
- 2:07everything without understanding the
- 2:08risks involved. By the third week, he
- 2:12targeted me specifically. He scheduled a
- 2:14Friday afternoon meeting with no agenda
- 2:17and pulled up a directory tree of my
- 2:19personal workspace. Every developer had
- 2:22one for automation tools and utility
- 2:24scripts, but mine was extensive because
- 2:26of my tenure. He called it a security
- 2:28risk and demanded a full audit, knowing
- 2:31it was a bureaucratic trap. I spent the
- 2:34next two weeks compiling documentation
- 2:36while he fired veteran support staff and
- 2:39canceled monitoring services, leaving
- 2:41our infrastructure vulnerable and
- 2:43causing our best team members to resign
- 2:45in frustration. The breaking point
- 2:47arrived on a Thursday when he brought
- 2:49corporate auditors, unannounced, to
- 2:51inspect my workspace.
- 2:53They found everything clean, documented,
- 2:56and fully compliant. Furious that his
- 2:59trap failed, he cornered me in the
- 3:00hallway and doubled down on his demands.
- 3:03The following morning at dawn, he sent a
- 3:05departmentwide email announcing that all
- 3:07personal directories would be
- 3:09decommissioned by the end of the
- 3:10business day with zero exceptions. He
- 3:14gave us 10 hours to migrate years of
- 3:16work or watch it get permanently deleted
- 3:18by management. I called a former
- 3:21colleague who reminded me about the
- 3:22legacy database reconciliation script I
- 3:26had written nearly a decade ago. It ran
- 3:28silently every single night ensuring
- 3:31data integrity between our old system
- 3:32and the new production servers. Nobody
- 3:35else knew it existed because it never
- 3:37failed. If that script stopped running
- 3:40without proper migration, the databases
- 3:42would slowly drift out of
- 3:43synchronization until a catastrophic
- 3:45safety shutdown triggered. I spent the
- 3:48afternoon documenting every single
- 3:50script in my workspace and warned
- 3:53management in writing about the critical
- 3:55dependencies. At 5:00, my supervisor
- 3:58walked up to my desks and demanded
- 4:00confirmation that my personal directory
- 4:02was cleared. I told him it was
- 4:04completely removed, exactly as he had
- 4:06commanded in writing. He smiled in
- 4:08triumph, thinking he had won his petty
- 4:10power play. But the moment my directory
- 4:13vanished, the active database
- 4:15connections severed, triggering the
- 4:17safety protocols I had documented.
- 4:20Within seconds, monitors across the
- 4:22office flickered and died. Alarm started
- 4:24ringing down the hall as every single
- 4:26database went offline simultaneously. My
- 4:29supervisor rushed to the server room and
- 4:31found complete chaos. When the senior
- 4:34administrator realized the
- 4:36reconciliation script was gone from my
- 4:38deleted folder, he looked at me in
- 4:40horror.
- 4:41My supervisor demanded that I restore
- 4:43the script immediately, but I calmly
- 4:45showed him my written warnings and his
- 4:47own reply, telling me to delete
- 4:49everything without delay. He realized he
- 4:52had walked right into his own trap. He
- 4:54begged me to fix the disaster he
- 4:56created, threatening me with termination
- 4:58before remembering I was the only person
- 5:00who knew how the legacy systems worked.
- 5:03I laid down strict terms for my help. I
- 5:06demanded a formal written
- 5:08acknowledgement from executives that the
- 5:10outage resulted from his reckless
- 5:12directive, full restoration of my
- 5:14administrative permissions, and zero
- 5:17retaliation. He had no choice but to
- 5:19agree as phone calls from angry
- 5:21executives flooded his phone. I spent
- 5:24the entire weekend working through the
- 5:26night alongside my colleagues,
- 5:28stabilizing the databases and rebuilding
- 5:30the core framework of the reconciliation
- 5:32script until every was fully operational
- 5:35by Monday morning. When the crisis
- 5:38finally ended, I submitted my
- 5:40resignation and handed over my badge.
- 5:42The interim director read the incident
- 5:45reports, acknowledged that my warnings
- 5:47were entirely correct, and thanked me
- 5:50for handling the disaster
- 5:51professionally. I walked out of that
- 5:53building knowing I had protected my
- 5:55legacy and stood my ground against
- 5:57corporate arrogance. Today, I run my own
- 6:00successful tech consultancy, helping
- 6:03companies avoid these exact disasters. I
- 6:05still check legacy server profiles and
- 6:08if a client ignores my warnings, I
- 6:10simply follow orders exactly as given.
About this transcript
This page contains the full transcript of He Deleted My Personal Directory to Prove His Power -The Whole Database Erased Itself by Liza Corporate Tales, generated from the public captions YouTube serves with the video. The transcript has 970 words across 163 segments, with the original timestamps preserved so you can click any line to jump to that moment in the embedded player.
What you can do with it
Use the transcript to take notes, quote the speaker, build a study guide, generate a summary with ChatGPT or Claude via the YouTube Summary tool, or export it as a timed subtitle file with YouTube to SRT. You can also re-open it in the transcriber to choose a caption track available on the video.
Free YouTube transcript tool
YouTube2Text is a free YouTube transcript generator — no signup, no daily limit. Paste any YouTube link and get the full transcript instantly, with timestamps, click-to-jump, caption language selection, AI prompts for ChatGPT, Claude, and Gemini, and exports to TXT, SRT, VTT, or Markdown.