Opišite svoju ulogu u proizvodnom incidentu.

Question

Accepted Answer

Žele vidjeti da ostaneš **miran, metodičan i bez greške** pod pritiskom — prvo obnovi servis, drugo dijagnosticiraj, treće spriječi ponovno ponavljanje. Koristi **STAR**.

## Kako se prema tome

```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
```

## Radni primjer

```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.
```

## Dobro naspram slaboga

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

## Zašto je to važno

Incidenti testiraju mirnoću — tim trebá stabilne ruke, a ne paniku, kada se stvari prekinu.

Pristupi bez greške čini ljude iskrene o uzrocima, što je jedini način da se zaista spriječi ponovno ponavljanje.

Kako se nošiš sa najgorim danom govori više o tvojoj starješinosti nego kako se nošiš s dobrim danima.