Rails projects generally organize code around what type of class you're writing (generally, a Model, a View, or a Controller (Mailers, Workers, Services, Helper

Rails projects generally organize code around what type of class you're writing (generally, a Model, a View, or a Controller (Mailers, Workers, Services, Helpers are less frequently used)). Django tends to organize code by feature - signup, shopping cart, billing, profile, etc. I've seen it explained as "Component Slicing" vs "Feature Slicing" - the term has appeared when I've looked into how to organize code in React projects but it fits. It seems there are just different ways people model things in their mind and for some folks the Rails way works best, and for other folks the Django way works better.