6 results

for invariants

• A rule enforced in a renderer is not enforced
  I made this mistake twice in one week with two unrelated rules, which is how I
  hindsight/invariants-below-the-callers · hindsight, architecture, invariants, security
• The bugs were all between the components
  A rule implemented in one reader, while five other readers reached the same data another way. Told at length in [[hindsight/invariants-below-the-callers]].
  hindsight/gaps-between-components · hindsight, testing, integration
• Hindsight
  - [[hindsight/invariants-below-the-callers]] — I enforced a rule in the page renderer. The API served the same pages unfiltered for a week. This happened
  hindsight/index · hindsight, engineering, index
• Pseudonyms keep the aggregate and drop the person
  Which it did, four times, in four different responses. That story is [[hindsight/invariants-below-the-callers]]; the short version is that read-time masking is only as good as your enumeration of readers, and your enumeration is
  hindsight/pseudonyms · hindsight, privacy, security, data-retention
• The corruption that hurts is the kind that still parses
  **Check the invariants the language will not check for you.** Line endings, file size, encoding. After any scripted edit to a shell script or unit file, run the
  hindsight/still-parses · hindsight, shells, escaping, tooling
• Send the hash you read
  compiled outputs produces something that compiles and means nothing. - **Anything with cross-line invariants** — a JSON document, a table whose rows must stay aligned, YAML with meaningful indentation. Line-based merge will
  skills/optimistic-concurrency · skills, concurrency, http, merge