すべての記事
-
Leaderboard walk-through: score events, a derived sorted set and rebuildable rankings
A design walk-through for leaderboards: server-authoritative score events with an idempotency key as the truth, one sorted set per board period as a derived index answering top-N and single-member rank queries, tie rules encoded into the score, period boundaries routed by occurrence time, and rebuilds as a routine.
-
Redirects 301, 302, 307 and 308: which ones preserve the request method
301 and 302 permit a user agent to turn a redirected POST into a GET; 307 and 308 forbid changing the method, so the body is resent; 303 always switches to a GET of another resource. 301 and 308 are heuristically cacheable, 302 and 307 are not. Choose by permanence and by whether the method must survive.
-
logging モジュールをエントリーポイントで一度だけ設定する
ライブラリはロガーを取得するだけで、ハンドラーを設定しません。アプリケーションが起動時にハンドラー、レベル、書式を一度だけ設定することで、出力を一か所で制御し、重複を防ぎます。
-
Reading the load average and understanding the OOM killer
Linux load average counts runnable and uninterruptible-sleep tasks over 1, 5 and 15 minutes, so a high number with idle CPUs points at I/O or a hung filesystem. When memory cannot be reclaimed, the OOM killer picks a task by badness score, which oom_score_adj shifts from -1000 (never) to +1000 (first).
-
新規貢献者の最初の5つの問いに答える CONTRIBUTING ファイル
貢献しようとする人はコードを書く前に、その変更は求められているか、どう提案するか、プルリクエストに何が必須か、返信までどれほど待つか、マージした変更がどうユーザーに届くかを尋ねる。5つの問いに順番に答え、その他はリンクで案内する CONTRIBUTING ファイルは、スコープやテスト不足で却下されるプルリクエストを未然に防ぐことを意図している。
-
Stereoscopic XR Rendering: Preserve Per-View Poses, Projections and Image Layers
Render consistent stereo views using runtime view data and validate multiview optimizations without losing eye-specific geometry or effects.
-
バグ報告を回帰テストに変える
バグを直す前に、報告を示す失敗する自動テストとして再現します。そのテストが修正を証明し、バグの再発を防ぎます。
-
LoRA：低ランク適応とメモリ削減が及ぶ実際の範囲
LoRA は基盤重みを固定したまま低ランクの更新を学ぶ。学習可能なパラメータとそのオプティマイザー状態は減るが、基盤モデル、活性化、配備時の互換性も考慮する必要がある。
-
Unreal gameplay framework: place rules, shared state and possession deliberately
Separate server rules, replicated match information, player control and the possessed body so respawning and multiplayer do not mix their responsibilities.
-
What share of shipped features are still used 90 days after release, and what happened to the unused ones and their flags?
Open question: feature-flag tools such as Unleash attach an expected lifetime to a flag and mark it potentially stale once that lifetime passes, which covers the flag but not the feature; for products that track feature usage, what share of features released in a year had meaningful use after 90 days, what happened to the rest (removed, hidden, kept), and did their flags and code follow?
-
debsumsとdpkg --verifyでDebian・Ubuntuのインストール済みパッケージの整合性を確認する
debsumsはインストール済みファイルをパッケージのビルド時に記録されたMD5値と比較し、dpkg --verify（dpkg 1.17.2以降）はdpkgデータベース自体に記録されたメタデータと比較します。dpkg -S/-Lでは、再インストールを判断する前に「このファイルはどのパッケージのものか」「このパッケージは何をインストールしたか」を確認できます。
-
Managing certificates from PowerShell: the Cert: drive, PFX import/export, and binding one to IIS
Browsing Cert:\LocalMachine\My, filtering by expiry with Get-ChildItem, moving a certificate with its private key via Import-PfxCertificate/Export-PfxCertificate, New-SelfSignedCertificate for test use only, and binding the result in IIS with New-WebBinding or checking it with netsh http show sslcert.
-
State units beside every measurement
Make measurement records interpretable by keeping units, aggregation and population beside each value.
-
IBM i security basics for administration: special authorities, object authority, QSECURITY, and QAUDJRN
IBM i access control rests on special authorities such as *ALLOBJ and *SECADM granted per user profile, object-level authorities checked with DSPOBJAUT/EDTOBJAUT, the QSECURITY system value that sets the enforcement level, and the QAUDJRN audit journal that records what happened — all administration and auditing, no exploitation.
-
Logging a consumer PM2.5 sensor: what to record beside each reading and what the number cannot say
A consumer particulate sensor reports an estimate of the mass of particles 2.5 micrometres and smaller; the EPA states that such sensors come with lower accuracy and higher uncertainty than regulatory monitors, describes collocation with reference instruments as an effective way to assess them, and notes that an outdoor correction may not apply indoors and that changing temperature and humidity may affect some sensors. A household log therefore stores the raw value, the averaging interval, placement, indoor events and the nearest official monitor's value with its distance.
-
Testing authorization through resource relationships rather than role names
Check whether a caller can act on a particular object through the relationship the product actually promises. This proposed lab method treats role labels as fixture attributes, not as the test oracle.
-
Modelling states with Literal, Enum and TypedDict
Replace free strings and loose dictionaries with Literal unions, enumerations and TypedDicts so that impossible states are rejected by the type checker and documented in one place.
-
make as a task runner: phony targets, tabs and one shell per line
A Makefile is a workable entry point for a repository's commands if command targets are declared .PHONY, recipe lines start with a tab, and it is understood that each recipe line runs in its own shell unless .ONESHELL is set; keep the default goal harmless and keep real file dependencies real.
-
Foot placement IK: preserve contact without fighting the walk cycle
Build terrain-aware foot targets, respect leg reach and contact phases, and keep pelvis adjustment and moving-platform anchors consistent.
-
Recursion versus iteration: stack depth, limits and when to convert
Recursion mirrors tree-shaped problems but spends one stack frame per level; the stack is bounded by the interpreter's recursion limit or the thread's stack size, so recursion over input-controlled depth is a crash waiting to happen. Convert to an explicit stack or loop when depth grows with input size.
機械可読： JSON