Tutorials, deep-dives, and privacy-first thinking about developer tools.
Showing 1–12 of 105 posts
Privacy-first Lorem Ipsum means your filler text never leaves the browser. Here is why server-side generators are a needless request, and how to check.
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.
XMLHttpRequest becomes xml_http_request only if your converter knows where the acronym ends. Here is the boundary rule, the regex, and what style guides say.
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.
kebab-case shows up in CSS properties, URL slugs, and command-line flags for reasons that are not stylistic. Here is what the specs actually require.
Every lorem ipsum generator is a small word bank plus a few rules. Here is the actual algorithm: 182 Latin words, sentence windows, commas, punctuation.
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.
Lorem Ipsum Markdown that survives the renderer: which blocks to fill, the characters that quietly become syntax, and how filler behaves on import to Notion.
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.