Yes. I’m not sure what you think makes you bad at writing bug reports, but here are tips I give to everyone (my day job involves working with bug reports).
Nominally, a decent bug report should have:
- the steps that got you the bug
- whether you can reproduce the bug
- what you expected to happen instead of the bug
Doing any of these things makes bug reports so much more actionable. You can do it. I believe in you!
Edit: Including a contact method so the software developer can have a conversation with you can also be helpful but not strictly required. Some bug reporting methods do this implicitly, like email bug reports and GitHub issues.
The recommendation changed from car lengths to seconds decades ago, but wasn’t well communicated fwict. I learned car lengths from my dad and then seconds when I got my motorcycle endorsement.
If everyone were leaving 2 seconds of space, it also reduces stop and go traffic that is caused, or at least exacerbated, by the traffic wave phenomenon. But that’s even less well socialized.