Developer Tools for Formatting, Encoding and Testing

These are the small utilities that sit between larger pieces of work: checking why an API response will not parse, decoding a token to see what is actually in it, or confirming a regular expression matches what you think it does before it reaches production.

Developer Tools (27)

Guides for This Topic

Formatting Is How You Find the Error

A minified JSON payload hides its own mistakes. Running it through a formatter both indents the structure and reports exactly where parsing failed, which is usually a trailing comma, an unescaped quote, or a single quote where the specification requires double. Reading the raw string looking for the problem is far slower than letting a parser point at the character.

Encoding Is Not Encryption

Base64 and URL encoding make data safe to transport; they do nothing to protect it. Anyone can decode either in seconds. A JWT is the same story: its payload is Base64 and readable by anyone holding the token. The signature proves the token was not altered, but it does not hide the contents, so nothing secret belongs in a JWT payload.

Hashing Choices Depend on Purpose

For checking that a file downloaded intact, a fast hash like SHA-256 is the right tool. For storing passwords, fast is exactly wrong, because it lets an attacker try billions of guesses. Password storage wants a deliberately slow algorithm such as bcrypt, with a work factor that can be raised as hardware improves. MD5 and SHA-1 should not be used for either job any more.

Test Patterns Against Real Data

A regular expression that works on three hand-written examples will meet inputs you did not imagine: empty strings, unicode, unexpected whitespace, and text far longer than you planned for. Testing against realistic samples before deploying catches the cases that would otherwise surface as production bugs.

Other Categories