ruby_good_practices

A series of good practices that I collect over my professional life

• Avoid external side effect in transactions
• Avoid flag argument
• Avoid putting full object in background job
• Create just enough data for test
• Do not abuse present? and blank?
• Use customized exception instead of ruby-provided exception
• Use value object instead of primitive
• Use expect instead of allow in rspec
• Use instance_double instead of double
• Use instance_double with string instead of class