-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Avoid weasel words/justification filler phrases #761
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
MatheusRich
wants to merge
2
commits into
main
Choose a base branch
from
avoid-weasel-words
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
suggestion: What you you think about inverting the framing to present the guideline in a positive lens?
I feel like your third bullet point is the core concept here, the meat of what the guideline is getting at. What would you think of surfacing that as the primary idea?
Perhaps something along the lines of:
I'd argue that avoiding filler phrases and weasel words alone won't increase the information communicated. It would remove the impression of communicated information that can lead to ambiguity. The removal would need to be coupled with added explanation/articulation of one's reasoning. Similarly, feedback that fully explained one's reasoning, yet happened to include some weasel words or filler — while being a bit verbose and having room for improvement — would fully communicate one's reasoning.
Some reasons to consider a positive framing over negative framing because:
ref - https://notes.andymatuschak.org/z63PA5ATVi8oyhyLgeGvL3p
ref - https://www.nicolecw.com/marketing/copywriting-positive-framing-negative-framing/
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm torn about that. While I like the positive framing, I fear it becomes too generic (too similar with the first bullet point in this file).
I'll let others chime in and leave their thoughts. If folks prefer the positive version, I'll update it. Thank you!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If it's similarity to other guidelines, is there an opportunity for a larger refactoring? (I can't quite think of what that might look like though).