This is a tweet from someone
Don't abstract too early. Duplication is far easier to deal with than the wrong abstraction. @sandimetz (OO version of YAGNI) #railsconf
Abstractions should be used because there is a pain that needs solving, whether that be because you're talking to third party code, or slow remote calls that need hiding during testing or because there is complexity that needs hiding. Putting abstractions in before we feel any of this pain just means more code to wade through when trying to get stuff done - no thanks.This goes against current-popular-thinking as of today.
rails s -p 10524