[bibbitybobbity]

I've personally experienced the "effective pause" and strongly feel against it. This assumes that software engineers always have ideas on how to fix things and are not autonomous.

In my opinion, it's helps much more to break down/simplify the engineer's thought and the problem they are trying to solve. And then, try to solve it together...

[_ketanbhatt]

1. I do think that the kind of people we have on our team will almost always have some ideas to fix things.

2. The break-down and simplifying happens, of course. But the dev leads the breaking down, with careful guidance by the lead. And it is being solved together, don't you think? The example didn't describe the full end to end design process, but just a part of it which was relevant to explain the point. I think I could have made it more clearer. Thank you for the feedback, noted :)