The ability to write a good bug report is so much more important than the bug report itself.
More often than not, a shoddy bug report is going to get closed offhand, despite the validity of the bug itself. Most developers don’t have the time to parse through and guess at what the report actually means, and they certainly don’t have the ability to “fix” something if they don’t know what it is they’re fixing. This is especially true if you ever try to open an issue with an open source project — for better or for worse. Continue reading