UUID Versions When Logging Request IDs
TL;DR: Request IDs that look like UUIDs are not all interchangeable—v4 is random, v1 embeds time and node bits, v7 orders by time. Pick a version for correlation logs on…
TL;DR: Request IDs that look like UUIDs are not all interchangeable—v4 is random, v1 embeds time and node bits, v7 orders by time. Pick a version for correlation logs on…
TL;DR: Raw spaces, ampersands, and non-ASCII in query values break when pasted into tickets, Slack, or email clients. Encode parameter values, keep delimiters literal, and decode only when inspecting. A…
TL;DR: Most “wrong timestamp” bugs are unit mistakes—seconds versus milliseconds—or time zone display issues, not a broken backend. Convert the raw epoch with a trusted browser tool, compare to UTC,…
TL;DR: Base64 makes binary and awkward characters travel safely through JSON and HTTP headers—it does not hide anything from a curious reader. Encode for transport, store real secrets in a…
TL;DR: Vendors publish SHA-256 or SHA-512 fingerprints so you can confirm a file arrived intact and untampered. Hash the download locally with a browser hash tool, compare case-insensitively to the…
TL;DR: Minified JSON saves bytes but hides typos in field names and missing commas. Pretty-print with stable key order, validate syntax, then paste into tickets or pull requests. Use the…
Eight lines, each with the job, the required input, and a limitation. Leave everything else on the homepage.
Compare two converters on one sample and keep the page whose output matches the system that will read it.
Use a phone for one-line lookups. Use a desktop for long pastes, wide tables, and anything you must compare.
Hidden characters and truncated fields cause most garbled pastes. Inspect a plain-text copy, then compare length.