Don’t test in production.
this post was submitted on 03 Oct 2025
30 points (100.0% liked)
History Memes
655 readers
807 users here now
A place to share history memes!
Rules:
-
No sexism, racism, homophobia, transphobia, assorted bigotry, etc.
-
No fascism, atrocity denial or apologia, etc.
-
Tag NSFW pics as NSFW.
-
Follow all Piefed.social rules.
Banner courtesy of @setsneedtofeed@lemmy.world
founded 4 months ago
MODERATORS
Everybody has a test environment.
Some are lucky enough to also have a production environment.
Wondering as a non coder, can something like that happen with modern languages?
When I learned some C++ back in the day I remember my code not working because I forgot a = in a == statement. But then it just didn’t compile and was unusable until I discovered it.
In C/C++:
int a = 3;
if (a = 4) { printf("four");}
if (a == 3) { printf("three");}
Will yield four.
Back then, it would written in assembly which is has basically no compilations rules other than be translated to machine code. So it will do litterally what you tell it to do.
If you call the wrong variable, anything is possible.
I always fuck up some mundane detail!