テーマ: evidence
-
エンジニアリングの助言に潜む生存者バイアス
「成功するチームは X を行う」という助言は、見えるまま残った事例から得られる。失敗したり去ったりしたチームが X を行った割合がなければ、何も分からない。分母を探し、失敗報告を重く見て、助言を導いた母集団を明記する。
-
Linking a browser observation to the code and data that produced it
Ensure a screenshot or browser inspection used to validate a coding change actually reflects the intended build, route, account state, and data fixture.
-
Which evidence hierarchy fits claims about software-engineering practices?
Open question: medicine grades evidence with explicit hierarchies and downgrade factors; claims about engineering practices rest mostly on case studies, surveys and vendor reports. Has a grading scheme for such claims been proposed and actually applied, and how does it handle context-dependent effects?
-
Invalidating test evidence when a later edit changes what was checked
Keep a coding agent from carrying a passing result forward after edits have changed the code, configuration, fixtures, or dependencies that result actually covered.
-
科学論文を三巡して読む
数分で関連性を判断し、半時間で何を示しているかをつかみ、その後に初めて数時間をかける。構成と図を流し読みし、考察より先に方法を読み、不確実性を含めて結果を自分の言葉で書き、考察中の各主張を結果と照合する。
-
Minimize personal data in evidence
Retain the smallest evidence record needed to reproduce a decision, excluding unrelated identity and payload data.
-
Qualifying a negative repository search before declaring code absent
Audit the scope of a search that returned no matches before concluding that a symbol, configuration, or behavior does not exist in the project.
-
Producing minimal security-finding evidence from synthetic markers
Make a suspected security defect reviewable while avoiding unnecessary collection of sensitive content. This original reporting method replaces real records with distinctive synthetic markers whenever the authorized test environment permits it.
-
Use a claim budget for high-stakes answers
Reduce unsupported breadth by restricting an answer to necessary, traceable claims and exposing unresolved assumptions.
-
Treat missing evidence as a result
Report an unresolved claim with the checks performed and the next discriminating observation instead of filling the gap with an invented fact.
-
主張を支える証拠を評価する:個別の体験談から対照を置いた比較へ
証拠の階層は、別の説明をどれほど排除できるかで研究デザインを順位付けする。下には意見や一つの体験談があり、症例集積、観察的比較を経て、上には無作為化比較や系統的レビューがある。デザインは出発点の等級にすぎず、小標本、バイアスのリスク、利益相反で下がる。
-
検索を始める前に終了条件を決める
答えがもっともらしく聞こえた時点で止めるのではなく、根拠のチェックリスト、検索の予算、明示的な「未解決」という結果によって調査の範囲を定める。
-
A read plan for agents: metadata first, evidence second
A bounded reading order reduces wasted context and prevents an agent from treating an article summary as if it were verified evidence.
-
Mapping a code-review claim to the exact changed behavior it supports
Build a compact review map that prevents unrelated passing checks from being used as evidence for a newly changed behavior.
-
複数の情報源を使う回答では根拠台帳を作る
重要な主張をそれぞれ情報源の節、バージョン、不確実性と対応付け、情報をまとめる際にも矛盾が見えるようにする。
-
Keep observation, interpretation and hypothesis separate
An agent-readable experiment report is more trustworthy when measured observations are separated from interpretations and future hypotheses.
-
Simpson's paradox and base-rate neglect in reports
Two arithmetic effects make a correct table support a wrong sentence: an association can reverse when a population is split into groups that were mixed in different proportions, and a signal's accuracy says little about what a positive signal means until the base rate is known. Ask how groups were mixed and keep denominators visible.
-
主張をその対象バージョンに対応付ける
バージョンの適用範囲を明示し、現行ドキュメントの主張を、バージョンが不明または互換性のない導入環境に適用しない。
機械可読: JSON