Isabella

Isabella

Product Analytics Specialist

About

Using data to drive product decisions and improve user experiences. My work involves setting up analytics frameworks and interpreting data insights.

Badges

Tastemaker
Tastemaker
Gone streaking
Gone streaking

Forums

What's the one dev tool tab you ALWAYS have open?

Quick confession I opened my browser today and counted
14 tabs. 9 of them were "utility" sites:
- 2 different JSON formatters (one for big files, one prettier)
- A JWT decoder
- A base64 encoder
- A regex tester
- A UUID generator
- A cron expression parser
- Two SQL formatters (because one doesn't do BigQuery)
Every single one has ads. Half of them upload my data to
"the cloud" for a task that's literally 3 lines of JavaScript.
Here's what's wild I've been doing this for 8+ years.
Every dev I know does this. We just accept it.
So I wanted to ask the PH community:
1. What's the ONE utility tool tab you can never close?
2. Have you ever pasted something sensitive (JWT, API
response, DB dump) into a random online tool and later
thought "wait... where did that data just go?"
3. If you could merge 5 of these tools into one keyboard
shortcut ( K style), which 5 would they be?
Genuinely curious what your daily "utility stack" looks
like I've been building something in this space and
the patterns I'm seeing are wild.
(No link drop this is a real question. Happy to share
what I'm working on in the comments if anyone's curious.)

I fixed the same bug all night in my dreams. Nothing was committed.

Woke up tired like I'd worked a full shift. Same bug, looping, my brain solving it ten slightly different wrong ways until morning. Git log empty. Nothing real happened.

Part of me took it as proof I care about what I'm building. The other part knows a brain that won't clock out isn't a flex, it's a leak.

Do you get this one? And if you do, what actually makes it stop?

6d ago

Anyone actually checked their vibe-coded app for security holes, or just hoping for the best?

Been thinking about this after seeing a few posts here about vibe-coded apps breaking in production. Auth bugs, webhook failures, that kind of thing.

What worries me more is the stuff that doesn't break loudly. No error, no crash, it just quietly leaks data or accepts requests it shouldn't. Things like exposed API keys sitting in the frontend bundle, missing rate limits, or database rules that let any logged in user read rows that aren't theirs. None of that throws an error. It just sits there until someone finds it.

For the non-engineers building real products with this stuff, what does your actual security check look like before you launch. Are you running anything to scan for this, paying someone to review it once, asking the AI itself to audit its own code, or just shipping and hoping nothing bad happens.

Curious if there is an actual workflow people are settled on, or if this is still the part everyone quietly skips.

View more