You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Development is slowing down and the codebase is starting to creak under its own weight. I want to take some time to clean up, rearrange, and refactor the codebase, so that development can continue happily. It's also time to rethink some fundamentals of our architecture, particularly the way we use Rails.
This issue is a placeholder for my thoughts on how we can handle this; I'll update it as I make some decisions.
Firstly, here are the current major pain points:
slow tests, especially feature tests, ESPECIALLY feature tests that use javascript.
no clear structure to the view layer and separation of concerns between models and display logic.
tight coupling between HTTP and the app's business logic.
very tight coupling between the business logic and the persistence layer.
huge and unwieldy routes file that should probably be split up.
slow compile time for JS. We're still split between this weird "asset pipeline + NPM" approach that really needs to go.
Rails autoloader is causing more and more problems.
And the biggest problem of all: a combination of points 3 and 4 above means that it's practically impossible to test anything in isolation, and we have to load the entire damn rails environment just to run a simple spec file. This is the number one problem I want to solve (and, as I'm slowly starting to understand, it's largely the result of poor design choices within Rails itself)
The text was updated successfully, but these errors were encountered:
Development is slowing down and the codebase is starting to creak under its own weight. I want to take some time to clean up, rearrange, and refactor the codebase, so that development can continue happily. It's also time to rethink some fundamentals of our architecture, particularly the way we use Rails.
This issue is a placeholder for my thoughts on how we can handle this; I'll update it as I make some decisions.
Firstly, here are the current major pain points:
And the biggest problem of all: a combination of points 3 and 4 above means that it's practically impossible to test anything in isolation, and we have to load the entire damn rails environment just to run a simple spec file. This is the number one problem I want to solve (and, as I'm slowly starting to understand, it's largely the result of poor design choices within Rails itself)
The text was updated successfully, but these errors were encountered: