Windows and non-functioning Path environment variables. Name a more iconic duo.

Just my $.02:

One thing I think a lot of students/schools miss when learning/teaching, is that your code has to be *maintainable*. Your code is (hopefully) going to be used for a long time, so program it to make it not only easy to upgrade and maintain, but easy for SOMEONE ELSE to upgrade and maintain, too.

The best code to work with is the stuff that's been coded with maintainability in mind.

There are two types of people in this world: those that comment their code, and FUCKING ASSHOLES

Introducing ArnoldC, a stack programming language based on Arnold Schwarzenegger phrases:

How can testing and debugging 10000 lines of uncommented, obfuscated code get worse?

Testing and debugging 10000 lines of uncommented, obfuscated code in visual studio.

So, I'm programming a control system for a prototype aerospace vehicle. You know, the stuff that needs to work to prevent falling out of the sky.

Anyway, test day was today (was -- not anymore). Wiring all the electronics, everything is actuating and works well. Except for one part, a little thruster for stability.

I spent hours - literally, fucking hours - trying to fix the problem. Wrong address? Wrong syntax? I had absolutely no clue what was wrong. Queue the hardware guy, $stupid:

$stupid: "How have you not got it working yet?!"

$me: "I don't know, everything I'm trying isn't working. I've spent hours digging through this code and nothing is fucking working."

$stupid: "Well have you set it up for the new thruster?"

$me: "What...What new thruster?"

$stupid: "Oh, the one we installed this morning, did noone tell you?"

WHY WOULDN'T YOU TELL ME THIS?! COMMUNICATION 101!