The Fewer the Concepts, the Better the Code

on YouTube ↗34m

" summary

Claim: minimizing the number of distinct concepts in code increases who can read and safely change it. Evidence: two Ruby implementations of the same task show RuboCop metrics flagging the idiomatic version as higher complexity while a concept count finds 13 concepts versus 9 concepts in the grotty loop, so the loop is learnable by more engineers. Tools and examples include RuboCop, RSpec, Rails routing concerns, a tax example, Stitch Fix deployment work, Twitter’s Scala School, and tradeoffs like Heroku vs RDS vs EC2.

AI-written summary · about

" chapters (12)

1. 0:00Start
2. 0:31Justin
3. 1:33Code Reviews
4. 5:02Rubocop Metrics
5. 7:23cart1.rb concepts
6. 8:14cart2.rb concepts
7. 12:08Josh's Contributions
8. 14:47Understanding
9. 17:39add_taxl.diff
10. 19:45triangle_spec.rb
11. 20:43config/routes.rb
12. 25:47Monolith vs. Microservices

" related talks

• 01h 12mRuby Best Practice PatternsRein Henrichs · Ruby Hoedown 2008
• 26mThe Dilemma of SimplicityPablo Astigarraga · Nickel City Ruby 2014
• 28mRuby for your two internal programmersJano Gonzalez · ArrrrCamp 2013
• 46mLittle SnippetsXavier Noria · EuRuKo 2016
• 32mruby best practice patternsRein Henrichs · Lone Star Ruby Conference 2008
• 36mUnfactoring From PatternsRein Henrichs · RubyConf 2008
• 35mRulesSandi Metz · Barcelona Ruby Conference 2013
• 23mMental Models for Better CodeNajaf Ali · Bath Ruby 2018