News for hackers. Stuff that matters.
Re:Programmer problem solving sequence: should it be like this? by btilly on Monday February 28, 2011 @10:42AM (#2271546)
This workflow is efficient for the programmer, but not for the co-workers or the company. When you go ask a co-worker, you break their flow, which can cost them 15 minutes of productive work while they get their flow back.

If you can figure it out in under 15 minutes, you've saved time overall versus asking the co-worker.

Re:Programmer problem solving sequence: should it be like this? by georgieporgie on Monday February 28, 2011 @02:32PM (#2272496)
The good news is that by merely attempting to phrase a question, people often solve their own problem. So, when a coworker bugs you, just look at them without processing anything they say. If they finish talking and don't have an have an 'aha' look about them after a few moments, only then do you actually switch mental gears, ask them to repeat the question, and go on from there.