> Have you found ways to make the extended engineering of Rails easier to understand for those used to limiting themselves to the out-of-box conventions? Rails

> Have you found ways to make the extended engineering of Rails easier to understand for those used to limiting themselves to the out-of-box conventions? Rails comes with a lot of the patterns I implement out of the box. Forms are just ActiveModel objects. Services are just POROs, as are queries. A decorator pattern can be done in 25 lines of code (https://gist.github.com/joshmn/87f14dc7d6b45a72bd4e3f4fb8d82259); https://gist.github.com/joshmn/87f14dc7d6b45a72bd4e3f4fb8d82... Commands are a bit more difficult but anything that can respond to context with flow control handling is easy to grep. There's a fine line between implementing patterns and implementing patterns that behave as Rails expects them to. Thankfully, as mentioned in Eileen's talk, Rails makes it really easy to do this. While the underlying logic may not be documented on the Rails Getting Started guides, peaking under the hood isn't as intimidating as one would think.