Interviewers willen een bewuste, contextbewuste afweging — niet een dogmatisch "altijd snel uitrollen" of "nooit compromissen". Het gaat erom de afweging bewust en zichtbaar te maken.
Waarom het belangrijk is
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
Uitgewerkt voorbeeld
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.
