Join 📚 Josh Beckman's Highlights
A batch of the best highlights from what Josh's read, .
I’d argue that field-level encryption should be a starting place for new application development, and in particular field-level encryption with distinct keys for each entity you might contract with (e.g. each business for a business-to-business product, each user for a consumer product).
A Brief Rant on Converging Compliance Regimes.
lethain.com
Instead, it’s much better to wrap your patch in a module and apply it using Module#prepend. Doing so leaves you free to call the original implementation, and a quick call to Module#ancestors will show the patch in the inheritance hierarchy so it’s easier to find if things go wrong.
Finally, a simple prepend statement is easy to comment out if you need to disable the patch for some reason.
Responsible Monkeypatching in Ruby | AppSignal Blog
blog.appsignal.com
A distributed system can be described as a particular sequential state machine that is implemented with a network of processors. The ability to totally order the input requests leads immediately to an algorithm to implement an arbitrary state machine by a network of processors, and hence to implement any distributed system.
Time, Clocks and the Ordering of Events in a Distributed System
Leslie Lamport
...catch up on these, and many more highlights
Readwise