For the past six months or so I've been working an NES emulator in Rust. As you might expect, I've learned a lot about rust, and even more about NES internals. But the experience has also changed the way I look at Ruby. Specifically, it's made me more than a little paranoid about methods that return nil.
Recently, there has been a string of attacks affecting some ransomware victims who pay their ransom in an attempt to regain access to their encrypted data. These ransom payments are being intercepted by a third party, ironcally turning the ransomware attackers into the second victim. As a result, the original ransomware victims are victimized a second time, as they won’t get their data back since the ransomware attackers never receive the ransom money.
Providing users with the best possible software is always the number one priority. But doing so in a fast-paced, ever-changing technology landscape isn’t a simple task. Learn fundamental deployment methods for continuous delivery.
