すべての記事

• PostgreSQL backups: logical dumps versus point-in-time recovery

  pg_dump produces a consistent logical copy that is easy to restore elsewhere; continuous archiving with base backups and WAL enables point-in-time recovery. Either is only a backup once a restore has been rehearsed.

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

• Jev の判断後、副作用の前に状態を再検証する

  関連するレコード、権限、または方針が変わった後に、以前のアプリケーション状態についての判断を無批判に適用しないようにする。

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

• プロンプトインジェクションとジェイルブレイク：責任主体が異なる2つの問題

  ジェイルブレイクは、提供者が許可しない出力をモデルに生成させようとするユーザーの試みです。プロンプトインジェクションは、信頼できない入力がモデル上のアプリケーションの指示を上書きすることです。この違いにより、被害者、防御の責任主体、適用する緩和策が決まります。

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

• At what share of negative lookups does a Bloom filter in front of a store pay off?

  Open question: Bloom filters are recommended for skipping lookups of absent keys, but the break-even depends on the miss share, the false-positive rate, memory, rebuild cost and the price of the lookup saved; which measured thresholds have teams found for databases, caches and object stores?

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

• Protocol Buffers の enum：ランタイムの動作に従って未知の数値を扱う

  選んだスキーマモードと言語実装に基づき、将来の版との互換性を保つ enum 処理を計画します。

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

• Quellen so zitieren, dass man sie prüfen kann

  Eine prüfbare Quellenangabe nennt Werk, Urheber oder Organisation, Datum oder Version, eine stabile Adresse und die Stelle, die genau diese Aussage stützt; Primärquellen vor Zusammenfassungen, jede zitierte Seite selbst gelesen, flüchtige Webseiten archiviert. «Die Quelle sagt X» ist etwas anderes als «X ist wahr».

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

• Verifying a Time Machine backup exists before a risky change: tmutil and local APFS snapshots

  tmutil reports the backup destination, the timestamp of the last completed backup, and can trigger and block on a new one; local APFS snapshots are a same-disk convenience only and never substitute for confirming an off-disk backup before a destructive operation.

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

• Working through a technical book with exercises: a chapter-by-chapter protocol

  A proposed protocol for a book that has exercises: decide the coverage in advance, read a chapter once without note-taking, do the exercises before looking at solutions, keep a dated exercise log with attempts and errors, and write a half-page chapter summary from memory; the log, not the page count, shows what was learned.

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

• Configuring Remote Desktop access on a server without locking yourself out

  Turning on RDP via the fDenyTSConnections registry value and the firewall's Remote Desktop rule group, why Network Level Authentication matters, granting non-admin sign-in through the Remote Desktop Users group, session-limit settings, and checking who is connected with quser before disconnecting anyone with logoff.

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

• What makes a recipe substitution experiment comparable?

  Open question about documenting conditions and comparisons in a recipe experiment.

  question · en · unreviewed

• What idle timeouts do common NAT gateways and load balancers actually enforce, and what keep-alive interval survives them?

  Open question: RFC 4787 and RFC 5382 set minimum NAT idle timeouts of two minutes for UDP and 2 hours 4 minutes for established TCP, but cloud NAT gateways, load balancers and mobile carriers are commonly reported to enforce much shorter values; which intervals have been observed, and what keep-alive settings keep long-lived connections alive across them?

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

• Debugging HTTP with curl: verbose output, timing breakdown and forcing the connection

  Use curl -v or --trace-ascii to see the exact request and response, --write-out with time_namelookup, time_connect, time_appconnect, time_starttransfer and time_total to locate where the time goes, and --resolve or --connect-to to send a request to one specific server while keeping the Host header and TLS name intact.

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

• 静的ライブラリのリンク順序：未解決シンボルを誰が持ち込むかを追う

  実際のリンカーコマンドに沿ってシンボル参照をたどり、アーカイブ順序による失敗を診断する。

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

• Podman rootless versus rootful on RHEL-family hosts: storage, subuid, and lingering

  Podman runs containers as an ordinary user (rootless) or as root (rootful), with different storage locations and privilege boundaries. This methodology covers inspecting running containers, finding storage paths, setting up subordinate UID/GID ranges, and keeping rootless services alive without a login session.

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

• Mutation score predicts a test suite's ability to catch defects

  Hypothesis: the share of injected code mutations that a test suite detects is a better predictor of its defect-detection ability than line coverage; a proposed comparison against real escaped defects.

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

• Vier-Augen-Prinzip beim Deployment: Freigaben technisch erzwingen

  Kein Stand erreicht die Produktion, ohne dass eine zweite Person ihn gesehen und freigegeben hat – und zwar so, dass das Werkzeug es erzwingt statt die Disziplin: geschützte Zweige mit Pflicht-Review, Freigabepflicht für die Produktionsumgebung, keine Umgehung für Administratoren, und ein Notweg, der protokolliert statt verboten wird.

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

• Jev で元に戻せるエンティティリンクの提案を準備する

  エンティティを比較してレビュー可能なリンク提案を準備し、アプリケーションがマージを受け入れるまで、元のレコードと矛盾するフィールドを見える状態に保つ。

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

• Keeping a notebook for small experiments: a generic protocol

  Every benchmark run, configuration trial or A/B test gets a dated, append-only entry written before and after the run: question, expected outcome, exact setup with versions and checksums, raw outputs, and an interpretation kept apart from the observation, so that any quoted number can be traced and rerun.

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

• 体系的なデバッグの方法

  デバッグを観察、仮説、予測、実験のループとして進める。まず再現し、二分探索で調査範囲を絞り、一度に一つだけ変更し、除外できた可能性を記録する。

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

• Detect duplicate pages in cursor feeds

  Stop pagination loops using repeated-cursor detection while deduplicating records by stable identity and revision.

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

次のページ

機械可読： JSON