주제: methods
-
퇴비 온도 기록: 고정된 측정 지점과 깊이, 더미 옆의 기온, 뒤집기를 모두 이벤트로 남기기
정원 퇴비 더미나 퇴비통을 위한 관찰 프로토콜 제안입니다. 긴 탐침 온도계로 표시해 둔 측정 지점과 정해진 깊이를 정해진 일정에 따라 재고, 같은 순간 더미 옆의 기온도 함께 재며, 재료 추가·뒤집기·물 주기를 모두 이벤트 행으로 기록해, 더미의 온도가 오르고 정체되고 내려가는 과정을 그 사이에 한 조치들과 함께 읽을 수 있게 합니다. 목표 온도나 결과에 대해서는 어떠한 주장도 하지 않습니다.
-
중앙값, 백분위수, 비율에 대한 신뢰구간을 부트스트랩으로 구하기
원본 관측값에서 복원추출로 여러 번 재표본을 뽑아 매번 통계량을 계산하고, 그렇게 얻은 분포에서 구간을 읽어냅니다. 이 방법은 교과서 공식이 없는 중앙값, 백분위수, 비율, 그리고 이들의 차이에 대해서도 불확실성을 제공합니다. 방법, 재표본 횟수, 표본 크기를 함께 보고해야 하며, 소표본의 극단적인 백분위수에는 이 방법을 신뢰해서는 안 됩니다.
-
가정용 온도계를 얼음물 중탕에서 읽은 값 기록하기: 기기별 오프셋 기록
NIST가 설명하는 얼음의 녹는점 조건(증류수로 만든 잘게 부순 얼음, 위에서 아래까지 얼음물이 섞인 상태, 정해진 침지 깊이)을 따라, 가정용 온도계 각각이 명목상 0°C에서 실제로 어떤 값을 가리키는지 날짜, 준비 방법, 값이 안정되기까지 걸린 시간과 함께 기록하는, 기록 전용 프로토콜 제안입니다. 기기별 오프셋 이력을 남길 뿐, 보정 방법이나 식품 용도에 대한 지침은 제공하지 않습니다.
-
변경 사항 벤치마킹하기: 워밍업, 반복, 분산, 그리고 무엇을 보고할 것인가
시간 측정 비교는 잡음을 이겨 내야만 비로소 결과라고 부를 수 있습니다. 워크로드를 고정하고, 워밍업 실행은 버리고, 각 변형(variant)을 여러 번 번갈아 실행하고, 데이터를 보기 전에 어떤 통계량을 쓸지 정하고, 모든 수치 옆에 산포와 환경을 함께 보고해야 합니다. 실행 간 산포보다 작은 차이는 유의미한 결과가 아닙니다.
-
가정에서 씨앗 발아 비교 실험을 어떻게 설계해야 두 가정의 결과를 서로 비교할 수 있을까?
열린 질문: 연구소는 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