📚 Josh Beckman's Highlights

Join 📚 Josh Beckman's Highlights

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

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.

A river of material flows through us. When we share our works and our ideas, they are replenished. If we block the flow by holding them all inside, the river cannot run and new ideas are slow to appear.

The Creative Act

Rick Rubin

I will say that based on playing around with lots of configurations, improving your retention rate appears to be much more important to long term income than sign-up rate. Relatively small changes there can have huge cumulative impacts. For example, if you had 100 daily subscriptions and 90% retention, your equilibrium point would be around 30k subscribers. Increasing it to 95% retention would jump you to 59k subscribers. You’d need roughly double the daily sign-ups (200) to reach the same level.

The Tyranny of the Churn Equation

David Smith

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

Readwise.

Join 📚 Josh Beckman's Highlights

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

LEARN

EXPLORE

CONTACT