We caught Aaron (Ruby committer, Rails committer, wildly popular keynote speaker) and Corey (world-traveling mentor and co-founder of Code Retreat) in Melbourne at RubyConf Australia. Even though they had limited experience working together, they had no problem communicating, laughing, and coding together like old friends.
This course observes Ruby experts Aaron Patterson and Corey Haines as they code through a real-world problem. You'll learn object design using the Ruby language, pair programming, test-driven development, problem solving, and how the 7-11 chain of stores got its name. Although this video has many laughs, don't underestimate the quality of code that two experienced developers can write while focused on solving the same task. Their use of Ruby objects will change the way you design your own applications.
Introduction [Autogenerated] It's a code. This is a special play by play. Our first pair of programming session. We filmed a rare meeting between Ruby commit er, Erin Patterson and World traveling code mentor Cory Haynes while it ruby confident. Melbourne, Australia Here's the task. They talked, coded and laughed through a fuzzy error reporting system. It's easy to catch one time blatant errors in a program, but how can one detect a synchronous errors involving third party Web service is? Here's a story. A few weeks ago, it peep code. We noticed that customers being sent to an external payment system were never returning back to our site. We'd set up a Ural handler to match the remote sites a p I, but the remote site wasn't calling it. This system should detect and report on these asynchronous silent, hard to detect errors. It will mark the beginning of an event such as send customer to payment and the end of an event such as payment completed if fewer than 50% events are completed within a six hour window and error will be logged. Even though they had never worked together, Cory and Aaron communicated well. They used screen sharing on two laptops but sometimes prefer an extra keyboard on one. They used T. D D. They used Ruby objects but built in a hook for an optional external persistence mechanism. As with every play by play, we won't pause to explain what's happening. Look for how they think through the design and what they do when they run into problems. Also, look for the follow up video, where re factoring specialist Ben Orenstein re factors their coat.