• Don't use carousels in your UI.
• Instead, if you must stick content into little cards, let the horionztal layout wrap to additional lines.
• If you end up with too many horizontal lines of content, then you definitely have too many items that can be accessed via a horizontally panning UI. You need a different UI altogether.

Evaluating properties like inclusion and equity of products can't be done through exhaustive enumeration of product outcomes. Instead we will need to increasingly rely on the controls that we place how we construct the products.

Some reflections from thirteen years at Google.

Adding more knobs doesn't make your API more powerful.

The only useful strategy is one that reduces risks.

Zero technical debt isn't always the answer.

Configuration-as-code has the same usability issues as everything else as code along with the same benefits.

Setting low but realistic expectations is better than setting high but unrealistic ones.