Write down steps you take to test a feature. We call that a test plan. 

For example, if you want to the functionality of creating a note in a Nostr client, you might create many test cases within that plan. 

“Create a text note”
“Create a note with text and a link”
“Create a note with text and an image upload”
“Create a note of only an image upload”
and so on. 

Try to think of all the different paths a user can take and write down each step for that path. 

Then, run through your tests and if anything odd happens, write it down. It’s helpful to write down the Expected behavior and the Actual behavior. 

Do that for you Nostr client and you’ll see what it’s like to be a tester. You could look for QA roles at software companies and show them your test plan and experience you’ve gained already. 

 Use Firefox, turn on uBlock:Origin, watch the world crumble when you claw back a tiny bit of screen real estate and privacy. As a tangent, I've noticed JavaScript that ChatGPT provides breaks on FF (in my very limited testing.) The sad thing is that most companies ignore well meaning netizens who bother to document and reach out to fix things. I usually lump companies that behave this way in with companies that practice more obvious dark patterns - Here's looking at you FAANG and wannabes!