in reply to Solving problems and fixing bugs

If something doesn't make sense, you're not seeing something.

I came to understand that one only after banging my head against it a dozen times. Usually it's a situation where the code appears to be perfect but won't run so I spend a few hours tweaking the perfect code into other equally valid versions, trying to force it to make sense, until I snap out of this moronic fog and check the config files or the environment or whatever and find that someone turned on something crazy somewhere or XYZ got silently upgraded to the wrong version or whatever.

Seems stupid but once I finally realized that if it looks right but runs wrong, I almost never have to fix it, I just have look elsewhere. The amount of time I've saved lately with this is *slowly* adding up to the amount of time I've wasted in the past fighting against it.

Replies are listed 'Best First'.
Re^2: Solving problems and fixing bugs
by nefigah (Monk) on Mar 23, 2008 at 08:55 UTC

    Amen to that. This is especially true if I'm using a language/framework I'm not super familiar with; I keep 2nd-guessing my syntax or rewriting stuff that was actually functioning in my search to locate the problem. This can be good for learning, but it's a bummer for beauty sleep (and heaven knows I could use more of that!)


    I'm a peripheral visionary... I can see into the future, but just way off to the side.

Re^2: Solving problems and fixing bugs
by Your Mother (Archbishop) on Mar 27, 2008 at 15:54 UTC

    Oh, Hubris, thy name is Yer Mamma. Yesterday I couldn't get one of my computers to send a file over wireless to another which had the right printer attached. So I tried the laptop instead. Then someone else's laptop. Then started fiddling with firewalls. Then started passing from A --> B to try to get to C. Then finally went and checked the unreachable computer after an hour of this. Its connection had dropped. L.