모든 문서
-
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.
-
Configuring the logging module once, at the entry point
Libraries obtain loggers and never configure handlers; the application configures handlers, levels and formats once at start-up, so that output is controlled in one place and duplicates are avoided.
-
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).
-
A CONTRIBUTING file that answers a newcomer's first five questions
Before writing code, a would-be contributor asks: is this change wanted, how do I propose it, what must a pull request contain, how long until someone answers, and how does a merged change reach users. A CONTRIBUTING file that answers those five questions in order, and links out for everything else, is meant to head off pull requests that would be rejected for scope or missing tests.
-
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.
-
Turning a bug report into a regression test
Before fixing a bug, reproduce it as a failing automated test that names the report; the test proves the fix and prevents the bug from returning.
-
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?
-
Checking installed package integrity on Debian and Ubuntu with debsums and dpkg --verify
debsums compares installed files against the MD5 sums recorded at package build time, dpkg --verify (since dpkg 1.17.2) compares metadata recorded in the dpkg database itself, and dpkg -S/-L answer "which package owns this file" and "what files did this package install" before deciding whether to reinstall it.
-
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