title: Why does rubocop or the ruby style guide prefer not to use get_ or set_?
body: <p>I was running rubocop on my project and fixing the complaints it raised.</p>
  
  <p>One particular complaint bothered me </p>
  
  <pre><code>Do not prefix reader method names with get_
  </code></pre>
  
  <p>I could not understand much from this complaint so I looked at <a href="https://github.com/bbatsov/rubocop/blob/master/lib/rubocop/cop/style/accessor_method_name.rb">source code in github</a>.</p>
  
  <p>I found this snippet </p>
  
  <pre><code>    def bad_reader_name?(method_name, args)
        method_name.start_with?('get_') &amp;&amp; args.to_a.empty?
      end
  
      def bad_writer_name?(method_name, args)
        method_name.start_with?('set_') &amp;&amp; args.to_a.one?
      end
  </code></pre>
  
  <p>So the advice or convention is as follows:</p>
  
  <p>1) Actually they advice us not to use get_ when the method does not have arguments . otherwise they allow get_</p>
  
  <p>2) And they advice us not to use set_ when the method has only one argument .otherwise they allow set_ </p>
  
  <p>What is the reason behind this convention or rule or advice?</p>