4 ms·
This is huge. My rule of thumb is that if you feel "stuck" for more than an hour you need to: (1) stop what you're doing, (2) go for a walk, and (3) let ~every
by ncphillips 8y ago
This is huge.
My rule of thumb is that if you feel "stuck" for more than an hour you need to: (1) stop what you're doing, (2) go for a walk, and (3) let ~everyone know you're stuck.
If nobody can help because they don't understand what you're working on, then that's a huge red flag. You definitely should talk to them. The more people that understand that problem the better.
- C1sc0cat 8y agoI used to like to walk to the nearest pub for lunch and have a pint and couple of pinball games and mentally review the problem whilst playing.
- KenanSulayman 8y agoThis. Teams can become so much more effective when lack of experience with certain parts of the code is communicated. It's a big step for a lot of people at first, because they are afraid of showing that they are actually stuck (“I'm afraid others will think I'm incompetent”).
- thrower123 8y agoAn hour is not enough time. That's barely long enough to have started thinking and researching a problem. Of course, it would probably make more sense to scale the timeout with the difficulty of the thing being done; if you're stonewalled on something trivial vs pondering architectural issues.
- CydeWeys 8y agoIt depends on the scale of the problem. An hour is entirely too long to waste on trying to figure out which API method to accomplish a given task, but not nearly enough to spend on properly architecting a new system.