Kako uravnavate hitrost in kakovost pod rokom?

Question

Accepted Answer

Intervjuvarji želijo **namerno, kontekstno zavedljiv kompromis** — ne dogmatičnega "vedno hitro izpusti" ali "nikoli ne zmanjšaj kakovosti." Ključno je, da kompromis naredite *zavestno in vidno*.

## Kako se pristopiti

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

## Praktični primer

```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 in šibko

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

## Zakaj je to pomembno

Hitrost in kakovost sta običajno težava obsega v prikritosti — zmanjšanje obsega varuje oboje.

Imovanje dolgov na glas drži bližnjice poštene, zato se raje odplačajo kot pozabijo.

Znanje, *katera* kakovost je nezdržljiva, je presoja, ki prihaja s izkušnjami — to je tisto, kar intervjuvarji raziskujejo.