ZNznowi·Dec 25, 2013Submission
2 points · Open discussionrubocop
ruby-style-guide
Learning & Reference2011–2021
rubocop / ruby-style-guide
ruby-style-guide
A community-driven Ruby coding style guide
24Distinct people
25Mentions
0Explicit recommenders
16.5KGitHub stars
What to know before exploring
What it is
A community-driven Ruby coding style guide
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 6:01:08 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year25 dated mentions
Observed mentions: 2011-09-12 14:53:36 UTC to 2021-11-11 11:09:28 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2011 | 2011-01-01 00:00:00 UTC | 2012-01-01 00:00:00 UTC | 2 | 2 | 0 |
| 2012 | 2012-01-01 00:00:00 UTC | 2013-01-01 00:00:00 UTC | 2 | 1 | 1 |
| 2013 | 2013-01-01 00:00:00 UTC | 2014-01-01 00:00:00 UTC | 5 | 2 | 3 |
| 2014 | 2014-01-01 00:00:00 UTC | 2015-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 3 | 0 | 3 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 3 | 0 | 3 |
What Hacker News says
5 sourcesTo follow up on my own question (about naming being the hardest thing), here's a supporting quote towards your argument:
"The only real difficulties in programming are cache invalidation and naming things. "
-- Phil Karlton
Came across that quote as I was reading some style guidelines for Ruby. In case it's of any interest to you: https://github.com/bbatsov/ruby-style-guide#naming
In Naming programming variables, classes and other thingsI couldn't trace the origins, but I believe it comes a long way from C. In K&R it was used quite freely in the form of
while ((c = getchar()) != EOF)
In this particular case it's necessary because of operators precedence, although I can't remember whether they used extra parens when it wasn't necessary.
In ruby most style guides, including github's[1], are forked from bbatsov's[2], which had the bullet point about using assignment return value.
[1] https://github.com/styleguide/ruby
[2] https://github.com/bbatsov/ruby-style-guide
In Small Refactorings in RubyWhile I was writing that, I realised that it may come down to the definition of what constitutes a long method / variable / class name.
I have usually found that the IntelliJ defaults are enough to make the names meaningful. For Ruby, the inspection kicks in at 30 characters. Interestingly, it's referenced from the ruby style guide here: https://github.com/bbatsov/ruby-style-guide where I can't find a recommended maximum length.
We're somewhat sidetracked from the main discussion. I'm generally in favour of trying to write code that is as readable as possible. Ideally in such a way that it is understandable even without the comments.
That said, I do think that good comments are helpful and essential if you're building a library. The Spring Framework comes to mind as a project that has a great set of documentation built from the comments (
Read the rest
but also has very readable code, along with long method, variable and class names).