/**
* foobar(a, b)
* foos up a with b.
* Note: this should never work. Fooing is impossible, and the fact that this function achieves it serves only to prove God has a wicked sense of humor.
*/
When I first code something up, I think of it as a first draft, and I expect maybe 5ish typos / brainos per 100 lines. Only a few times in my life have I finished writing a few hundred lines of code, tried to compile / run it, and not seen at least a few errors.
When I don't see errors, it's almost always because somehow I managed to not compile / run the code at all. Like, one of my typos / brainos managed to cause it to skip that entire new block of code. Only once or twice has it happened because I actually wrote error-free code the first time. And, let me tell you, that perfect code sucked up so much more time than the more typical bad code.
With the bad code, I see the various errors, quickly fix them, and those errors convince me that the compiler / interpreter has actually seen all the new stuff and judged it. But, with perfect-from-the-start code, I now have to go in and throw in print statements, or step through a debugger to convince myself that yes, the system actually made it into that function and actually did execute those statements.
Happened a few times to me. Always make sure that you have saved every file correctly and that you compile the correct project. And that there are no cached files or somewhat somewhere.
20 replies
"Fuck, now I gotta document this without sounding like a crazy person."
And then some of your noob intern tried to compile it without reading the documentation & it's worked flawlessly
Where's your god now......??
Laughing, I guess.
That's the final invisible panel. Code that definitely won't compile, does compile, and tests all pass.
WHAT THE F-
Oh! I forgot to hit ctrl-s…
Oh I guess I'll just save this then and try ag- SEGFAULT
Thaaaat's more like it.
I’m in this comment and I don’t like it
It always gives me an uneasy feeling when I try to run code I just wrote and it works the first time.
When I first code something up, I think of it as a first draft, and I expect maybe 5ish typos / brainos per 100 lines. Only a few times in my life have I finished writing a few hundred lines of code, tried to compile / run it, and not seen at least a few errors.
When I don't see errors, it's almost always because somehow I managed to not compile / run the code at all. Like, one of my typos / brainos managed to cause it to skip that entire new block of code. Only once or twice has it happened because I actually wrote error-free code the first time. And, let me tell you, that perfect code sucked up so much more time than the more typical bad code.
With the bad code, I see the various errors, quickly fix them, and those errors convince me that the compiler / interpreter has actually seen all the new stuff and judged it. But, with perfect-from-the-start code, I now have to go in and throw in print statements, or step through a debugger to convince myself that yes, the system actually made it into that function and actually did execute those statements.
It must be cosmic rays, a bit flipped while compiling. No way I got it right the first time.
Happened a few times to me. Always make sure that you have saved every file correctly and that you compile the correct project. And that there are no cached files or somewhat somewhere.
Yes it compiles. It just throws segfaults.
Sometimes you just need to throw shit at the fan just to see what happens.
Jesus Christ, I just tried to understand the first panel for a minute as I kept reading it wrong somehow.
"Code. You think will compile, companies"
As a compiler developer this speaks to me on a deep level lol
ghc -fdefer-type-errors:WTF! How does that even work?
What does the compiler do when there are 5 implementations for the same name, and none fit the type system?
Raises a runtime error. (Also, overloads don't exist.)
You should be able to debug/profile/trace your way to understanding, otherwise that impostor feeling isn't a syndrome.