Kako se odločiš, kdaj prositi za pomoč?

Question

IT Interview Practice · Accepted Answer

Intervjuvarji tukaj iščejo **dobro presojo**: niti ne biti tako trmast, da bi pozabil dan, niti ne biti tako hiter, da nikoli ne poskusiš. Idealna točka je **časovni limit in jasen vprašaj**.

## Kako se lotiti

```text
RULE OF THUMB
→ Try on your own for a bounded time (e.g. 30-60 min)
→ Write down what you tried and where you're stuck
→ Then ask a specific question, not "it doesn't work"
```

## Obdelan primer

```text
S: A build kept failing with a cryptic error.
T: I needed it fixed to unblock my PR.
A: I spent 45 minutes searching and trying fixes, noted the exact error and my
   attempts, then asked a senior with that context.
R: She recognized it in two minutes — a known cache issue. I learned the fix and
   documented it so others wouldn't lose time.
```

## Dobro vs šibko

```text
✓ Time-boxed effort, then a specific ask
✓ Respects others' time with context
✗ Stays stuck for hours out of pride
✗ Pings someone before trying at all
```

## Zakaj je to pomembno

Pravilno spraševanje je veščina: prihrani tvoj čas brez da obremeniš svoje člane ekipe.

Prinašanje konteksta ("tukaj je, kaj sem poskusil") te naredi hitrega za pomoč in kaže iniciativo.

Vedeti, kdaj eskalirati, preprečuje tihe blokade, ki mirno ubijejo sprint.

Kako se lotiti

Obdelan primer

Dobro vs šibko

Zakaj je to pomembno

Povezana vprašanja