How do you manage your codebase once it gets large?
patio11: This is one of my periodic pain points with Rails, as compared to Java.  At the day job I work with multiple code bases with more than X00,000 lines of code each.  My Rails site has 5k lines as reported by rake stats, and due to a combination of poor IDE support compared to Java and the toss-it-all-in-one-folder Rails conventions, that sometimes results in headaches.My suggestions:1)  Refactor like it is going out of style.  Rails classes (particularly controllers and models in my experience) have a tendency to accumulate cruft over time.  Periodically evaluate whether something should be broken into two classes, or at least two files.  Mixins and require are your friend here.  (Breaking a controller into two changes URLs by default.  I think letting Rails assign publicly visible URLs is a mistake, but most people do it.  Consider carefully whether you can accept URLs changing as a result of code changes.)2)  Encourage internal code reuse, and better separation of responsibilities, by breaking things into plugins when appropriate.  I extracted code from my own classes to make A/Bingo for example.  It keeps my own classes readable and makes it much easier to publish and reuse A/Bingo.3)  Coding conventions are your friend.  Since the IDE lacks a reliable jump-to-definition-of-this-function feature, I tend to try to put predictable things in predictable places.  For example, model classes always have a consistent ordering of filters, validations, and associations at the top of the file prior to business logic.  (Those could be externalized if they got realllly messy, via the magic of require.)4)  Put partials into thematically coherent subdirectories.  This saves you from having to find the right form partial from a directory with 20 views and 50 partials.