Some time ago I talked about how to write good bug reports. Today, I've found an essay that describes this process in great detail; you can find it here, written by Simon Tatham.
Related to this, I also found an article that explains how to make good questions; i.e., to not annoy the person that may answer you - it focuses on hackers answering - and to provide enough information to make your question complete. You can find it here, written by Eric S. Raymond.
These documents are not short, but they are worth reading, really. Even if you think you do good questions and write good bug reports, you'll surely find something in them to improve your style.
Featured software
Featured posts
- Fast machines, slow machines
- EndBASIC 0.10: Core language, evolved
- Farewell, Microsoft; hello, Snowflake!
- Rust is hard, yes, but does it matter?
- Rust traits and dependency injection
- A year on Windows: Introduction
- Always be quitting
- How does Google keep build times low?
- How does Google avoid clean builds?
- Unit-testing a console app (a text editor)
- More...
