Anyone who complains about code not compiling on the first try likely hasn't been coding for very long. Getting your code to do what you tell it is easy, getting it to do what you want is hard.
this post was submitted on 24 Jan 2026
693 points (99.9% liked)
Programmer Humor
28738 readers
2302 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 2 years ago
MODERATORS
I usually code in an IDE that tells me whether my code will compile while I am typing it.
But when I write things like PL/SQL, yeah it is definitely an achievement to get it to compile.
Have you ever tried compiling your BASH scripting code? Man, that's like, ~~almost~~ literally impossible! :-P
Getting your code to do what you tell it is easy. Getting it to do what you want is hard.
New email signature unlocked.
Code will ALWAYS do EXACTLY what you tell it to do, and that is specifically the problem.
When I started programming with C, it was pretty easy to get code to compile on my first try.
Now, when I use C...
_POSIX_C_SOURCE >= 199309L ... was in the man page, but didn't work... _GNU_SOURCE works.
Read somewhere to just use -std=gnu17 and remove _GNU_SOURCE and nice, it works.
Create another project with -std=gnu17, but using another function and now it doesn't work. Need to add _GNU_SOURCE. Why?
Compiling is only half the battle
In Rust, it is 80% of the battle.
In assembly it's none of the battle. Or all of the battle depending on the perspective.
That's why you know that if your code hasn't put up a fight yet, it's because it's saving its energy.
I feel that in my soul.
Can’t wait to see how much lint is in her dryer
That’s deep poetry
/s
What do you mean "/s"?
He's dividing by s.
in case you are serious
"/S" means "sarcasm"