Developer & Text Tools

Developer utilities explained: JSON, Base64, QR codes, and hashes

These tools remove the small frictions that interrupt coding. Paste a minified API response into a JSON formatter to pretty-print, validate, and locate the missing comma or trailing bracket behind a “Unexpected token” error — for example, spotting that `name` was quoted with backticks instead of double quotes. Validated JSON also reveals type bugs early, such as zip codes sent as numbers (90210) losing a leading zero that strings (“02139”) preserve.

Encoding tools bridge text and transport. Base64 turns binary into plain ASCII — “Hi” becomes “SGk=” — which is how small images embed in CSS data URIs, email attachments survive SMTP, and Basic Auth headers carry credentials. Remember it is encoding, not encryption: anyone can decode it, so never treat Base64 as security. For sharing, a QR code generator turns a long URL like https://example.com/menu?table=14 into a scannable code for tables, packaging, or Wi-Fi onboarding, with error correction keeping codes readable even when a logo overlays 20–30% of the symbol.

Hashing answers a different question: “Did this change?” A SHA-256 digest like 9f86d081884c7d65… uniquely fingerprints a file, so comparing hashes after a download verifies integrity, checksums in CI catch corrupted artifacts, and salted password hashes (bcrypt, Argon2) let servers verify logins without storing passwords. Use MD5 only for non-security checks — it is broken for collision resistance — and prefer SHA-256 or SHA-512 for verification. Together, formatting, encoding, QR, and hash tools cover the daily loop of debug, transmit, share, and verify. The same toolbox handles the surrounding chores: URL-encoding a query string so spaces and ampersands survive transit, stamping events with Unix timestamps, minting UUID v4 identifiers for database rows, and checking password strength before shipping credentials to production.