Some of the patterns used while building Reverb.com's large codebase including concepts from DCI and Clean Architecture such as Use Cases, Roles, Events…
James Coplien(@jcoplien), thankfully, gave us a talk titled "DCI and Ruby — the current DCI language of choice". Which was arranged by @kakutani to, I guess, let us, Japanese Rubyists, know about true DCI concept given by its main advocator. Thanks guys for the great opportunity. Here, I'll wrap up what I got from today's talk. It probablly includes many misunderstanding, though. It doesn't precis
January 2, 2013 “DCI” in Ruby is completely broken Rubyists are people who generally value elegance over performance. “CPU time is cheaper than developer time!” is a mantra Rubyists have repeated for years. Performance has almost always taken a second seat to producing beautiful code, to the point that Rubyists chose what used to be (but is no longer) the slowest programming language on earth in o
In a recent reddit post and more generally on his website, Sandal raised some valid issues with DCI and in particular queried the value of DCI contexts to represent use-cases. In this article I will do my best to present some reasons as to why Contexts can be useful. What is a Context in DCI? When programming in a DCI style a context declares an interaction between a set of objects. It does this b
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
