In podcast-bike-shed-episode-5-rails-is-not-your-arch they talk about folder structure.
Maybe the problem is that folders are not the right way of thinking of things... tags is more appropriate.
With symbolic links, you can link the disparate files of a large feature together into a cohesive structure that's easier to reason about while developing, but critically also when you come back to the code in the future.
It also helps answer the question of where the feature-level documentation should go. "clarity of writing indicates clarity of thinking"