Rails Book Chapter Review

Welcome! And thank you for your interest in helping review some of the chapters for my book "Optimize for Change". This book is a collection of patterns, ideas, decisions and behaviors that Rails developers can leverage to write less software and have higher volume, higher quality, and faster development in the changes they release to users. I've accumulated these patterns over my 15+ year career as a rails developer, working across dozens of code bases and a range of teams with both great design decisions and bad ones. I've experienced what speeds up application development and what slows it down, and want to offer developers new perspectives and ideas for leveraging Rails to it's maximal potential for development speed. Below is the Table of contents. Let me know which ones you'd be interested in and I will send you one chapter at a time as a dedicated google doc for you to leave your comments in. Most chapters are a few pages long. Chapters that end with a * in their name are lengthy. I'd love to hear what you think, so i can write a better book. Reviewers will also get a free copy of the book when it is released! **Part I: Theory** 1. Complexity Amplification 2. Systems Thinking 3. Higher Order Thinking **Part II: Frontend** 4. CSS Frameworks 5. Hotwire 6. Turbo Native & Strada 7. Partials & View Components 8. Feature Flagging **Part III: Backend** 9. Refactoring* 10. Design Patterns* 11. Flexible Tests 12. Scientist 13. Modularizing Rails **Part IV: Modeling** 14. Composable Modeling 15. Immutable Records 16. Persist Domain Boundaries **Part V: Process** 17. Introducing Change 18. Strangler Fig 19. Linters 20. Follow up Work 21. Pull Requests