Kako balansiraš brzinu i kvalitetu pod rokom?

Question

Accepted Answer

Intervjueri žele **namjerni, kontekstno-svjesni kompromis** — ne dogmatski "uvijek brzo prosljeđi" ili "nikada se ne pomiri". Ključ je napraviti kompromis *svjesno i vidljivo*.

## Kako pristupiti problemu

```text
1. Identify what quality is non-negotiable (correctness, security, data safety)
2. Find what can be deferred (polish, edge cases, refactors)
3. Cut scope, not core quality — ship less, not worse
4. Name any debt out loud and schedule paying it down
```

## Radni primjer

```text
S: We had three days to launch an MVP for a client pilot.
T: Full feature set wasn't possible without risking stability.
A: I shipped the core happy path solidly, deferred two edge cases behind a flag,
   and wrote a ticket for the debt with a date. I told the client which parts
   were preview-only.
R: The pilot launched on time and stable. We closed the deferred tickets the
   following sprint.
```

## Dobro vs slabo

```text
✓ Conscious tradeoff, debt tracked, scope cut
✗ Shipping broken code silently to hit a date
✗ Refusing to ever bend, missing the deadline
```

## Zašto je to važno

Brzina i kvaliteta su obično skriveni problem opsega — smanjivanje opsega štiti oboje.

Nazivanje tehnološkog duga naglas održava prečace iskrenim, tako da se otplaćuju umjesto da se zaborave.

Znati *koja* kvaliteta je ne-pregovarajuća je presuda koja dolazi sa iskustvom — to je ono što intervjueri istražuju.