this post was submitted on 20 May 2026
1091 points (99.8% liked)

Programmer Humor

31505 readers
2168 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

founded 2 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] Feathercrown@lemmy.world 9 points 1 day ago (2 children)

One of my coworkers is fond of using ternary expressions instead of "if" blocks. Even ones without an "else". So I see things like:

condition ? someVar = "blah" : null;

or

condition ? doSomething() : null

Which should both just use "if" statements. Or my favorite:

condition ? someVar = "foo" : someVar = "bar"

which should really be

someVar = condition ? "foo" : "bar"

[–] testaccount789@sh.itjust.works 4 points 1 day ago* (last edited 1 day ago) (2 children)

UUUuuuuuh, I am not a programmer (you're going to say "thank god"), but...

I sometimes even chain them. You can put yet another ternary operator in the else and keep going. You know, else-if.
So anyway, I can get ternary operators spanning 2 - 3 lines.
Oh, I also often have issues thinking of proper loops, so you'd see a few terribly used goto statements.

Although I do remove ones that are obvious brain fart.
For example, quite obvious

void example(bool true_or_false){
    if(true_or_false){
        //code if true
    }
    else{
        //code if false
    }
    //other code
}

Well, I've already had my brain goof up even that once or twice. "How the fuck", you're asking?

void example(bool true_or_false){
    if(true_or_false){
        goto if_true;
    }
    //code if false
    goto end_false_if;
if_true:
    //code if true
end_false_if:
    //other code
}

The brain-fart if-else.

[–] Feathercrown@lemmy.world 7 points 1 day ago

Dear lord lmao

[–] lukstru@piefed.social 2 points 1 day ago (1 children)

You need another goto end right before the end_false_if:, otherwise the false code will always run

[–] testaccount789@sh.itjust.works 2 points 21 hours ago (1 children)

I tested it, it works as it is.

#include <stdio.h>
#include <stdbool.h>

void main(){
        bool true_or_false = true;
        if(true_or_false){
                goto if_true;
        }
        printf("This code runs only if false.\n");
        goto end_false_if;
if_true:
        printf("This code runs only if true.\n");
end_false_if:
        printf("This code always runs.\n");
}

If true, it jumps to if_true, then runs other code. If false, the if gets skipped, if false code gets run, then it skips over if true code.

[–] lukstru@piefed.social 3 points 21 hours ago

I totally did the thing where I commented without reading properly before. Sorry!

[–] dbx12@programming.dev 4 points 1 day ago (1 children)

The last thing, that would be a "request changes" for me.

[–] Feathercrown@lemmy.world 3 points 1 day ago

I haven't seen him do it lately in any code I've reviewed but I do change it whenever I see it if I'm doing work nearby lol