Tutorials, deep-dives, and privacy-first thinking about developer tools.
Showing 1–12 of 33 posts
Format XML online without uploading anything. How browser formatters indent, why whitespace is risky, and when to reach for xmllint instead.
Crop a photo online the right way in 2026: pick the ratio each platform documents, understand the re-encode cost, and avoid the EXIF rotation trap.
Resize an image online by exact pixels, percentage, longest side, or preset — plus how to choose a target size, batch safely, and avoid blur.
The 15 free online developer tools worth a permanent bookmark in 2026 — JSON, JWT, diff, hashing, images and colour, all running in your browser.
Renaming every key in a JSON object breaks on nesting, arrays and collisions. Three patterns — interceptor, codegen, manual — and when each one is correct.
CONSTANT_CASE is the only naming convention environment variables reliably survive. Here is what POSIX requires, what breaks, and how to convert safely.
How many words of lorem ipsum a mockup needs depends on the container, not habit. Here is the formula, per-block targets, and why 30 words is everywhere.
REST API naming forces a choice: snake_case on the backend, camelCase in the client. Here is where to convert, what the round trip loses, and how to decide.
Lorem ipsum survived sixty years of design tooling for one reason: it fails loudly. Here is what filler text is genuinely good at, and where it costs you.
Lorem Ipsum passes every layout test, then German breaks it. Here is why Latin filler hides i18n bugs and what to paste instead before you localise.
PascalCase looks trivial until an acronym shows up. Here is what each major style guide actually requires for class names, types, and HTTP-shaped words.
camelCase vs snake_case vs kebab-case is rarely a taste question — each one is enforced somewhere. Here is the 2026 map of which convention goes where.