How to report bugs (if you want them fixed) ↦
most of the time engineers get poor bug reports that they cannot act upon, which results in either the bug not getting fixed at all or additional communication between departments needed, that can be easily avoided with a good bug report.
This is a nice bug report template you can share with folks in your life (especially non-technical ones) to help them get better results when reporting bugs. Wash it down with JS Party #93 where we spend the entire episode discussing communication skills for coders.
Sign in or Join to comment or subscribe
Jordi Cabot Sagrera
I’m an ICREA Research Professor at Internet Interdisciplinary Institute, the Research center of the Open University of Catalonia (UOC) where I’m leading the SOM Research Lab. Previously, I’ve been at École des Mines de Nantes, Inria, Technical University of Catalonia, University of Toronto and Politecnico di Milano.
My research falls into the broad area of systems and software engineering, especially promoting the rigorous use of software models and engineering principles in all software engineering tasks while keeping an eye on the most unpredictable element in any project: the people involved in it.
I think an interesting complementary option is to let the users create the bug report from within the communication tools they already use. For instance, here : https://livablesoftware.com/slack-chatbot-github-repositories/ , we show how users could open a bug report from slack, with the chabot asking the right questions to make sure the bug report includes all the required info.
Jerod co-hosts The Changelog, crashes JS Party, and takes out the trash (his old code) once in awhile.
I agree, that’s a a great way to meet users where they are and help them report the issue in a way that’s easily consumed by the receiver. Thanks for sharing!