Dev Tool Bugs, Assumptions, and a Tiny Bit of Advice

[jbv]

There's another recipe that I've been using for years :
when you're stopped by a bug that you can't locate,
instead of spending the whole night on it (with little
success but lots of stress), do something completely
different for a couple of hours (go to the movies, have
dinner with friends in a nice restaurant), and then go
back to your problem : very often, it only takes a few
minutes before the solution appears right on your face...

I'm not sure I can explain why, but this works...
As if the brain, by shifting the focus to another activity,
was still having an intense background / unconscious
activity...

JB

> JB.....
>
> Good to know there's something besides my raw desperation behind this
> tactic!
>
> On Jun 21, 2005, at 11:45 AM, jbv wrote:
>
> > putting a problem into words for a third party is
> > a very efficient way to solve it (or at least get closer to the
> > solution)
> > and I've been practicing it for years (and not only in coding).
> >
>