// Do not delete! Yes, it's not used anywhere in the code, but if it is removed
// the application crashes and the error code is useless for debugging.
let f = 'a';
There was a function that wasn't called from anywhere in the project which if deleted caused the whole system to fail in test and (presumably) production at runtime. It turned out to be scripts for a cron job that were only on the servers. I moved them in to the project and thus version control. Mystery solved.
I once wrote C code for a hangman game. I took in a character and checked if it's matching with any of the hidden characters. Long story short I did not code what should happen when the user inputs more than 1 character, but during testing I realized that it just analyzes every chracter one by one, and if you input the same characters multiple times it would just ignore it ofc. Making it possible to type a single character, multiple if you wanna be risky. Or the whole word. I liked it better than if it would work on a "guess" basis because it was way more fun, so I kept it that way. Have no idea why it does what it did, but it works.
better example is & and * in Rust. If someone tells me they can get them good the first try, TEACH ME, or they are lying. When it works it judt works don't you dare touch them.
Just containerize the dev environment and ship that to the customer.
Just make sure to add comments like
To make sure no-one accidentally breaks the spell.
if ( "a" == "a" ) { // i swear i saw this somewhere }
I once did
const theNumber = 4in a function (and then took a second, actually random, number and compared it totheNumber).In the comment to the function I actually referenced https://xkcd.com/221/.
If you even know which line of random bullshit you changed that made it work, that is
//HERE BE DRAGONSI solved one of these once upon a time.
There was a function that wasn't called from anywhere in the project which if deleted caused the whole system to fail in test and (presumably) production at runtime. It turned out to be scripts for a cron job that were only on the servers. I moved them in to the project and thus version control. Mystery solved.
Well you can't call the code generated by chat gpt as YOURS.
these things happened before chatGPT tho.
I once wrote C code for a hangman game. I took in a character and checked if it's matching with any of the hidden characters. Long story short I did not code what should happen when the user inputs more than 1 character, but during testing I realized that it just analyzes every chracter one by one, and if you input the same characters multiple times it would just ignore it ofc. Making it possible to type a single character, multiple if you wanna be risky. Or the whole word. I liked it better than if it would work on a "guess" basis because it was way more fun, so I kept it that way. Have no idea why it does what it did, but it works.
better example is & and * in Rust. If someone tells me they can get them good the first try, TEACH ME, or they are lying. When it works it judt works don't you dare touch them.
I think you basically made a Wordle version of hangman by accident there, lol.
unexpected crossover
The way I see, if chatgpt can steal our art, then we can steal its science.
I know why it works. Because it was copied from stack overflow..
@fckreddit
Haha yeah so some other random dude made it work ๐
The answer is usually that I've pushed to the dev environment but I'm looking at staging.
Hi there! The links in your response are not clickable for Lemmy users, here are the clickable versions: ![email protected]
Going back to the most famous code comment in Unix history
You are not expected to understand this.@sin_free_for_00_days or "# The code is documentation enough"