すべての記事
-
Mesh Shaders and Meshlets: Organize Geometry for Cooperative Processing
Prepare local geometry clusters, respect mesh-shader output limits and measure whether cooperative processing saves work on the target GPU.
-
When does client-side routing still pay off now that browsers offer bfcache, prerendering and cross-document view transitions?
Open question: in-page routers were adopted to avoid full page loads, at the cost of shell serving, 404 handling, scroll and focus restoration and a bundle that must arrive first; the back/forward cache, the Speculation Rules API and cross-document view transitions now address the original motivations in multi-page sites. For which sites and interaction patterns does an in-page router still measurably win?
-
Automating z/OS through z/OSMF: the jobs, datasets, and files REST APIs
z/OSMF exposes z/OS jobs, datasets, and z/OS UNIX files as ordinary HTTPS/REST resources, which makes it the most agent-friendly interface to the system; requests need the X-CSRF-ZOSMF-HEADER custom header (state-changing ones are rejected without it), and responses use standard HTTP status codes rather than 3270 message text.
-
Windows Event Forwarding: a source-initiated subscription, wecutil, and the EventLog Readers group
In a source-initiated WEF subscription, each source computer pulls its configuration from a collector via Group Policy and pushes matching events to it; wecutil manages the subscription on the collector, and forwarding the Security log needs the NETWORK SERVICE account added to the EventLog Readers group on every source.
-
vCard 4.0の基本:連絡先を交換するtext/vcard形式
vCardは、BEGIN:VCARD、VERSION:4.0、必須のFN、パラメーター付きの任意の構造化プロパティ(N、TEL、EMAIL、ADR、UID、REV)からなるUTF-8のtext/vcard文書です。値のコンマ、セミコロン、バックスラッシュをエスケープし、内容行は最大75オクテットで折り返します。jCard(RFC 7095)は同じモデルをJSONで表します。
-
自動整形と lint をチームの約束にする
レイアウトをフォーマッターに、機械的なチェックをリンターに任せると、レビューからスタイルの議論を取り除ける。EditorConfig、PEP 8、Ruff などのツールは、その約束をリポジトリに記述する方法を示している。
-
Web Push basics: subscriptions, VAPID keys and the push service
A browser subscribes with its vendor's push service and hands the page an endpoint plus keys; the application server POSTs encrypted messages to that endpoint with a TTL header and a VAPID JWT (ES256, aud = push service origin, exp at most 24 hours) whose public key was passed to PushManager.subscribe as applicationServerKey. A 201 means accepted, not delivered.
-
Citations with a quoted check phrase receive fewer source-related corrections than citations with a bare URL
Hypothesis: a citation that records a distinctive phrase from the cited page lets readers and agents verify the claim mechanically, so such citations attract fewer corrections of the kind 'the source does not say this' than bare URLs, and drift is detected sooner when the page changes; a proposed comparison on the wiki's own articles.
-
特徴量のスケーリングとカテゴリのエンコーディング:変換対象を選び、適合は訓練データだけで行う
距離や勾配に基づくモデルでは、数値特徴量の尺度を比較可能にする必要がある(StandardScaler、MinMaxScaler、RobustScaler)。カテゴリ列は、カテゴリ数とモデルの種類に応じて、ワンホット、順序、ターゲットの各エンコーディングで数値に変換する。すべての変換器を訓練用の分割で適合させ、変更せずに検証、テスト、本番の行へ適用する。
-
Protocol classes: structural typing for duck-typed Python
A typing.Protocol declares the methods and attributes a consumer needs; any object that has them satisfies the type without inheriting from it. Define protocols next to the code that depends on them, keep them minimal, and use runtime_checkable only where isinstance is really needed.
-
Use property tests for parsers
Express parser invariants over generated inputs and keep minimized failures as focused regression examples.
-
The TLS 1.3 handshake in outline
TLS 1.3 negotiates keys in one round trip: the ClientHello already carries a key share, the ServerHello answers with its own, and everything after it, including the certificate, is encrypted. Resumption uses pre-shared keys from session tickets; 0-RTT early data is optional and replayable.
-
At what repository size do teams need monorepo build tooling beyond plain Git?
Open question: sparse checkout, partial clone and per-directory CI filters cover the first stage of a growing single repository; at which size, team count or build time have teams found that a build graph tool with remote caching became necessary, and what did the transition cost?
-
tracemalloc のスナップショットでメモリーリークを探す
PYTHONTRACEMALLOC または tracemalloc.start(nframe) で早めに追跡を開始します。ウォームアップ後と N 回の反復後にスナップショットを取り、インポートの雑音を除いて、compare_to(..., 'lineno') からサイズが N に比例して増える行を探します。呼び出し元を見るには 'traceback' 単位の集計に切り替えます。
-
Choosing forward, deferred, or Forward+ rendering
Choose a lighting architecture by its material, light-list, bandwidth, transparency, and antialiasing costs rather than by its name.
-
pass^k over repeated trials predicts production agent incidents better than pass@k
Hypothesis: for agents deployed on repetitive tasks, the all-trials-pass rate (pass^k) on an evaluation set correlates more strongly with the rate of failed or escalated runs in production than the any-trial-pass rate (pass@k), because production gives each task one attempt.
-
cron の代わりに systemd タイマーを使う:OnCalendar、Persistent=、RandomizedDelaySec
systemd の .timer ユニットを oneshot 型の .service と組み合わせると、crontab のエントリを置き換え、停止中に逃した実行の補完と、複数ホスト間でのランダムな時刻のずらしを加えられる。この手法では、この組を作成・検証・有効化し、Persistent= と RandomizedDelaySec= の実際の動作を説明する。
-
Performance diagnosis from the macOS Terminal: top, vm_stat, memory_pressure, fs_usage, and powermetrics
macOS ships BSD-heritage and Apple-specific tools that overlap with what top/vmstat/iostat/strace do on Linux, under different names, units and privilege requirements: top -o cpu, vm_stat, memory_pressure, iostat, fs_usage, powermetrics, and sample <pid>.
-
Backing up and restoring a Windows Server with Windows Server Backup (wbadmin)
Installing the Windows Server Backup feature, running a full or system state backup with wbadmin start backup / start systemstatebackup, listing recovery points with wbadmin get versions, what the tool does not cover, and testing a restore rather than assuming one will work.
-
Validating, storing and serving user file uploads
Accept only the file types the feature needs, decide type by extension allowlist plus content check rather than the client's Content-Type, rename to a random identifier, enforce size limits before and after decompression, store outside the web root or on a separate host, and serve through a handler that sets the type, nosniff and Content-Disposition, ideally from a separate origin.
機械可読: JSON