proomt

Search

Search posts, papers, and topics

All posts

Hacker News front pageDeric Tilson8 min readintermediate

Things that apparently cause cancer

Summary

Harvard epidemiologists used a distance‑based “proximity score” to link nearby nuclear plants to cancer deaths, but the method ignores actual exposure and produces absurd attributions for unrelated landmarks like Costco and sports stadiums. A replication by the author shows the approach yields positive results for any site, highlighting that such ecological analyses can generate precise nonsense…

  • Proximity‑based exposure scores can produce spurious cancer attribution for any landmark.
  • Replication shows the methodology yields positive results for unrelated sites such as Costco and stadiums.
  • The studies lack true exposure measurement, proper controls, and placebo tests, invalidating causal claims.
  • Large radii (up to 200 km) are unsuitable for detecting radiation effects that are orders of magnitude smaller.

Engineers building data pipelines or statistical tools must recognize the limits of ecological analyses to avoid producing misleading, policy‑impacting results.

6/10

Related reading

  1. RADAR: Catch gray failures with anomaly detection

    Databricks built RADAR, a four‑stage, metric‑agnostic pipeline that uses streaming anomaly detection (SPOT) to surface gray failures in minutes with >90% precision. The blog shows how to recreate the system on Databricks for any metric, from billing to model drift.

    Databricksdatabricks.com7 min
  2. How we tracked down a 16-year-old SQLite bug

    Tailscale experienced 19 SQLite database corruptions over six months due to a 16‑year‑old bug in SQLite’s WAL checkpoint logic. The single‑writer, Go‑driven shard architecture forced them to add forensic telemetry, a transaction‑logging replay pipeline, and work directly with SQLite core developers to isolate and fix the issue, dramatically reducing downtime.

    Tailscaletailscale.com14 minpostmortemHN1223239
  3. Simple Testing Can Prevent Most Critical Failures

    A study of 198 production failures in distributed systems (Cassandra, HDFS, etc.) found that 92% of catastrophic outages stemmed from incorrect handling of non-fatal errors. Over half of these could have been prevented by simple testing of error handling code, even without deep system understanding.

    Hall of Fameusenix.org58 minpaperHN4
  4. Postmortem Culture: Learning from Failure

    Google SRE advocates for a blameless postmortem culture to learn from inevitable incidents in complex distributed systems. Postmortems document incidents, identify root causes, and drive preventive actions, focusing on systemic improvements rather than individual blame.

    Hall of Famesre.google9 minHN2
  5. Big Ball of Mud

    The paper defines the "Big Ball of Mud" anti‑pattern—systems that grow haphazardly due to expedient fixes—and outlines seven related patterns that explain why they arise and how to mitigate or reverse them.

    Hall of Famelaputan.org74 minpaperHN14231