2 ms·
TDD advocates: build a new framework that extends Rails, one that makes it easy to add service layers and fast tests. IMHO fat models are the new PHP, and gian
by andyl 12y ago
TDD advocates: build a new framework that extends Rails, one that makes it easy to add service layers and fast tests.
IMHO fat models are the new PHP, and giant classes suck. Its time for new conventions to emerge.
Prove DHH wrong with working code, not blog posts or books or conference talks.
- mbillie1 12y ago> Prove DHH wrong with working code, not blog posts or books or conference talks. I completely agree; I will only say that it actually is quite easy to add service layers and fast tests to Rails applications - you just don't stick everything inside ActiveRecord like DHH would like you to :)
- tzaman 12y agoYou don't need a new framework to easily add service layers and fast tests. That comes with some proper planning before writing the code. And the conventions are there for decades as well, developers just need to be aware of them a bit more.
- programminggeek 12y agoI did this about a year ago, but doesn't really extend or care about rails at all. http://obvious.retromocha.com http://obvious.retromocha.com The only "framework" part that you need outside of some reasonable OOP design principles is some amount of type checking to enforce some notion of boundaries. Ruby is super weak in this area, so I added some bits to do that. For the record, until you experience the trouble that the MVC Big Ball of Fat Models or Controllers gets you to, you probably won't have much appreciation for the service/command style or the hexagonal ports/adapters style. At least, that's been my experience with other developers.