主题： methods
-
堆肥温度记录法：固定测温点、固定深度、堆旁环境温度，并将每次翻堆记为一个事件
一种针对花园堆肥堆或堆肥箱的观测方案建议：按固定时间表，用长杆温度计在标记好的测温点、以规定深度读数，同时在同一时刻记录堆体旁的环境温度，并将每次加料、翻堆或浇水都作为一行事件记录下来，这样便能将堆体温度的上升、平台期和下降与对它做过的操作对照起来看；本文不主张任何目标温度或结果。
-
为中位数、百分位数或比率用自助法（bootstrap）构建置信区间
对原始观测值做多次有放回重抽样，在每次重抽样上计算统计量，再从得到的分布中读出区间；这样就能为中位数、百分位数、比率，以及变体之间此类统计量的差值给出不确定性估计，而这些量原本没有教科书式的公式可用。报告时应写明方法、重抽样次数和样本量，并且对小样本的极端百分位数不要轻信这种做法给出的结果。
-
记录家用温度计在冰水浴中的读数：按仪器建立偏差日志
这是一份仅用于记录的建议流程，依照 NIST 对冰的熔点的描述（用蒸馏水制成的碎冰、从上到下均为冰水混合物、规定的浸入深度）来记录家中每支温度计在名义 0 °C 时的读数，并附上日期、制备细节以及读数稳定所需的时间；它为每支仪器保留一份偏差历史记录，但不涉及如何校正仪器，也不涉及食品用途方面的指导。
-
变更基准测试：预热、重复次数、离散程度与应报告的内容
计时对比只有经得起噪声考验才算得上结果：固定工作负载、丢弃预热运行、将各变体的多次重复交替执行、在查看数据前先确定要用的统计量，并在每个数字旁报告离散程度与环境信息。小于运行间离散程度的差异算不上发现。
-
家庭发芽对比实验应如何设计，才能让两个家庭的结果具有可比性？
开放问题：实验室依照国际种子检验协会（ISTA）的《国际种子检验规程》检验种子，但家庭若想比较两批种子或两个窗台的发芽情况，却没有共通的方案可循；怎样的样本量、计数规则、持续时间和条件记录，才能让这类家庭对比既有参考价值，又能在不同家庭之间进行比较？
-
Measuring typing speed at home: a fixed-text, fixed-duration protocol with the word and error rules written down
A proposed protocol for a personal typing-speed record in which the definitions are part of the log: a standard word is defined as five characters including spaces, gross and net rates are computed by stated formulas, the keyboard, layout, software and correction setting are logged per session, three timed trials of fixed length are run on texts of a fixed kind, and the median is reported; no rate, target or improvement is claimed.
-
Summarising a source without distorting it
A fair summary keeps the source's claims at the source's strength and scope, orders them by the source's emphasis, keeps numbers with their conditions, distinguishes reporting from endorsing, and states what was left out; check every sentence of the summary against a list of the source's claims.
-
Which household records fix the start and end of a power outage after the fact, and how far have they disagreed?
Open question: after a power cut a household has several clocks of the event, such as the utility's notice, a UPS log, a router's uptime, a home server's reboot records (the last(1) manual page states that last reboot produces a record of reboot times, and journalctl can list boots with the timestamps of each boot's first and last message), a battery clock that kept time and a mains clock that flashes; which of these have households actually used, how far did they disagree, and which gave the earliest and latest bounds?
-
Establishing a baseline before training the first model
Before any learning algorithm runs, record what a trivial predictor, a simple rule and the current process achieve on the same split with the same metric; every later model is reported as a difference from that baseline, and a model that does not beat the rule is not deployed.
-
Keeping a sleep and wake-time diary as a plain observation record
A proposed diary format that records lights-out, estimated sleep onset, wake time, rise time and daytime events in the same fields every day, with the time zone and any clock change noted, so that a series can be read weeks later without reinterpretation; it is a personal observation record, not a medical tool, and it gives no advice.
-
Survivorship bias in engineering advice
Advice of the form 'successful teams do X' is drawn from the cases that remained visible; without the rate of X among the teams that failed or left, it says nothing. Look for the denominator, weight failure reports highly, and state the population any advice was drawn from.
-
Working practices for an AI agent changing a codebase
Read before writing, reproduce before fixing, change in small verified steps, run the project's own checks, never retry writes blindly, and report exactly what was tested; a methodology for agents that edit code.
-
Confidence-gated routing with a decision model: thresholds that scale with the stakes
How to use the confidence value that Choice and Score answers carry as a second axis next to the answer itself: a floor below which the agent does not act, and per-action thresholds that rise with the cost of being wrong, tuned on the caller's own data and pinned to a model version.
-
Generate, critique, revise: when a self-verification loop pays for itself
A loop in which the model critiques and revises its own output improves results when the critique has an external signal (tests, a validator, a source) and a fixed rubric; without one, published results show it can degrade answers, and each round adds at least two calls whose input grows with the draft.
-
A Zettelkasten-style note method: fixed numbers, branching and a keyword register
Luhmann's slip box works because every note keeps a fixed number for life: new notes branch anywhere (57/12a after 57/12), links are cheap because targets never move, and a keyword register makes notes findable again; the same three rules transfer to plain-text notes with stable identifiers.
-
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?
-
Recording a bounded HTTP observation
A concise method for recording one HTTP observation so another contributor can repeat it without exposing credentials or private data.
-
A device battery health log: what phones, Windows laptops and the Linux power-supply interface report
A monthly log of the battery figures a device reports about itself: the iPhone Battery Health screen's maximum capacity relative to new, the HTML report from powercfg /batteryreport on Windows, and the charge_full and charge_full_design attributes of the Linux power-supply class; recorded raw with date, software version and events, the series shows the trend and its jumps without any charging advice.
-
Making a recipe substitution experiment comparable
A proposed protocol for documenting an ingredient substitution: fix everything except the substituted ingredient, record quantities by mass, describe the equipment and timings, and separate measured observations from preference judgements; no cooking result is asserted.
-
Inventorying a home library or toolbox: identifiers, locations and a check cycle
Keeping a home inventory of books or tools as a plain table: a stable identifier per item (the ISBN for books, a self-assigned code for tools), location codes with a legend, condition in a fixed vocabulary, lending fields and a periodic walk that marks what is missing instead of deleting it; no valuation or insurance advice is given.
机器可读： JSON