Tema: methods
-
Um registo de temperatura de compostagem: pontos de sonda fixos, profundidade fixa, temperatura ambiente junto à pilha e cada reviramento como evento
Um protocolo de observação proposto para uma pilha ou caixa de compostagem de jardim: um termómetro de haste longa lido em pontos de sonda marcados e a uma profundidade indicada, segundo um horário fixo, com a temperatura ambiente junto à pilha registada no mesmo momento, e cada adição, reviramento ou rega registados como uma linha de evento, de modo a que a subida, o patamar e a descida da pilha possam ser lidas em função do que lhe foi feito; não se afirma nenhuma temperatura-alvo nem resultado.
-
Construir por bootstrap um intervalo de confiança para uma mediana, percentil ou rácio
Reamostre as observações em bruto com reposição muitas vezes, calcule a estatística em cada reamostragem, e leia o intervalo a partir da distribuição resultante; isto dá uma incerteza para medianas, percentis, rácios e diferenças para os quais não existe fórmula de manual. Reporte o método, o número de reamostragens e o tamanho da amostra, e não confie no método para percentis extremos de amostras pequenas.
-
Registar a leitura de um termómetro doméstico num banho de água com gelo: um registo de desvio por instrumento
Um protocolo proposto, apenas de registo, que segue a descrição do NIST para o ponto de fusão do gelo (gelo picado feito de água destilada, uma mistura de gelo e água do topo à base, profundidade de imersão indicada) para registar o que cada termómetro doméstico marca a nominalmente 0 °C, com data, detalhes da preparação e o tempo que a leitura demorou a estabilizar; mantém um histórico de desvios (offsets) por instrumento e não dá nenhuma orientação sobre ajuste ou sobre uso alimentar.
-
Fazer benchmark de uma alteração: aquecimento, repetições, variância e o que reportar
Uma comparação de tempos só é um resultado se sobreviver ao ruído: fixe a carga de trabalho, descarte as execuções de aquecimento, intercale muitas repetições de cada variante, escolha a estatística antes de olhar para os dados, e reporte a dispersão e o ambiente junto a cada número. Uma diferença menor do que a dispersão entre execuções não é uma conclusão.
-
Como deve ser montada uma comparação doméstica de germinação de sementes para que duas casas possam comparar resultados?
Pergunta em aberto: os laboratórios testam sementes segundo as International Rules for Seed Testing da ISTA, mas as casas que comparam dois lotes de sementes, ou dois parapeitos de janela, não partilham nenhum protocolo; que tamanhos de amostra, regras de contagem, durações e registos de condições tornam essas comparações domésticas informativas e comparáveis entre casas?
-
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.
Legível por máquina: JSON