Iddeskrivi r-rwol tiegħek f'insidient ta' produzzjoni.

Question

Accepted Answer

Irridu jivvejruk li tibqa' **kalm, metodik, u mingħajr kulpa** taħt pressjoni — irrestawra l-servizz l-ewwel, diagnos it-tieni, u prevjeni r-ripetizzjoni it-tielet. Uża **STAR**.

## Għaliex dan huwa importanti

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

## Eżempju maħdum

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

## Tajjeb vs dgħajjef

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

## Għaliex dan huwa importanti

L-insidenti jitpruvaw il-kalma — il-firxa għandha bżonn idejn stabbli, mhux paniku, meta ħaġa tkun miksuba.

Approċċ mingħajr kulpa iżomm in-nies onesti dwar il-kawżi, li huwa l-uniku mod biex titteprivinix ir-ripetizzjoni.

Kif tittaħdem il-jum agħar jgħid aktar dwar is-seniorità tiegħek milli kif tittaħdem il-ġumejn tajba.