This is a real tension, not a trick question. Productive struggle is how engineers build durable skill, but struggle is only productive up to a point, and deadlines are real. The answer is not to pick a side; it is to read the stakes and the person, then choose deliberately.
| Stakes | Right move |
|---|---|
| Low / learning task, time available | Let them struggle, hints only |
| High / on the critical path, clock ticking | Unblock now, debrief later |
| Repeated stuck on the same thing | Stop, teach the underlying concept directly |
A mid-level engineer is stuck on a flaky test the night before launch. I don't run a Socratic seminar at 9pm; I pair, we fix it, we ship. The next morning we spend twenty minutes on what made it flaky so the lesson still lands.
Always giving answers creates dependence and engineers who never grow. Always withholding them burns time, morale, and deadlines. Good mentoring lives in the judgment between the two, applied case by case rather than as a rule.