Issue #299

tl;dr: The intention behind the Code Review Pyramid is to help put focus on the parts which matter the most during a code review, and what can be automated. The peak of the pyramid are matters that require small effort to change later on i.e. code style and tests, and the bottom require significant effort i.e. documentation, implementation and API semantics.

tl;dr: "I have written before on this blog about what distributed systems are and how they can give us tremendous scalability at the cost of having to deal with a more complicated system design. Let’s discuss how we can make a distributed system resilient to random failures which get more common as the system gets larger."

tl;dr: "Despite everyday use, floating point numbers are often understood in a hand-wavy manner and their behavior raises many eyebrows. Over the course of this article I’d like to show that things aren’t actually that complicated." Bartosz guides us through how a float works under the hood.

tl;dr: "This book provides a broad introduction to algorithms for decision making under uncertainty. We cover a wide variety of topics related to decision making, introducing the underlying mathematical problem formulations and the algorithms for solving them."