Hacker News new | past | comments | ask | show | jobs | submit login

Don't demand, just explain. Stay positive, don't whine or despair, just explain.

File as _good a bug report as you can_, which means taking _extra time_ on your side to do so. The ultimate is a bug report with a failing test case and/or demonstration app.

By the time you're there, you're often more than half a way to actually fixing the bug and sending a PR/patch, which is of course great too, but not neccesary to be a good bug reporter.

But do as much work as you can when filing the bug to save as much time as you can from the responder. Clearly describe the context and problem, what happened that you think was wrong, what you expected to happen as 'right'. And actual code demonstration in the form of failing test or demo app is _amazing_.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: