Back to Course Refined Ruby 0% Complete 0/0 Steps Coding with Clarity 12 Topics Incidental Change Intention Revealing Message Intention Revealing Argument Protocol Complication Loop Golf Consistency Stay Positive Stay Positive 2 Don't Use Greater-Than No Comment Plural Name Tabular Struct Refactoring with Sam Livingston-Gray Everything in its Place 8 Topics Method Dependencies Break The Circle Microconcerns Invariant Minimum Viable Method API Design for productivity Nested Class Extract Default to Method Coding for Confidence 14 Topics The Trouble With Nil Symbol Placeholder Benign Value Error Value Special Case Null Object Safe Navigation Part 1: Reliable Associations Safe Navigation Part 2: Try, Try Again Safe Navigation Part 3: Everything is Optional Safe Navigation Part 4: Refinements Safe Navigation Part 5: Adapter Partial Safe Navigation Mistake-Proof API Bouncer Method in Ruby Incremental Evolution 11 Topics Gradual Stiffening Coincidental Duplication Coincidental Duplication Redux More Coincidental Duplication Extract Command Object Macro Two Refactorings Replace Parameter with Option Where do Private Methods Come From? Tell, Don't Ask Sprout Class Conclusion and Next Steps Search (Entire Site)Search Refined Ruby Everything in its Place Minimum Viable Method Module 2, Topic 5 In Progress ← Previous Next→ Minimum Viable Method Module Progress 0% Complete Is there such a thing as a method that is too small? Is it worth it to extract a method just to satisfy a guideline like the Law of Demeter? Oop, this content isn't available to visitors. Please register or log in to continue! Or you could purchase this course.
