Skip to content
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

Add Philosophy Section #31

Merged
merged 1 commit into from
Feb 15, 2019
Merged

Add Philosophy Section #31

merged 1 commit into from
Feb 15, 2019

Conversation

danfrenette
Copy link
Contributor

This was excerpted from something Kevin wrote in which he lamented that we should add this to the README, so here we are. Slight tweaks for grammar and punctuation have been made.

The content of this text is not made to be final, but I think it's a good jumping off point that sums up our relationship with a robot that yells at us for putting parentheses in the wrong place.

README.md Outdated
@@ -120,6 +120,10 @@ gnar-style provides defaults for three different scenarios. You can specify whic
* `rubocop_rails.yml` - Styling for use in a rails project.
* `rubocop_gem.yml` - Styling for use in a gem.

## Philosophy

Our adherence to our style guide is based on the general case, and not to ensure there are no exceptions. Our philosophy is to use the guide precisely in that way - as a guide. It's not meant as a command that must be taken, but a suggestion to be considered. To the extent that things make sense sometimes - great, let's deviate. However, having rubocop start the discussion and if nothing else, having the author justify to themselves why this deviation is warranted, can be valuable.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thought this might be a little clearer

Suggested change
Our adherence to our style guide is based on the general case, and not to ensure there are no exceptions. Our philosophy is to use the guide precisely in that way - as a guide. It's not meant as a command that must be taken, but a suggestion to be considered. To the extent that things make sense sometimes - great, let's deviate. However, having rubocop start the discussion and if nothing else, having the author justify to themselves why this deviation is warranted, can be valuable.
Our adherence to our style guide is based on the general case, and not to ensure there are no exceptions. Our philosophy is to use the guide precisely in that way - as a guide. It's not meant as a command that must be taken, but a suggestion to be considered. To the extent that deviations make sense sometimes - great, let's deviate. However, having rubocop start the discussion and if nothing else, having the author justify to themselves why this deviation is warranted, can be valuable.

Copy link
Contributor

@apalmer0 apalmer0 Feb 14, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

that comment isn't super clear. I just changed this:

To the extent that things make sense sometimes

to

To the extent that deviations make sense sometimes

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Grateful for the follow-up comment 👍 and I agree this is more explicit.

Copy link
Contributor

@apalmer0 apalmer0 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I feel like other people should read this and share their thoughts on it, but at least from my point of view it looks good

README.md Outdated
@@ -120,6 +120,10 @@ gnar-style provides defaults for three different scenarios. You can specify whic
* `rubocop_rails.yml` - Styling for use in a rails project.
* `rubocop_gem.yml` - Styling for use in a gem.

## Philosophy

Our adherence to our style guide is based on the general case, and not to ensure there are no exceptions. Our philosophy is to use the guide precisely in that way - as a guide. It's not meant as a command that must be taken, but a suggestion to be considered. To the extent that deviations make sense sometimes - great, let's deviate. However, having rubocop start the discussion and if nothing else, having the author justify to themselves why this deviation is warranted, can be valuable.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Our adherence to our style guide is based on the general case, and not to ensure there are no exceptions. Our philosophy is to use the guide precisely in that way - as a guide. It's not meant as a command that must be taken, but a suggestion to be considered. To the extent that deviations make sense sometimes - great, let's deviate. However, having rubocop start the discussion and if nothing else, having the author justify to themselves why this deviation is warranted, can be valuable.
Our adherence to our style guide is based on the general case, and not to ensure there are no exceptions. Our philosophy is to use the guide precisely in that way - as a guide. It's not meant as a command that must be taken, but a suggestion to be considered. To the extent that deviations make sense sometimes - great, deviate. However, having rubocop start the discussion and if nothing else, having the author justify to themselves why this deviation is warranted, can be valuable.

This was excerpted from [something Kevin
wrote](#27 (comment)) in which he lamented that
we should really add this to the README, so here we are. Slight tweaks
for grammar and punctuation have been made.
@danfrenette danfrenette merged commit 971fe19 into master Feb 15, 2019
@danfrenette
Copy link
Contributor Author

Seems like pretty solid amount of agreement here. Merged!

@kevin-j-m kevin-j-m deleted the readme-philosophy-section branch March 14, 2019 18:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants