 Okay. My name is Kobe Grandquist. To start off with, I started when I first found a Ruby in 2006. The first thing I did is I heard about the Ruby Meetups on Second Life. So I signed up for a Second Life account, and it's the only reason I went there. Those are my email addresses. I am part of the LA Ruby users group, which we are in the process of getting underway. There's a URL there for that. My side project, or one of my side projects with Carl Jungblood is Confreaks. You can see all the conferences we recorded at those URLs plus a number of others. I'm going to show you a plugin that was written by, or a plugin or a gem that was written by one of my coworkers, Jacob Dunphy. It's called Kablame. Why would you use Kablame? Basically, someone on your team isn't pulling their weight. Kablame. You can read the rest of the bullet points. I like the last one, which you'll see in just a moment is exactly why it was created. I just wanted to be a real show-off jerk who wants recognition for all the tests you write and think nobody respects you at the office. This will show them. This is Kablame ran on the web tier of YellowPages.com and Jay Dunphy's got 21,000 lines. What Kablame does is it uses either Git or SVN and the blame function within it and evaluates all of the code in the repository or in the revision you're looking at and tells you who's responsible for how many lines. Very simple. So we took it with Yehuda and we ran it against Merb. And now you have the winner of that one. So it's a simple fun utility. It's more for humor than anything else because all it does is tell you who's responsible for the number of lines in the plug-in. The other PSI reference there, I also work for YellowPages.com. We build a consumer website. We're running on Nginx with Rails. We use no active record in the web tier. We have a service tier, which is also Rails on Nginx. We use a fast search engine as a back end. Everything's very restful. And we use NoracleDB when we don't get our data from the search engine. We also develop client apps. We have an iPhone native app team. We have a web app for the iPhone. We have a number of J2ME apps that are deployable on all the handsets. We also build a ton of stuff with search and data. We have huge business listing repositories, frequent updates from a wide variety of sources. We've got a bunch of interesting R&D projects going on. We do natural language search. We've got some really fun stuff. We're planning with web crawling and voice recognition. And at YPC, we're always looking for passionate talent, including Ruby developers, co-co-developers, and other smart people. And we have desks. And if you can't see the picture there, that's actually a Russian beer. And the way I refer to it is Ruby's the only language that the Russians found awesome enough to turn into a drink. So we've got a Russian beer. And that's it. Unless somebody actually has questions about yellow pages and does Rails scale. Yeah, Brian? A question about yellow pages. Say you're using Rails in the front end and you're actually talking like some restful stuff to a Rails app on the back end. Yes. That's my one time. Yep. Anything else? Yeah? We're doing a conference in Boston in November called Voices that Matter. Yes. So Mike's here for the S&W conference on Ruby Seriously. And one of the talks is going to be a case study on Ruby in the front end. Yeah, I'll finish plugging that. I'm presenting at the professional Ruby conference in November on yellowpages.com. The big rewrite because in June of 07, yeah, June of 07, they launched a new site through a quarter million lines of Java code and replaced it with, I forget the exact count, but a lot less lines of Rails. I spent the previous, I've been at yellowpages.com for four months. I spent the two and a half years prior to that as an independent freelancer similar to Toralian. You know, basically doing work out of Sulix in Utah. I looked at yellowpages, looked at the job position and looked at the fact that somebody gave a chief architect enough autonomy to throw away a quarter million lines of Java code and figured it was worth a try. So.