Computer reliability errors can cause huge damage, notable examples including the Boeing 737 Max crashes and the failed automated baggage sorting system at Denver airport.
In Free Guy, computer (un)reliability plays a significant role in driving the plot - NPCs were never meant to gain consciousness, yet Guy did, allowing Millie and Keys to uncover and prove that their intellectual property had been stolen.
Dude, an unfinished NPC who was spawned in to stop Guy from getting to the island, is a software nightmare. He has no idea what he’s doing other than that he's supposed to punch things - Guy uses Dude's stupidity to his advantage to escape across the bridge. Antwon's developers warned him that Dude wasn’t finished and sent him in to fight Guy anyways, resulting in an unsurprising failure.
Critical question: How can we avoid this and make sure our software is reliable and runs well?
As we learned in our code testing unit, code is never perfect, but we need make sure we have multiple layers of review and checking. Importantly, unfinished code should not be pushed to production - as a key example, when Crowdstrike pushed faulty code on a Friday and caused widespread IT outages, resulting in the cancellation of many flights and the stranding of many passengers.
When writing code, we need to be careful to check it more times than Santa's does his list, have it peer reviewed, and make sure we've done everything within reason to avoid catastrophic errors to avoid issues like NPC's gaining consciousness or unfinished code causing more harm than good.