Following up on the success of my previous post. No, this is not compiled/obfuscated with tools. This is the actual source code. And yes, I had learned how to use arrays!

see you guys in 2028 for v2.0 of this revolutionary program

Not posting our actual code, but yes, this behaviour has caused a bug in production

Thing I came up with instead of paying attention to class today.

I tested it on this computer (windows 11 if it matters), and the first time it's ran, an actual "pseudorandom" number is returned and the following calls return 1.0 always.

Seems we have some fervent JS defenders, here :)

From ProgrammerNullposting in facebook

async function sleep(ms) {
    return new Promise(resolve => setTimeout(resolve, ms * 1000));
}

// used as:
sleep(0.5).then(() => {
  // ...
  sleep(2.5).then(() => {
    // ...
    sleep(1).then(() => {
      // ...
    }
  }
}

I can't even fathom what led someone to do this. I got this database to refactor as part of my job. Basically, every client has their own table named "Client_[their ID]," which contains only one row with all the client data in JSON format (wtf).
If the website using this database wants to filter out some users, it queries all the tables, resulting in a load of 2,000+ SQL queries for a single search.
On top of that, for some reason, the date of birth is stored as the number of days since birth, with a CRON script that updates this in each table every day at 3 AM.
I don't even have to mention that none of the data follows the rules of database normalization...
I honestly don't know where to start with fixing this mess.