Tutorials, deep-dives, and privacy-first thinking about developer tools.
Showing 1–12 of 28 posts
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.
Converting snake_case to camelCase is trivial until acronyms and digits arrive. The boundary rule, the round-trips that lose data, and where to convert.
Bacon Ipsum, Cat Ipsum and Hipster Ipsum swap Latin for themed filler. Here is when a themed generator helps a mockup, and when it quietly wrecks one.
A practical guide to converting camelCase to snake_case: the regex that works, the acronym rule that breaks it, and why round-tripping loses information.
Lorem Ipsum makes every layout look finished. Here is exactly what filler text hides in a design review, and when to swap it for real or difficult content.
A classroom timer has to be readable from the back row, stay awake and make a noise. Here is the fullscreen browser setup that does all three.