A code deserves a thousand errors :)

Question

Just like how every picture deserves a thousand words to describe it, every program deserves to have a thousand errors when compiled. 😁

Answer 1

You write a program in C.

You attempt to compile, and it gives 329 errors. You look through the code, and you find that you were dividing a number by zero. So you fix that and move on.

You attempt to compile, and it gives 311 errors. You find that you accidentally assigned one of your pointers some impossible value. So you reset that to a regular address and continue.

You attempt to compile, and you get no errors. You wonder what's wrong with this picture, so you run through the program... and it segfaults.

You reset the variable again, and you perform some error checking to make sure that it's the address you want. So you compile again, 448 errors. Your compiler informs you that it actually never found any errors - it just likes throwing error messages at you. Your program compiled just fine.

You sit back and contemplate this for a moment. Your compiler has been messing with you your whole career. Now you realize it's just messing with you for fun. Because your compiler loves watching your face twist in agony every time your program compiles incorrectly. You find yourself instinctively writing input to your program. Everything makes sense now. You equate your compiler to a cosmic force, destined to see you fail... and yet you find an odd beauty in that. You know you're not in control of the universe, and the scale of this whole process is dizzying. You're not in control of the program - the program is in control of you.

Then you snap back to reality, and your program segfaults. *sigh*

Answer 2

And that's also when you start wondering why you ever chose this career... So that's why there are so few programmers. I wonder where they all go...