If you are not redirected automatically, please click here.
If you are not redirected automatically, please click here.
Note: This website has been deprecated and is no longer maintained. Many articles found in the Ruby community largely oversimplify the use of DCI. These articles, including my own, highlight how DCI injects Roles into objects at runtime, the essence of the DCI architecture. Many posts regard DCI in the following way: class User; end # Data module Runner # Role def run ... end end user = User.new #
“I always get so frustrated trying to dig through a project new or old, and trying to trace the flow of execution and how things fit together...” You can't afford complicated code. Writing small and easily testable methods can certainly clean things up, but as your application grows your classes start to know too much. Large classes means a large cognitive overhead for understanding how things wor
If you’re reading this, you have my permission to nag me to write up an actual post about why I’m no longer distributing Objects on Rails. In the meantime, feel free to sign up for my free email course about how most of what they told me about object-oriented programming was wrong: Lies of Object-Oriented Programming in Ruby and Rails
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く