Building a QR code, one cell at a time
Start with a message. Follow its bytes through error correction, grid placement, and masking. Play the construction, step through each cell, or jump to any stage.
FIELD NOTES
Technical stories grounded in the repositories: the problem, the implementation, and what the code actually shows.
47 stories
Start with a message. Follow its bytes through error correction, grid placement, and masking. Play the construction, step through each cell, or jump to any stage.
V39's controller connects repository identity, release evidence, and service access.
Rodeo Operations connects people, assignments, and access without making every user an administrator.
Data Matrix makes a small image carry structured information. The interesting work happens before the pixels.
A small Reed–Solomon example makes error correction tangible.
Crabby Dan is an early command-line AI experiment whose entire request path is easy to inspect.
Just a Clock connects a time signal, a real-time clock, and a bright display—and documents how they interfere.
Part 1 of 6. Follow the same six characters through QR, Data Matrix and Aztec, then check the rendered images with an independent decoder.
A two-instance reference demonstrates deployment as a sequence of verifiable transitions.
AWS Setup preserves how the platform was created while keeping ordinary releases away from provisioning.
Clockthenticator explores authentication codes on a small embedded display.
A clock and a survey link share an embedded display.
A small Canvas experiment makes image correspondence visible.
The Ukrainian dictionary repository makes lexical information available to software.
A historical repository captures small services, shared utilities, and an earlier delivery model.
CIDR planning becomes easier when the ranges, conflicts, and gaps share one model.
CIDR Runner organizes operational capabilities behind explicit HTTP routes.
DenoBar gives many small development services a shared operational vocabulary.
Dir Diode treats agent workspaces as explicit overlays instead of automatic mirrors.
The service name is TSDB; the inspected implementation is a focused Redis-style data store.
Stokes UI makes shared interface decisions explicit and locally reusable.
Player Piano connects a visual score, browser playback, and a small portable file format.
QR Card moves an existing encoder interface into a restricted service without changing its output.
Inkframe treats panels, gutters, artwork, and lettering as editable parts of one document.
The Rules Desk connects retrieval to immutable editions and citation lines.
Deno ZXing preserves known encoder behavior while adapting the service boundary.
Sticher models an audio session as instructions over original recordings.
Forklift Choreography turns motion into an editable score.
AWS Recall combines domain-weighted practice with confidence-aware review.
Cashbox treats concurrency and uncertain acknowledgements as normal operating conditions.
Tinyloop turns a short moment into an animated GIF without uploading the recording.
Evidence Ledger separates original evidence from editable planning state.
Extracting a local AWS tool means preserving its interface while making its hosted limits explicit.
The hosted learning category preserves useful workflows and identifies the adapters still required.
The operations category adapts media tools to a narrower hosted environment.
The hosted deployment category currently exposes a navigation service, with a narrow runtime contract.
Reference Workspace is a useful example of documenting what a package contains—and what it does not yet expose.
The household category shows how a local file-oriented tool can be adapted to hosted storage.
The creative category connects focused tools through a common hosted contract.
The subscriptions category draws a clear line between browsing retained work and running external media jobs.
The application workspace extracts a focused workflow from a larger local toolkit.
How stokes91.com, forit.us, and cgrarodeo.v39.us share a load balancer and a blue/green deployment system while keeping publishing access, hostnames, and HTTPS behavior distinct.
Part 2 of 6. Encode ABC123 as alphanumeric pairs, add parity, place the bits and inspect the selected mask.
Part 3 of 6. Work through C40 arithmetic, Reed–Solomon parity, Utah patterns and the dimensions needed to render the entire symbol.
Part 4 of 6. Trace mode choices, six-bit data words, two kinds of parity and the layers surrounding Aztec’s bullseye.
Part 5 of 6. Render the encoders’ coordinates, preserve their geometry and inspect the image bytes that an independent reader actually sees.
Part 6 of 6. Reproduce 23 successful round trips, inspect five failing edge cases and separate image fidelity from message correctness.