TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

How to help your team write better bug reports

4 pointsby maxcameronabout 15 years ago

3 comments

camwestabout 15 years ago
Max and I had a conversation about this piece and one thing we wanted to avoid was pigeonholing our bug reports into a category system like I've seen so many others do: Fill out 15 drop downs to describe the state of your machine when the bug was found. What component, what OS, browser etc… There has to be a better way than that right?
Isamuabout 15 years ago
Add a bug button on the prototype? Integrating the bug reporting means you can automatically supply a history of the last n things the user did, or whatever debugging state you think is helpful, and the user will fill in the rest. Similar to automatic crash reporting, except without requiring the crash.
评论 #1359418 未加载
maxcameronabout 15 years ago
I didn't write this for customers obviously - they deserve to report bugs in any way they want. But I think developers need to do a better job helping their team-members write better bug reports.