サクサク読めて、アプリ限定の機能も多数!
トップへ戻る
パリ五輪
www.dan-manges.com
I paired with Yogi today on a few Rake tasks for our build. I mistakenly thought a Rake task could be overwritten by redefining it. That behavior may not be expected for build tasks, but it would be analogous to defining methods in Ruby: class Person def first_name "Yogi" end def first_name "Dan" end end Person.new.first_name #=> "Dan" For custom Rake tasks, you shouldn't need to modify them after
I saw the warning issued on Ola's blog: don't overuse instance_eval. JEG II blogged about a compromise, and why had an idea. But I like variation of Jim Weirich's MethodDirector. how instance_eval works If you're not familiar with instance_eval, it evaluates a block of code with self set to the object that's receiving the instance_eval call. Here's an example. add_two = Proc.new { self + 2 } puts
Before we went live with the new Rails site at CarePages, we decided to use Munin for monitoring. We needed to write a few custom plugins to visualize application health. Fortunately, Munin plugins are really easy to write - I'll provide the source for a couple of them. We wrote plugins for Passenger process status, Passenger memory stats, Rails response time, Rails hits, the ARMailer queue, and t
Note: Even if you're familiar with benchmarking and profiling, take a look at the profiling section of this post. There's a nice helper method and an interesting real world example. Improving the runtime for a page from 0.75 to 0.25 seconds may not make much of a difference to the end user's experience. But it triples the number of requests that your app servers can handle. This post covers improv
このページを最初にブックマークしてみませんか?
『www.dan-manges.com』の新着エントリーを見る
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く