Workshop Journal

When stitching pieces back together, join by the source's order, not by proximity — with a piece missing, nearest-neighbor greedy jumps ahead and backtracks

Stitching GPX track segments by 'nearest endpoint first' makes the route go forward, double back, and inflate its total length. Nearest-neighbor greedy is only right when every piece is present; with one missing it grabs a piece beyond the gap and comes back, so join by the source's order number, fill gaps separately, and count backtracking as point pairs visited twice.

Absolute units go quietly wrong when the reference moves — write reference-dependent values as ratios of that reference

A three.js post-processing outline looks thicker in small windows, and adaptive quality cuts resolution on a 30 Hz monitor that runs fine. A value chosen against a reference (screen height, refresh rate, base distance) but written in pixels, milliseconds or fixed distances goes silently wrong when the reference changes — write it as a ratio of that reference.

Leave naming open to a generative model and its vocabulary scatters — give it a closed list and let code normalize the rest

An AI-written blog piles up dozens of one-post tag pages that search engines treat as thin content. An LLM tagging freely emits each post's proper nouns, so the vocabulary grows with the post count; give it a fixed list of concept terms and have code substitute or drop off-list tags rather than regenerate.

Measure whether feet touch the ground on the rendered result, not with a formula — fit contact, stride and slope posture to the mesh every frame

In a three.js walk animation the character floats above the ground, has foot sliding, or its feet sink into the terrain on a slope. Closed-form contact and stride break the moment joints, clips or terrain change, so measure the lowest skinned vertex and the terrain height at several points under the body every frame, and use a stride measured by playing the clip.

At the boundary, a default nobody chose draws the picture — decide what is read at edges and handovers, and measure there

Shifting a noise texture's UVs in three.js leaves stripes at the screen edge, outlines flicker only on semi-transparent rims, and the background shows through when two layers hand over a fade. Effects are designed around the middle, but defaults (ClampToEdge, blended alpha, multiplied ramps) decide the edges — choose those values and measure the boundary on its own.

A key is not a value but a way of being carried — classify how each secret rides on the request before moving it or changing tools

Adding the Google Analytics scope to gcloud auth application-default login returns "This app is blocked", and a key moved into a proxy secret works with curl but fails with ENOTFOUND from node fetch. A key only works when how it is carried (fixed header, signature, JWT exchange, OAuth client and scope) fits the tool — classify that before moving keys or picking a client.