Apa kudu dadi prioritas mu ing 90 dina pisanan minangka tech lead anyar?

Question

Accepted Answer

90 dina pisanan mu iki babagan **mbangun konteks lan kapercayan sadurunge ngganti apa-apa**. Pimpinan anyar asring cepet-cepet arep ngono'i apa sing didelok; gerakan sing luwih becik yaiku paham sistem, tim, lan riwayat dhisik. Goleki hak kanggo mimpin sadurunge mulai ngarahake.

## Dene apa kudu diandel

```text
DAYS 1-30  LISTEN & LEARN
  - Read the code, the docs, the incident history
  - 1:1 with every engineer: what's working, what's painful?
  - Understand who depends on you and who you depend on
  - Resist the urge to announce big changes

DAYS 31-60  CONTRIBUTE & DIAGNOSE
  - Ship something small to learn the workflow first-hand
  - Identify the top 2-3 real problems (not pet peeves)
  - Start improving process lightly (e.g. clearer code review)

DAYS 61-90  STEER
  - Set or clarify technical direction
  - Make a visible improvement the team feels
  - Establish how decisions get made
```

## Conto kasunyatan

Kowe neruska tim sing CI-ne alon lan sak-asal. Tinimbang nulis maneh pipeline ing minggu kapisan, kowe abot wulan paham *apa sebabe* alon lan sak-asal, banjur ajoken perbaikan sing tim-mu terima, supaya tetep.

## Klepu sing kudu dilindhari

Misalak "sheriff anyar": ngganti tool, standar, lan arsitektur sadurunge paham apa sebabe barange kaya mangkono. Iku bisa ngrubak kapercayan kanthi cepet.

## Dene apa kudu diandel

Kapercayan iku alat tukar kanggo pamimpinan tanpa wewenang, lan 90 dina pisanan iku nyetel irama.

Yen cepet-cepet, tim ora bakal krungu; dengari dhisik lan dheweke bakal nuntun sampeyan ing panggilan sing angel.