惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

博客园 - 三生石上(FineUI控件)
S
SegmentFault 最新的问题
阮一峰的网络日志
阮一峰的网络日志
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
雷峰网
雷峰网
Apple Machine Learning Research
Apple Machine Learning Research
WordPress大学
WordPress大学
博客园 - 司徒正美
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
宝玉的分享
宝玉的分享
爱范儿
爱范儿
月光博客
月光博客
The GitHub Blog
The GitHub Blog
M
MIT News - Artificial intelligence
H
Hackread – Cybersecurity News, Data Breaches, AI and More
B
Blog
T
Tailwind CSS Blog
美团技术团队
D
Docker
V
Visual Studio Blog
Martin Fowler
Martin Fowler
博客园 - 聂微东
The Cloudflare Blog

Arpit Bhayani

Temporal Primer - Building Long-Running Systems What Matters in Production RAG Structure of Every LLM Chat How LLMs Really Work Your Monolith Is Already A Distributed System Databases Were Not Designed For This BM25 JOIN Algorithms Venting at Work Comes at a Reputation Cost Why Half Your Skills Expire Every Few Years Multi-Paxos - Consensus in Distributed Databases MySQL Replication Internals Bloom Filters When You Increase Kafka Partitions Product Quantization The Q, K, V Matrices How LLM Inference Works What are Blocking Queues and Why We Need Them Heartbeats in Distributed Systems How Writes Work in Apache Cassandra Redis Replication Internals How to Handle Arrogant Colleagues at Work How Does a CDN Handle Content Replication You Can't Fix Everything on Day One When Emotions Spill Over at Work Why gRPC Uses HTTP2 Meetings With No Agenda Are a Waste of Time Career Longevity Beats Constant Job Hopping Stay Relevant at Higher Salary Levels Why Distributed Systems Need Consensus Algorithms Like Raft
The Day I Accidentally Deleted Production
Arpit Bhayani · 2025-11-24 · via Arpit Bhayani

Back in 2015-16, I once accidentally deleted the “entire production” at Practo.

Slight exaggeration, but here’s what happened…

There was one EC2 server running the whole stack for one of the acquired companies. On a Sunday afternoon, while cleaning up unused servers from an AWS account, I deleted this EC2 by mistake, and there was no data backup.

The moment I realized (~4 hours later) what I had done, my heart dropped. Panic. Fear. A voice in my head saying: Maybe nobody will notice. Maybe just stay quiet.

I stayed quiet while the team tried to figure out who deleted the instance. When my manager discovered it was me, instead of getting angry, he spoke with me as usual and treated it like a normal mistake.

Thankfully, the data was not highly sensitive or mission critical, but it still should not have happened. Of course, after the incident, we added the necessary guardrails to ensure we do not find ourselves in a similar situation again.

That day, I learned something important: mistakes are inevitable, and the best way to handle them is to face them.

One bad moment should not and would not define your career. A single accident does not erase all your hard work. What matters is what you do next.

People remember:

  • Honesty
  • Accountability
  • How quickly you learn and recover

And I was trying to put mine under the carpet and hide it.

Hiding almost always makes things worse. It creates doubt and damages trust. Speaking up shows integrity. It shows others they can rely on you.

You are not the first person to make a massive mistake, and you will not be the last. We all have our stories. The key is to own it, fix what you can, and take one small lesson forward.

Fun fact: if you never touch production, you will never break production. But you will also never grow, never lead, and never build anything important.

If you want to build, you have to be willing to accept the times you break.