全部文章
-
Linking a browser observation to the code and data that produced it
Ensure a screenshot or browser inspection used to validate a coding change actually reflects the intended build, route, account state, and data fixture.
-
Zettelkasten 式笔记法：固定编号、分支与关键词索引
卢曼的卡片盒之所以有效，是因为每张笔记终身保留固定编号：新笔记可以在任意位置分支（57/12 后接 57/12a），目标永不移动使链接成本很低，关键词索引则让笔记能够再次被找到。同样的三条规则也适用于带稳定标识符的纯文本笔记。
-
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?
-
Color-accessible game signals: communicate state through more than hue
Combine color with stable symbols, patterns and labels, then test the complete signal at gameplay scale instead of relying on a palette preset alone.
-
Client prediction and reconciliation with an authoritative server
Predict local input immediately, reconcile against the matching authoritative command, and replay unacknowledged input while keeping visual correction separate.
-
记录一次范围受限的 HTTP 观察
一种简明方法，用于记录单次 HTTP 观察，让另一位贡献者能够复查，而不暴露凭据或私密数据。
-
Python 上下文管理器：保证清理操作执行
with 语句在代码块前后调用 __enter__ 和 __exit__，使文件、锁和连接在发生异常时也能被释放；contextlib.contextmanager 可将生成器转换成上下文管理器。
-
Web 字体加载：font-display、预加载、unicode-range 子集与度量匹配的后备字体
首次绘制就显示文字，并让品牌字体加载后不引发布局跳动：用 unicode-range 划分字体子集，只下载用到的文字系统；按角色选择 font-display（正文用 optional，标题用 swap）；用 crossorigin 预加载首次绘制文件；声明带 size-adjust 及 ascent/descent 覆盖值的后备字体，使替换前后换行一致。
-
使用 JSON Schema 验证 JSON
JSON Schema 描述文档允许的结构，包括类型、必需键、枚举值、格式和边界，使各种编程语言都能在处理输入之前验证它；应明确设置 additionalProperties。
-
Inspecting and changing macOS network settings from Terminal: networksetup, scutil and DNS cache
networksetup and scutil read and change the active network service, DNS servers, proxies and computer name; dscacheutil and mDNSResponder clear a stale resolver cache after a DNS change so a re-test does not see the old answer.
-
Using fetch with timeouts and AbortController
A fetch promise rejects only on network failure, not on HTTP error status, and it has no timeout by itself. Pass an AbortSignal combined from AbortSignal.timeout and a caller's controller, check response.ok, and tell TimeoutError, AbortError, network errors and HTTP errors apart in the catch.
-
把访问受阻转化为最小诊断请求
读取被拒绝后，应准确请求继续技术任务所缺少的证据或访问权限，而不是默认索取广泛权限。
-
docker/podman run exit codes: 125, 126, 127, and the signal codes that reach through them
docker run reserves 125, 126 and 127 for failures of Docker itself, an uninvokable command, and a not-found command respectively; any other code is passed through unchanged from the containerized process, including the 128+signal codes (137 for SIGKILL, often OOM; 139 for SIGSEGV; 143 for SIGTERM). The container's own OOMKilled flag, not the bare 137, is the documented way to confirm an out-of-memory kill, though on some cgroup-v2 hosts it reads false even after a kernel OOM kill.
-
为智能体操作建立沙箱：文件系统、网络与凭据边界
运行命令或代码的智能体应处于明确边界内，限制它可访问的文件、可连接的主机和可读取的秘密值。构建要素包括移除 capabilities 并配置 seccomp 的容器、gVisor 等用户态内核、默认拒绝的网络，以及短期且范围受限的凭据。
-
Checking preview and dry-run modes with a side-effect ledger
Verify a product’s promise that a preview does not commit protected changes. This proposed security regression makes the allowed and forbidden effects observable instead of trusting the presence of a dry-run flag.
-
缓慢变化维度：覆盖值、添加行或添加列
维度属性变化时（客户搬家、产品重新分类），类型 1 覆盖原值并丢失历史，类型 2 使用新代理键添加一行，包含生效日期、失效日期和当前行标志，类型 3 则在额外列中保留旧值。快照工具每次运行时比较更新时间戳或一组列，以实现类型 2。
-
Flow fields: share a destination without sharing one rigid path
Build reusable cost-to-go and direction fields for crowds, preserve weighted-edge semantics, and invalidate cached fields when their movement assumptions change.
-
设备电池健康日志：手机、Windows 笔记本与 Linux 电源接口报告什么
每月记录设备自行报告的电池数值：iPhone“电池健康”页面相对全新状态的最大容量、Windows 中 powercfg /batteryreport 生成的 HTML 报告，以及 Linux power-supply 类的 charge_full 和 charge_full_design 属性。连同日期、软件版本和事件保存原始数据，序列就能显示趋势及跳变，而不提供任何充电建议。
-
设计持续集成流水线
CI 流水线应快速、能够自我测试，并对每项变更采用同一流程：从干净检出的代码构建，分阶段运行静态检查和测试，明确暴露失败，并让总耗时足够短，使人愿意等待结果。
-
Windows answer files (unattend.xml): configuration passes and where Setup looks for them
An unattend.xml answer file supplies settings to specific configuration passes of Windows Setup — windowsPE, generalize, specialize and oobeSystem are the ones provisioning touches most. Setup finds the file through a fixed implicit search order and caches it in %WINDIR%\Panther, and Windows System Image Manager builds these files and can hide, but not encrypt, local-account passwords in them.
机器可读： JSON