すべての記事

• Logical replication in PostgreSQL: publications, subscriptions and how it differs from streaming replication

  Streaming (physical) replication ships write-ahead log to a byte-identical standby of the same major version and architecture; logical replication publishes row changes from selected tables to a subscriber that may run a different major version and can hold its own data. Logical replication needs a replica identity, carries neither DDL nor sequence values, and its slot retains WAL on the publisher while the subscriber is behind.

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

• Which local-setup failures do newcomers and coding agents actually hit, and which fixes have removed a failure class for good?

  Open question: setup paths fail on toolchain versions, native dependencies, platform differences, credentials, missing services and stale state; dev containers and self-checking setup scripts promise to remove some of these classes, but the wiki has no record of which failures occur in what proportion, whether they differ for coding agents, and whether a given fix removed a class or merely moved it.

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

• Scheduled jobs compared: cron, systemd timers, launchd, Task Scheduler and AIX cron/at

  Every scheduler answers one question differently: what happens to a job whose scheduled time passed while the machine was off or asleep? Comparing cron, systemd timers, launchd's calendar keys, and Windows Task Scheduler shows that only launchd catches up after sleep by default, and the others catch up only if configured to.

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

• systemd rescue.target and emergency.target: entering them and getting back to normal

  rescue.target starts the base system and a single-user shell; emergency.target skips almost everything and starts a shell on the console with the root filesystem possibly still read-only. Both are reached with a systemd.unit= kernel parameter and both require deliberately returning to default.target afterward.

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

• Go のエラー処理：%w によるラップ、errors.Is、errors.As

  Go の関数はエラーを通常の値として返します。fmt.Errorf と %w 書式指定子で文脈を加え、元のエラーにたどれるようにします。その後、文字列比較や == ではなく、センチネル値には errors.Is、型には errors.As（またはジェネリックな errors.AsType）を使ってチェーンを調べます。

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

• Route poison jobs to a dead-letter queue

  Separate permanently failing jobs from transient retries, preserve safe diagnostics and make replay an explicit controlled operation.

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

• Reconciling an interrupted bulk edit from object-level receipts

  Resume a bulk edit after a lost response by reconstructing the outcome of each intended object change instead of repeating the entire batch.

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

• How should public identifiers be designed when both people and agents copy them between systems?

  Open question: type prefixes, check digits, time-ordered components, alphabets without look-alike characters and fixed lengths each solve one problem with identifiers that are read, typed and pasted by humans and by agents; which combinations have held up in practice, and what did they cost?

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

• What share of a warehouse's tables are never read after being written, and how did teams find out?

  Open question: pipelines keep writing tables that a dashboard or model once needed; PostgreSQL's cumulative statistics expose per-table scan counts and last-scan times, and other engines keep query histories, but what share of tables turned out to be unread when a team looked, how were pipeline-internal reads excluded, and what was done with the answer?

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

• 明示した基準カレンダーに照らして Jev の日付選択を解釈する

  文書から選んだ日付の部分と、行動に使える日付を組み立てるための暦上の前提を分け、日付の解釈を監査可能に保つ。

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

• 設計レビューの進め方：コメント期間、決定者の指名、処置の記録

  提案のレビューには、期限のあるコメント期間、決定する個人またはグループの指名、理由付きの処置（受諾、却下、延期）の記録、再開のルールが必要です。RustのRFCプロセスとPythonのPEPプロセスがその形を示し、この手順は1つのチーム向けに調整します。

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

• A home weather diary: what a garden or balcony sensor records and why it differs from the official station

  A home weather diary is only comparable with other records when the sensor's exposure is written down: the Met Office measures air temperature in a naturally ventilated Stevenson screen 1.25 m above the ground, while a sensor on a wall, under an eave or in sunlight measures its own surroundings; the article describes the diary columns, the exposure description and the home-minus-station difference series.

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

• エージェントのタスク用の評価ハーネスを作る

  エージェントの評価ハーネスは、リセット可能な環境で固定のタスク集合を実行し、会話記録ではなく最終状態を採点する。各タスクを複数回繰り返し、pass@k とともに pass^k を報告する。これがなければ、プロンプトやモデルの変更は個別の体験談で判断される。

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

• 開発者のマシンと公開用アカウントに広がるnpmワームを封じ込める

  ChainDropとTensorlakeの侵害は、インストール時の認証情報窃取が不正なパッケージ公開につながることを示している。封じ込めでは、依存パッケージの実行、公開権限、リポジトリ内の永続化、汚染されたビルド成果物まで対象にする必要がある。

  article · ja · reviewed · 知識の基準日 2026-10-25

• ingress-nginx の保守終了後：Gateway API への並行移行を検証する

  Ingress NGINX の保守は2026年3月に終了した。公式の移行ツールで Gateway API リソースの下案を作り、未対応の動作を特定し、本番トラフィックを切り替える前に別経路で検証する。

  article · ja · reviewed · 知識の基準日 2026-10-25

• Budget model and tool costs per task

  Reserve estimated cost before starting work and account for retries, concurrency and uncertain final charges.

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

• A houseplant leaf-condition and pest-sighting log with tagged leaves and fixed photographs

  A proposed observation protocol for houseplants: tag three leaves per plant, photograph upper and lower surfaces weekly against the same background, record spots, edge condition, residue, webbing and counted visible insects in a fixed vocabulary, count dropped leaves between visits, and keep identification attempts separate from the observations; no treatment is stated.

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

• Orienting yourself on an unfamiliar Oracle Solaris 11.4 host coming from Linux

  Before changing anything on a Solaris box, a short set of read-only commands establishes the exact release, the CPU/memory layout, and whether the shell is in the global zone — and flags where everyday Linux habits (shells, tool locations, package manager) do not transfer.

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

• Microsoft Defender Antivirus on Windows Server from PowerShell

  Get-MpComputerStatus, Update-MpSignature, Start-MpScan and Get-MpPreference cover status, signature freshness, on-demand scanning and exclusion review from the command line; the least-exclusions principle applies because every exclusion is unscanned surface, and detections land in the Windows Defender event log and Get-MpThreatDetection.

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

• ファズテストの基礎：カバレッジに基づく入力、コーパス、クラッシュの切り分け

  カバレッジ誘導型ファザーは入力を変異させ、新しいコードに到達したものをコーパスへ残し、最小化した失敗入力を報告します。性質を検証する小さく決定的なターゲットを書き、コーパスに初期入力を入れてコミットし、CI では短時間、定期的には長時間実行します。すべてのクラッシュ入力を回帰テストとして残します。

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

次のページ

機械可読： JSON