It can be beneficial for maintenance as it helps avoid overly-large methods and monolith objects.
Might be, but (regarding ruby) not if your codebase is designed[1] and not grown. Saudi Metz does an extremely good job at explain how to use 'single responsibility' to make even huge codebases maintainable.
I believe the same is be true for smalltalk and any OO language.
[1] http://poodr.com
Re:Ruby Is Defined by Terrible Tools
by endlessvoid94 on Wednesday July 08, 2015 @01:03PM
(#9853044)
Have you tried using Smalltalk?
Am I the only one that thinks this sounds like a maintenance nightmare?
I don't understand how this could ever be a good thing.