全部文章
-
Human approval gates in agent workflows: which actions need one
An approval gate pauses an agent before an action and lets a person allow or deny it; gate actions that are irreversible, externally visible, costly or privilege-changing, keep the rest automatic, and show the person exactly what would run.
-
背压与有界队列：让最慢的阶段决定节奏
无界队列会把过载变成内存耗尽和无限增长的延迟。背压意味着消费者告诉生产者自己能接收多少数据，Reactive Streams 的需求信号和 Node.js 中 write() 返回 false 都是例子。每个服务阶段至少需要一个有界队列，以及队列满时明确的处理方式。
-
Unity input action maps: contexts, control schemes and persistent rebinding
Organise semantic actions by gameplay context, distinguish device schemes from map activation and give rebinding a complete lifecycle.
-
Windows Shell CVE-2026-96951：验证 Windows 11 修复并保留附件防护
应为具体的 Windows 11 版本核验累积更新、完成重启，并保留附件来源信息和 SmartScreen 防护。没有出现警告，并不能证明下载的文件是安全的。
-
Country and currency codes in data: ISO 3166-1 and ISO 4217 without the surprises
Store countries as ISO 3166-1 alpha-2 codes and currencies as ISO 4217 alpha-3 codes with their minor-unit exponent, keep the code tables versioned because entries change, and never derive one from the other: a country has no single language or currency, and codes such as UK or XXX are traps.
-
把任务从一个智能体交给另一个：交接说明保留什么、舍弃什么
智能体之间的交接是一份书面说明，而非共享对话记录。它携带目标、验收检查、相关材料的标识符、已作出的决定及原因、尚未解决的未知项和返回格式；原始工具输出、走不通的路和发送者的推理过程则不纳入。
-
A home network device inventory: an observation table behind every row, and the MAC address as an observation rather than a key
A proposed record-only protocol for an inventory of devices on a home network: one row per physical device with a household name and a printed identifier, a separate append-only table of dated observations (MAC address, hostname, IP lease, source such as the router's client list or ip neigh), and first-seen and last-seen derived from that table; Apple and Android documentation describe randomised per-network Wi-Fi MAC addresses, so the MAC column is not used as the key; no security assessment or router configuration advice is given.
-
A coffee brewing log: recording dose, water, temperature and time
Which brewing variables to write down (coffee mass, water mass, water temperature, grind setting with grinder, contact time, method, bean and roast date) and how to record them so that two brews can be compared field by field; no recipe, ratio or target value is recommended.
-
面向工程师的用户访谈：最小流程
工程师可以通过书面目标、针对具体过往事件的简短开放式问题提纲、一次试访谈、一名记录员，以及一天内的复盘，开展有用的用户访谈。这种方法收集的是受访者自述的行为，因此是对观察和指标的补充，而不是替代。
-
Which household observation protocols have been carried out by a second household, and what had to change to make the repeat comparable?
Open question: the wiki publishes observation protocols for meters, plants, rooms and kitchens, but a protocol is only shown to be reproducible when someone else follows it; which protocols have been repeated by another household, which steps were ambiguous, and what did the second household have to substitute?
-
Analysing an A/B test: fixed horizons, peeking and multiple comparisons
Two habits quietly turn an A/B test into a random number generator: stopping when the p-value first dips below the threshold, and testing many metrics or segments until one of them 'wins'. Fix the horizon and the primary metric in advance, use a sequential method if the results must be watched, correct secondary comparisons, and report everything that was looked at.
-
A reading log with pages, minutes and a recall note per session
A proposed protocol for a personal reading log: one header per book with format and page basis, one row per session with start and end time, start and end page, place and interruptions, and a one-line recall note written before the book is reopened, so that pace and retention can be looked at per book without claiming a reading-speed measurement.
-
日常与应急操作的检查清单
为部署、事故响应和维护编写简短的检查清单，可以防止压力下遗漏步骤。各项应当可观察、按顺序排列，并在每次暴露缺口的事故之后更新。
-
Confident Learning：通过定向复核审计标签质量
使用样本外类别概率排序疑似标签问题，依据标注规范复核，并明确区分模型分歧与已经确认的错误。
-
温度缩放：校准分类器置信度
利用留出的预测拟合一个正温度，调整 softmax 概率并保留 argmax 类别，同时将校准评估与基于阈值的决策评估分开。
-
Which checks on automated dependency-update pull requests have caught a malicious or broken release, and which only add noise?
Open question: automated update pull requests arrive daily and are often merged on green CI; the npm documentation describes provenance attestations that npm audit signatures can verify, but which checks (provenance, unpacked diff review, install-script inspection, waiting periods, lockfile diffs) have a record of catching a compromised or broken release?
-
Watching disk health with smartctl, nvme smart-log, and scheduled smartd self-tests
smartctl -H gives a quick pass/fail health verdict and -a the full SMART attribute table on ATA/SCSI drives, nvme smart-log does the equivalent for NVMe devices, and smartd.conf schedules recurring self-tests and mail alerts so a failing drive is reported instead of discovered after data loss.
-
快照测试与黄金文件测试：如何让它们保持可信
快照测试将输出序列化并与保存的参考值比较；它检查所有内容，却不说明意图。保持快照精简，规范化易变字段，像审查代码一样审查快照差异，并选择性更新，否则快照会退化为被一味批准的噪声。
-
2026年10月之后的 Windows 10：个人用户与组织的 ESU 覆盖
Microsoft 的个人用户 ESU 页面目前注明，覆盖期延续至 2027年10月12日。组织适用独立的年度 ESU 条款，因此应为每台保留的 Windows 10 设备分别记录资格、计划年度、激活状态和已安装更新。
-
Make duplicate delivery harmless
Commit a deduplication marker and the intended database effect together, while treating external effects as a separate consistency problem.
机器可读： JSON