Lightning Talks from Dorian Marie
summary
Claims that Ruby on Rails code gains modularity by enforcing package boundaries using the pack work gem, shows the actual files and config needed (a package.tml per package and adding components to the load path), demonstrates running a linter called backward check that reports dependency and privacy violations, and uses an automatic updater to register and fix violations so the example app becomes clean and the enforcement actually works.
AI-written summary · about
chapters (4)
related talks
36mRails Core Panel Discussion
27mLaying the Cultural and Technical Foundation for Big Rails
38mAll you need is Rails (Engines): Compartmentalising your Monolith
31mWhat Comes After MVC
20mMaster the Rails Asset Pipeline: Best Practices for Apps & Gems
33mRefactoring Towards Component-based Rails Architectures
39mModularization techniques from monolithic to multi-packages app
41mOff the Tracks - Challenging the Rails Mindset