主题: 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