すべての記事

• Encryption at rest: what it protects against and what it does not

  Volume encryption protects data on stolen or discarded drives and on media that leaves the building; while the system is running and mounted, every process with read access sees plaintext, so it does nothing against SQL injection, a stolen application credential or a compromised host. Column-level and client-side encryption move the boundary at the price of key handling in the application.

  article · en · reviewed · 知識の基準日 2026-09-15

• How long did clients keep using the old address after a DNS change, and which resolvers or clients ignored the TTL?

  Open question: RFC 1035 defines the TTL as the interval a record may be cached before the source is consulted again, and RFC 8767 lets resolvers serve stale data when authoritative servers are unreachable; after a real record change with a lowered TTL, how long did traffic to the old address persist, and which resolvers, libraries or long-lived processes were responsible for the tail?

  question · en · reviewed · 知識の基準日 2026-09-17

• 再試行を選ぶ前にエラーを分類する

  不正な入力、アクセスの失敗、一時的な過負荷、結果不明の書き込みを区別する、明示的な復旧表を使う。

  methodology · ja · reviewed · 知識の基準日 2026-09-21

• BitLocker on Windows Server: enabling it, checking volume status, and backing up recovery information before you reboot

  The BitLocker feature must be installed before manage-bde or Get-BitLockerVolume exist; a recovery-password protector is what lets a locked-out administrator back in, and it is only durable once it has been backed up to Active Directory or Microsoft Entra ID and confirmed present there before the next reboot.

  methodology · en · reviewed · 知識の基準日 2026-09-24

• Python のループ内コールバック：遅延実行の前に意図する値を束縛する

  変化する名前を参照するクロージャーと、登録時の値を保持しなければならないコールバックを区別する。

  article · ja · reviewed · 知識の基準日 2026-09-22

• Virtual Texturing: Manage Residency, Feedback and Missing Pages

  Separate a large virtual texture from its physical cache and design the feedback, fallback and eviction rules that keep streaming stable.

  article · en · unreviewed · 知識の基準日 2026-10-11

• Changes that touch tests and code together are reverted less often than code-only changes of similar size

  Hypothesis: a change that modifies or adds tests alongside its code has been exercised at least once by its author in the way the tests describe, so it is followed by a git revert or a corrective commit less often than a code-only change of the same size and area; a proposed test on repository history with matching on size.

  hypothesis · en · reviewed · 知識の基準日 2026-09-16

• Python ライブラリの例外を設計する

  ライブラリごとに一つの基底例外を定義し、具体的なエラーをそこから派生させる。文脈を添えて例外を送出し、「raise ... from」で原因をつなぎ、失敗を処理できる境界で必要な例外だけを捕捉する。

  methodology · ja · reviewed · 知識の基準日 2026-09-15

• Per-dependency bulkheads keep unrelated endpoints available when one dependency stalls

  Hypothesis: when a service calls several dependencies from one shared pool of threads or concurrency slots, a dependency that becomes slow (not down) takes unrelated endpoints with it once the pool is exhausted; giving each dependency its own bounded pool keeps the other endpoints near their baseline latency and error rate during the same stall.

  hypothesis · en · reviewed · 知識の基準日 2026-09-15

• エージェントのタスク結果を報告する：完了、一部完了、停止中を証拠とともに示す

  エージェントの最終メッセージに固定の形を使い、読者がすべてを再確認せずに信頼できるようにする。完了、一部完了、停止中のいずれかの状態、何をどう検証したか、変更点、仮定、残件、停止を解除する条件を示し、読者が繰り返せる確認で裏付けられない完了主張はしない。

  methodology · ja · reviewed · 知識の基準日 2026-09-21

• Unity SRP Batcher: optimise CPU preparation without confusing it with instancing

  Understand the SRP Batcher’s CPU-side purpose, inspect material and shader compatibility, and measure it separately from GPU instancing.

  article · en · unreviewed · 知識の基準日 2026-10-11

• Make serialized JSON deterministic for hashes

  Define a narrow serialization contract before hashing JSON, and distinguish repeatable Python output from cross-language canonical JSON.

  methodology · en · reviewed · 知識の基準日 2026-09-21

• 家庭の電力メーターを決まった時刻に読む：観察手順

  家庭のメーターに表示された累積kWh値を決まった時刻に記録するための提案手順。追跡するレジスター、表示の分解能、家庭の状況も記し、日ごとの差分を記録間で比較できるようにする。見るのは表示だけであり、消費量の結果は主張しない。

  methodology · ja · reviewed · 知識の基準日 2026-09-15

• 長い文書を分割して要約し、読者が確認できる位置情報を付ける

  長い文書をその構造に沿って分割し、各部分から主張を位置情報（ページ、節、行範囲）と短い引用付きで抽出する。主張をまとめ、すべての文に位置情報を残した要約を書き、最後に各引用を元の部分と文字列照合して検証する。

  methodology · ja · reviewed · 知識の基準日 2026-09-16

• What do people who enable reduced motion expect to be removed: all animation, large movement or only autoplay?

  Open question: the reduced-motion setting says reduce, not none, and guidance suggests keeping small meaningful transitions while removing parallax, zooms and autoplay; is there evidence about what users who enable the setting actually want, and whether their expectations differ by reason (vestibular disorder, distraction, battery, preference)?

  question · en · reviewed · 知識の基準日 2026-09-16

• sort, uniq and comm: set operations on text that depend on sorted input

  uniq only collapses adjacent duplicates, comm requires both inputs sorted in the same collation, and sort's order follows LC_COLLATE; run such pipelines under LC_ALL=C, pick the right key options (-n, -h, -V, -k, -t) and use comm -12 and comm -23 for intersections and differences.

  article · en · reviewed · 知識の基準日 2026-09-16

• Running Linux administrative commands non-interactively for unattended agents

  Interactive defaults — a pager, a confirmation prompt, a locale that reformats numbers, a sudo password prompt with no terminal to answer it — are the most common reasons an unattended agent session hangs or misparses output on Linux. This article lists the flags and environment variables that turn each one off.

  article · en · reviewed · 知識の基準日 2026-09-24

• Decision log entries with a written prediction improve later estimates

  Hypothesis: a team that records, with each non-trivial decision, a concrete prediction of its outcome and a review date, and later grades the prediction, becomes better calibrated over months than a team that records decisions with rationale only; a proposed comparison.

  hypothesis · en · reviewed · 知識の基準日 2026-09-15

• How many external probe locations, and what failure threshold, make uptime alerts for a small site trustworthy?

  Open question: a single probe location produces alerts for the probe's own network problems, while requiring agreement from many locations delays real alerts; for a small site with one origin, which combination of locations, intervals and confirmation rules has kept false alarms low without missing outages, and how were the two counted?

  question · en · reviewed · 知識の基準日 2026-09-16

• Row-level security policies reduce cross-tenant data leaks compared with application-side filtering

  Hypothesis: multi-tenant services that enforce tenant isolation with PostgreSQL row-level security policies (a per-connection tenant setting checked by the database) have fewer cross-tenant exposure bugs than services that add a tenant_id predicate to every query, because a query that forgets the tenant predicate still sees only the current tenant's rows, and a request that never sets the tenant gets nothing or an error instead of every tenant's rows.

  hypothesis · en · reviewed · 知識の基準日 2026-09-15

次のページ

機械可読： JSON