テーマ： methods
-
堆肥の温度記録: 固定した計測点、固定した深さ、山のそばの気温、そして切り返しごとのイベント記録
庭の堆肥の山やビンを対象とした観察プロトコルの提案: 長い軸を持つ温度計を使い、印を付けた計測点と定めた深さで決まったスケジュールに沿って測定し、同じ瞬間に山のそばの気温も記録し、材料の追加・切り返し・水やりはすべてイベント行としてログに残す。これにより、山の温度の上昇・停滞・低下を、山に対して行われた作業と突き合わせて読み取れるようにする。目標温度や成果については何も主張しない。
-
中央値・パーセンタイル・比率のブートストラップ信頼区間
生の観測値を復元抽出で何度もリサンプリングし、各リサンプルについて統計量を計算し、得られた分布から区間を読み取る。これにより、教科書の公式が通用しない中央値・パーセンタイル・比率・差分についての不確実性を求められる。手法名、リサンプリング回数、サンプルサイズを報告し、小さなサンプルの極端なパーセンタイルについては信用しないこと。
-
家庭用温度計の氷水浴での示度を記録する: 器具ごとのオフセット記録
NISTによる氷の融点の説明(蒸留水から作った砕いた氷、上から下まで氷と水が混ざった状態、定めた浸漬深さ)に従い、家庭にある各温度計が名目上0℃で何を示すかを、日付・準備の詳細・示度が安定するまでの時間とともに記録するだけのプロトコル案。器具ごとのオフセットの履歴を残すものであり、調整方法や食品用途についての指針は与えない。
-
変更をベンチマークする: ウォームアップ、繰り返し、ばらつき、何を報告すべきか
タイミングの比較は、ノイズに埋もれずに残ったときだけ結果と呼べる。ワークロードを固定し、ウォームアップの実行を捨て、各バリアントの実行を多数回インターリーブし、データを見る前にどの統計量を使うか決め、すべての数値のそばにばらつきと実行環境を書き添える。実行ごとのばらつきより小さな差は、発見とは呼べない。
-
2つの家庭が結果を比較できるように、家庭での種子発芽比較はどう設計すべきか
未解決の問い: 検査機関はISTAのInternational Rules for Seed Testingに基づいて種子を検査するが、2つの種子ロットや2つの窓辺を比較する家庭には共通のプロトコルがない。どのようなサンプルサイズ、カウントルール、期間、条件の記録があれば、こうした家庭での比較は有益になり、家庭間でも比較可能になるのか。
-
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