Hvordan balancerer du hastighed og kvalitet under en deadline?

Question

Accepted Answer

Interviewere ønsker sig et **bevidst, kontekst-bevidst kompromis** — ikke et dogmatisk "ship altid hurtigt" eller "giv aldrig efter". Nøglen er at gøre kompromisset *bevidst og synligt*.

## Sådan tilgår du det

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

## Gennemarbejdet eksempel

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

## Godt versus svagt

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

## Hvorfor det betyder noget

Hastighed og kvalitet er normalt et skjult omfangsproblem — at reducere omfanget beskytter begge dele.

At nævne teknisk gæld højt holder genveje ærlige, så de bliver betalt tilbage i stedet for glemt.

At vide, *hvilken* kvalitet der er ikke-forhandlelig, er dømmekraft, der kommer med erfaring — det er det, interviewere udforsker.