
Why I built my own browser-based dev tools (and why privacy matters more than I thought)
I've been a developer for years. Like most people, I had a handful of online tools I used daily — JWT decoders, JSON formatters, Base64 encoders. Open a tab, paste, copy, close. Then one day I caught myself pasting a production API token into some random website I'd never heard of. I didn't know who built it. I didn't know where my data went. I just trusted it because it showed up in Google search results. That bothered me enough to build something better. What I built ToolDock is a collection of developer tools that run entirely in your browser. No backend, no accounts, no data sent anywhere. You can verify this yourself — open DevTools Network tab while using any tool and you'll see zero outbound requests with your data. Current tools: JWT Decoder Base64 Encode/Decode JSON Formatter + Validator Regex Tester CRON Expression Parser Color Converter (HEX ↔ RGB ↔ HSL ↔ HSB) UUID Generator, Text Diff, Timestamp Converter and more (19 total) What I learned building it Browser APIs are power
Continue reading on Dev.to JavaScript
Opens in a new tab
![[Learning notes and hw] getting started with R-cnn: Manually implementing Intersection over Union (IoU)](/_next/image?url=https%3A%2F%2Fmedia2.dev.to%2Fdynamic%2Fimage%2Fwidth%3D800%252Cheight%3D%252Cfit%3Dscale-down%252Cgravity%3Dauto%252Cformat%3Dauto%2Fhttps%253A%252F%252Fdev-to-uploads.s3.amazonaws.com%252Fuploads%252Farticles%252Favit2emoxc0g68e5ltqj.jpg&w=1200&q=75)



