> And if "boilerplate" is such a bad word, how did Ruby on Rails ever succeed. It's an environment literally built on boilerplate This is not remotely true. "D

> And if "boilerplate" is such a bad word, how did Ruby on Rails ever succeed. It's an environment literally built on boilerplate This is not remotely true. "Don't Repeat Yourself" and "Convention Over Configuration" are the two core tenants of the Rails philosophy[1], both of which are intended to reduce boilerplate. This is why you don't have to specify table names, foreign key names, controller endpoint paths, view file names, etc... [1]https://edgeguides.rubyonrails.org/getting_started.html#what-is-rails-questionmark https://edgeguides.rubyonrails.org/getting_started.html#what...