Join 📚 Josh Beckman's Highlights

A batch of the best highlights from what Josh's read, .

Nick Rowe memorably described [finance as magic](http://worthwhile.typepad.com/worthwhile_canadian_initi/2010/01/finance-as-magic.html). The analogy I would choose is finance as placebo. Financial systems are sugar pills by which we collectively embolden ourselves to bear economic risk. As with any good placebo, we must never understand that it is just a bit of sugar. We must believe the concoction we are taking to be the product of brilliant science, the details of which we could never understand. The financial placebo peddlers make it so.

Why Is Finance So Complex?

Nick Rowe

One of the most common mistakes when starting with Domain Events and with DDD in general is to not go the whole way and figure our what is actually going on in the domain. It is easy to fall into the trap of naming all events SomethingCreated, SomethingUpdated and SomethingDeleted. While not a problem in itself it does not make use of the powerful thing we get by adding the context and meaning to the actual change that the Domain Event represent. You lose the intent of the event and reading the event log later will not provide that much value.

What Are Domain Events? | DDD | Serialized

serialized.io

When adding jitter to scheduled work, we do not select the jitter on each host randomly. Instead, we use a consistent method that produces the same number every time on the same host. This way, if there is a service being overloaded, or a race condition, it happens the same way in a pattern. We humans are good at identifying patterns, and we're more likely to determine the root cause. Using a random method ensures that if a resource is being overwhelmed, it only happens - well, at random. This makes troubleshooting much more difficult.

Timeouts, Retries, and Backoff With Jitter

Amazon Web Services, Inc.

...catch up on these, and many more highlights