Quality rails coding
- 2. Before we begin... - Discussion encouraged!
- 3. Who am I? - Calum Halcrow - Ruby Developer - Rapid River Software - "There are no experts, there’s only us"
- 4. What is code quality?
- 5. What is code quality? - Extensible. - Easy to understand/modify; simple. - “bug free”; bugs almost never make it to production. - ??? (the UX itself?)
- 6. How do you achieve code quality?
- 7. How do you achieve code quality? - Single responsibility principle. - How things are named; self-documenting code. - Well thought out data model. - Code review, from humans and automated tools. - Obsessive attention to testing.
- 10. Single responsibility principle. - Apply to classes. - Apply to methods. - Implies the need to use non-model classes to perform business processes. - service objects, DCI, trailblazer?, “7 Patterns to Refactor Fat ActiveRecord Models”
- 11. How things are named; self-documenting code. - Why write documentation when someone can just read the code? - Leads to readable, understandable code. - Can show where your code needs to be simplified. - Is difficult! - Expand your English vocabulary.
- 12. Well thought out data model. - Once you’ve got this right, it will seldom change. - Rails ERD.
- 13. Code review, from humans and automated tools. - Automated tools can take you far… - rubocop (-a for auto-fixing!), CodeClimate, simplecov, rails_best_practices, brakeman, bullet, CI, ??? - …humans can take you the rest of the way. - code review (via PR), pair programming, etc.
- 14. Obsessive attention to testing. - Always be confident that a passing test suite => that your app is working. - Always be thinking “how will I test this”. - TDD? - Constantly maintain/improve your test infrastructure.
- 15. Mindset. - “Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live. Code for readability.” - John F. Woods - Go further than just making it work. - “No rush, no distractions” - Calum Halcrow !
- 16. Fin.