Log in

No account? Create an account
Andrei in the office


Andrei's Universe

One man's journey from infinity to nothingness

Previous Entry Share Flag Next Entry
Andrei in the office

Idiotic programming move 35b

I realize most of you aren't programmers, but this is Moron-move 35b

You have a function like this:

Do something cool {
    Do something boring
    Do something very complicated all at once in a very convuluted manner
    Display the cool results

Well, it doesn't quite work the way you want so you do the following.
    You cut the really complicated stuff out and paste it into

Do something very complicated in a better manner {
    // And lots of steps here.

You run it... Several times. You tell the computer to stop running when it gets to the new code. It never works. Hey it never even seems to get there.

See moron-move 35b is that you've cut the bad code, made a new function call, and forgot to tell the place where the old code was to actually call the new code.

Anyone else want to fess up to having done this?

  • 1
"why can't the compiler find this goddamned function?!?!"


"oh. because i created a new .c file, but forgot to include the dependency in my makefile."

similar, i think. :)

Yep, that's the one (or even F77 loader directives...same difference).

I spent a good half a day making changes to a DLL I was working on and couldn't figure out why none of the changes would work and why the source debugger wasn't in sync with the source.

I kept forgetting to copy the DLL over to the test exe's directory. I even had a cmd file to copy and run the debugger. I just kept forgetting to use it.

I think I usually catch it before it's live. Usually.



Nope. No, I've never ever done anything like that. Oh, no. Never.


I've done such things many many times... and worse...

  • 1