Five small tools I reach for when text is the problem. A messy query at 2 AM, two files that should match and do not, a string that needs to be a variable name, a README I want to see rendered, a character that keeps breaking a payload. Paste it in, fix it here, copy it out.
I paste a query that came out of a log or a ticket as one long line, and this lays it out so I can read it. Keywords go uppercase, each clause starts a new line, and nested brackets get indented.
Two versions of the same text, side by side in my head, never works. I paste the old one on the left and the new one on the right. Lines that changed get flagged, lines that stayed put stay quiet.
One string, every case I actually use. I type a name once and get the variable, the constant, the class, the URL slug, and the heading, all at once, instead of retyping it five times and typoing one of them.
| camelCase | |
| PascalCase | |
| snake_case | |
| kebab-case | |
| Title Case | |
| UPPER CASE | |
| lower case | |
| SCREAMING_SNAKE |
I write a README or a runbook note in Markdown and want to see it the way a reader will, before I push it. This renders the common bits: headings, bold, italic, code, lists, links, quotes, and rules.
A quote or an ampersand in the wrong place has broken more of my payloads than any real bug. I pick the format, escape or unescape, and check the result before it goes into a config, a URL, or a JSON body.