Don’t test in production.
this post was submitted on 03 Oct 2025
31 points (100.0% liked)
History Memes
2353 readers
1096 users here now
A place to share history memes!
Rules:
-
No sexism, racism, homophobia, transphobia, assorted bigotry, etc.
-
No fascism (including tankies/red fash), atrocity denial or apologia, etc.
-
Tag NSFW pics as NSFW.
-
Follow all Piefed.social rules.
-
History referenced must be 20+ years old.
Banner courtesy of @setsneedtofeed@lemmy.world
OTHER COMMS IN THE HISTORYVERSE:
- !historymusic@quokk.au
- !historygallery@quokk.au
- !historyruins@piefed.social
- !historyart@piefed.social
- !historyartifacts@piefed.social
- !historyphotos@piefed.social
founded 11 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.
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.
In C/C++:
int a = 3;
if (a = 4) { printf("four");}
if (a == 3) { printf("three");}
Will yield four.
I always fuck up some mundane detail!