Reverb.com Dev Blog | 5 architecture anti-patterns and solutions for large Rails apps

As your Ruby/Rails codebase grows, it’s important to take note of patterns that are or are not working. As we move into 2014 here at Reverb, with a year of experience in building and maintaining a large marketplace at breakneck velocity, here are our learnings. These tips assume you are growing a sizeable Rails codebase with a domain layer living outside of Rails. If you need help getting started

[a666666]

5 architecture anti-patterns and solutions for large Rails apps (via @Pocket) 同意したい、が Helper やめようぜとか自分自身に説得力が無い…

[taketyan]

大規模 Rails 開発のアーキテクチャにおけるアンチパターン。大変共感できる。ヘルパーは参照透過性大事だと思う。

[PaulYamamoto]

これはPHP5.4/PHPフレームワークでも同じだよね。"The reason is it makes it very difficult to find where your methods are coming from and to cleanly read a class definition and see its public API. "　Traitも使いすぎると訳わからなくなる。