Use local utilities for quick inspection
Developer workflows often involve pasted JSON, CSV, XML, YAML, URLs, tokens, sample data, stack traces, and config snippets. Browser-based tools are useful for quick inspection when the transformation can run inside the tab.
The main habit is data hygiene. Remove secrets, customer data, session tokens, and internal hostnames before using any tool, even a local-first one.
- Format and validate snippets before debugging parser errors.
- Use generators for sample data instead of copying production records.
- Separate local transformations from live lookup tools like DNS or WHOIS.
Formatting is not validation
A formatter can make JSON or SQL easier to read, but it does not prove the data is semantically correct. Validation checks syntax; schema checks structure; application tests confirm behavior.
For CSV, YAML, and XML, inspect edge cases like quoting, indentation, mixed text, empty rows, and special characters. Small formatting differences can change how another system reads the data.
Know when a tool needs the network
Most formatters, encoders, diff tools, generators, and validators can run locally. DNS lookup, WHOIS lookup, HTTP header checks, and public IP detection need live external data by definition.
Treat those categories differently. A file or pasted snippet tool should avoid unnecessary network use, while a lookup tool should clearly describe the public request it makes.