How to effectively move an idea from your brain to someone else's brain
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 17
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
-
How to make sense of any mess (thanks @AlexAxthelm)
In the professional world — unlike in school, college, or graduate work — no one cares how hard the writer tried nor how much improvement has been demonstrated since last time. The bottom-line question, where the quality of professional writing is concerned, is simple: “Did the reader get delivery of what the writer was intending to send?” If the answer is “yes,” the writing was good enough; if “no,” it wasn’t. Therefore, to understand the language better, we should get to know as fully as possible how readers actually go about the act of interpretation.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file, test, or entry point is identified. Read the issue's two linked resources and inspect the repository's existing resource organization before deciding whether they belong there. Done is not defined by the issue, including the target location or format for any addition.
Written by the indexing model from the issue text.
Assessment
- Domain
- content, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100