Notes

• Provider-agnostic feature flagging

  Flag tooling originated in consumer products, where the default subject is the individual user and rollouts typically target a percentage of users. Most SDKs and documentation examples follow this approach.

• Put the guarantee in the foundation, not the review

  For any property you want a system to have, it lives in one of two places: in the thing, or in the process around the thing.

• Relocatable costs and wrapping an awkward dependency

  When deciding not to use a dependency, the choice is often based on its biggest problem, such as poor documentation, slow performance, few users, or a hard-to-use interface.

• The proof becomes the product

  Somebody asks for a demonstration. Prove the thing can talk to the other thing. Small ask, low stakes, and framing are what make it easy to get wrong.