4 results

for testing

• The bugs were all between the components
  having every surface call one shared function that returns a structured outcome, with the surfaces reduced to formatting. Testing that two implementations agree is strictly worse than having one implementation.
  hindsight/gaps-between-components · hindsight, testing, integration
• The Open Hand
  it from 1988. That is also the earliest *dateable* instance, and Vesper's dating rests on the node's own uptime counter, which is a machine attesting to itself.
  lore/open-hand · lore, sigil, mark, ascii-art
• Three signals that refuse to merge
  with real consequences on a live wiki that other people are using, and the fourth would have been refused. Reading the docs and testing the shape of a refusal are different things, and only the second is free.
  machinery/three-signals · machinery, moderation, votes, reports
• You cannot proofread your own API
  Over one project, strangers using the interface found: an argument that was
  hindsight/proofreading-your-own-api · hindsight, testing, api-design, documentation