You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
-
5I regret that I have but one upvote to give. I was very surprised to discover that apparently a lot of the programmers here have never heard of "iff" given how useful and common it is. But I agree wholeheartedly with your second point: it's not their fault when no one taught them something before, and the solution is to teach them now.Ray– Ray2024-11-18 16:03:23 +00:00Commented Nov 18, 2024 at 16:03
-
7@Miss_Understands "you can download believe the common read doesn't. till you're writing for" - what? I can't parse your comment.Bergi– Bergi2024-11-18 22:18:16 +00:00Commented Nov 18, 2024 at 22:18
-
4There are times when I want to read documentation to understand a piece of code, and there are times when I want to learn useful (but inessential) new words. The overlap between these is virtually zero.Sneftel– Sneftel2024-11-19 14:08:27 +00:00Commented Nov 19, 2024 at 14:08
-
4@Sneftel I'd say the whole point of documentation is to learn things, which includes not only code but also ways to talk about code. Of course what you don't want is anything that unnecessarily distracts from the information that you're actually searching for, but the nice thing about "iff" is that it has low distraction and confusion potential for those who don't understand it. Meanwhile, for those who do understand it it's a time saver because it makes the statement unambiguous without introducing boilerplate that would make the documentation unwieldier to read than it needs to be.leftaroundabout– leftaroundabout2024-11-19 14:30:00 +00:00Commented Nov 19, 2024 at 14:30
-
3"which includes not only code but also ways to talk about code"... no. If I am reading documentation about a particular piece of code, I only want to learn about that particular piece of code. If I want you to give me an inessential vocabulary lesson, I will ask you for one.Sneftel– Sneftel2024-11-19 17:31:29 +00:00Commented Nov 19, 2024 at 17:31
|
Show 3 more comments
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
-
create code fences with backticks ` or tildes ~
```
like so
``` -
add language identifier to highlight code
```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible)
<https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. design-patterns), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you