Presenter's computer went down and it's taking forever to reboot. Stupid Mac. # rubykaigi
That's one of those rough moments where you really feel bad for the presentor. But he handled it like a champ -- continuing the presentation while he waited for his machine to boot back up. Well done. I wish I got more out of the talk but it was one of those inspirational talks that are hard to translate. The Japanese speaking audience seemed to love it.
Please use the overburdened …
Giles Bowkett - Ruby Inside's Top Presenter of 2008 - contributes a guest post:
I created a 90-minute video called How To Get A Kickass Job, Making Six Figures Working (From Home) With The Stars Of Your Community, Even If You Just Got So Fired That The Cops Hauled You Out Of The Building In Handcuffs . Part of my magic formula includes understanding Google PageRank, and the best way to understand complex, abstract mathematics is to reduce them to …
There are a couple of ways to keep it clean. Sometimes they are called " Presenter Objects" or something similar. It doesn't matter how you call them, and you don't have to use any complicated gems or libraries. Regular classes suffice.
Here's an example of a typical helper:
module PostsHelper def post_title ( post ) header_class = post. published ? ? "published" : "normal" header = content_tag ( :h2 , post. title , :class => header_class …
…difficult to test through the GUI. Sure, we had a lot of tests that drove out the implementation of the Presenter, but, it's always nice to know that the GUI is behaving, and you're driving something end to end.
Our solution — use the Strategy pattern to extract out the behaviour around how code is executed in the GUI, we use an anonymous method/delegate to pass a code block to a class that either executes it on the same thread (for our tests), or, uses ThreadPool.QueueUserWorkItem …