Re: Greatest programming mistakes and what to learn from

Not the greatest mistake, but a timeless classic I'm-a-moron moment is when you realize that you're editing one thing, looking at another thing and wonder why nothing happens.

The only improvement over the years is the frequency with which it happens, and the time it takes to realize that you are, in fact, behaving like a moron again.

Comment on Re: Greatest programming mistakes and what to learn from

Replies are listed 'Best First'.
Re^2: Greatest programming mistakes and what to learn from by TilRMan (Friar) on Dec 24, 2004 at 01:31 UTC
Another, similar classic is accidentally opening the same file twice in different sessions, editing one, saving and closing it, and then habitually saving and closing the other on top of the first. What I've learned is to only have one editor open at a time, ever. What I should have learned is to use an editor which notices a file that got changed out from under it.	[reply]
Re^2: Greatest programming mistakes and what to learn from by wolfger (Deacon) on Dec 23, 2004 at 13:37 UTC
...or when you are trying to solve a problem, and you run to Perl Monks for help, and you accidentally post the wrong set of code to your node... Doh! -- Linux, sci-fi, and Nat Torkington, all at Penguicon 3.0 perl -e 'print(map(chr,(0x4a,0x41,0x50,0x48,0xa)))'	[reply]
Re^2: Greatest programming mistakes and what to learn from by michaeld (Monk) on Dec 23, 2004 at 08:16 UTC
J. I can so completely relate to this type of situation... Sigh Cheers, MichaelD	[reply]