Automating Best Practices in Rails

A quick overview of why automating best practices is a good idea and how to do so for Rails applications

Transcript

1. Automating Best Practices or “How to make jerks out of robots” @adarshp
2. Best Practices: Why do they matter? • Developer Happiness (save money on recruiting) • Faster Development (more return on your developer dollar) • Fewer Bugs (save money by reducing customer churn)
3. “Refactoring: Improving the Design of Existing Code” Martin Fowler, Kent Beck, John Brant (2012) “I'm not a great programmer; I'm just a good programmer with great habits” -Kent Beck
4. What best practices do we adhere to now? What best practices should we adopt? How much do we believe this “best practices” ?
5. Ok great: We agreed to never use trailing conditionals. How do we enforce this?
7. Write (editors, CLIs) Commit (git hooks) Submit (CI services) Ruby (Style) SCSS JavaScript Testing RuboCop CI (Circle, Travis) SCSS-lint js-hint Overcommit CI (Circle, Travis) SimpleCov Hound Ruby (Quality) RubyCritic, Flog/Flay/Reek, rails_best_practices Code Climate Security brakeman, bundler-audit CI (Circle, Travis) CI (Circle, Travis)