Even if you're not technical, it should be possible for you to learn how to write a good bug report if you're interested and as a longtime developer I can tell you from experience that a really good bug report is a real delight to receive.

[–] shrek_is_love@lemmy.ml 9 points 2 days ago

And if you're specifically seeking out bugs, many open source projects provide some form of beta or nightly releases that need special attention before they ship it as an official release.

[–] Ulrich@feddit.org 7 points 1 day ago (1 children)

Do you have any resources for that?

[–] darklamer@feddit.org 10 points 1 day ago (2 children)

Simon Tatham wrote this several decades ago, but I still think it's all excellent advice:

https://www.chiark.greenend.org.uk/~sgtatham/bugs.html

[–] Username85920@lemmy.ml 3 points 1 day ago

Thank you for the resource! I'll also try bug triage. It looks like a good way to learn what is useful for developpers

[–] gothic_lemons@lemmy.world 5 points 1 day ago

Just read it can confirm it's excellent advice as someone who written quite a few bug reports. Thanks for posting! Might share it at work. Maybe then I won't be the one who submitts 95% of the teams bug reports😭