Jelaskan peran Anda dalam insiden produksi.

Question

Accepted Answer

Mereka ingin melihat Anda tetap **tenang, metodis, dan tanpa salah** di bawah tekanan — pulihkan layanan terlebih dahulu, diagnosis kedua, dan cegah pengulangan ketiga. Gunakan **STAR**.

## Cara memulai

```text
INCIDENT ORDER
1. Stabilize — stop the bleeding (rollback, failover, mitigate)
2. Communicate — keep stakeholders updated on a clear channel
3. Diagnose — root cause once it's stable, not during
4. Prevent — a blameless post-mortem with action items
```

## Contoh praktis

```text
S: A deploy caused checkout errors for ~15% of users.
T: I was on call and had to restore service fast.
A: I rolled back the deploy first (service recovered in minutes), posted updates
   every 10 minutes, then traced the cause to an unhandled null from a new API
   field. I added a guard and a contract test.
R: Downtime stayed under 20 minutes. The post-mortem added the missing test to
   CI so it can't recur.
```

## Baik vs lemah

```text
✓ Mitigate first, communicate, blameless follow-up
✗ Debugging live while users are down
✗ Blaming the person who deployed
```

## Mengapa ini penting

Insiden menguji ketenangan — tim membutuhkan tangan yang stabil, bukan panik, saat sesuatu rusak.

Pendekatan tanpa salah membuat orang jujur tentang penyebab, yang merupakan satu-satunya cara untuk benar-benar mencegah pengulangan.

Cara Anda menangani hari terburuk mengatakan lebih banyak tentang senioritas Anda daripada cara Anda menangani hari-hari baik.