 I almost got quieter when I said that. This is going to be a kind of game show. It's not a kind of game show you like to have over in the US. It's something a bit weird, a bit British. I can just trust me here. It's going to be an awful lot of fun. But I do need you as an audience to respond. I need you to be vocal. So we're going to try that again. And this time, you're going to make enough noise for 350 people, OK? Good afternoon, Goruko! Excellent, excellent. OK, I'm going to need three things from you all as an audience. OK? The first thing you need to know is the game we're about to play is very hard, is a huge challenge for the speakers involved. So when you feel they have done well, I need you to raise those voices, put those hands together, and let them know. OK? It's very daunting being up here. Just give them all the encouragement you can. The second thing you need to know is that the game involves challenges where the panelists will put just a little bit of criticism on what's just been said, and they're pretty subjective. So if you feel some of the challenges are a little harsh, maybe, by all means, let us know that as well. And the third thing is actually the very first thing, because each show starts exactly the same way. I'm going to boisterously welcome you all to the show. And once I've done that, I need you. I'm going to play in the piano music, which is just the theme music for the show. As soon as you hear that piano, I need you all to raise the proverbial roof. Can you do that for me, Goriko? You're getting better. OK, here it goes. Welcome to Just a Minute. That is right. Good afternoon, and welcome to a very special edition of Just a Ruby Minute, here in the spectacularly oversized fruit that is New York City, New York. My name's Andrew Faraday, and we're going to play the game of Just a Minute. It's a huge part of British culture. It's been going to our audiences for almost half a decade, and it's slowly finding a home in the Ruby community. So what's going to happen each round? I'm going to select one of these witty, insightful, and of course terrified individuals, currently arrayed before you, and give them a topic that's of some kind of interest to the Ruby development community. They'll then have to speak about that topic for 60 seconds without hesitation, including pauses or hedging noises, repetition of words other than the topic sentence they've already used in that round, or deviation where they're no longer talking about the topic. Now, if the other panelists discover these rules being broken, they can challenge by pressing their buzzers. Someone buzz for me? Excellent. Now, you'll notice one of our panelists has turned green, and the timer has stopped. So what will happen there is I will ascertain the nature of their challenge, and if they're correct, they'll gain a point for a correct challenge, and then take control of the topic, be allowed to continue speaking until the minute's over, or they are in turn challenged for exactly the same reasons. Now, whoever's speaking at the end of the minute gains a point for doing so, and if the challenge is incorrect, the original speaker gains a point for being interrupted, and is allowed to continue where they left off. Now, the end of the minute sounds just a little bit like this, and that is the whole game, a very simple set of rules, and a very difficult set of rules to follow. So now that we know the rules, let's meet the panel. First up, closest to me, we have the chief zealous officer at Coding Zeal, and in his own words, master of smile generation. Please welcome Adam Cuppey. Next up, we have got a senior engineer at Ghost Spot Check, a huge part of both Kubmo and Bridge Foundry, and this being her third panel, a Ruby Jam veteran. Please welcome Kinsey Ann Durham. Next up, we have got the co-founder and director at Ignition Works, a very prolific public speaker, and the presenter of the Ruby Book Club podcast, Nadia Odineo. Nadia. And last but certainly not least, we've got a senior developer from the New York Public Library, organiser for eight of the 10 years of Go Ruko from right here in New York, Stephen Shaw. So without any further adieu, let's move on to the first round, appropriately known as round one. Kinsey, as our returning panellists, you're up first to start, and your topic is my startup idea. So that's my startup idea, Kinsey Ann Durham, for 60 seconds, starting now. My startup idea is the best idea that anyone has ever heard of. It relates to dogs because I am obsessed with that breed of animal, and I really just want to stare at pictures of cute puppies all day. So my startup idea is to just have a website where you can look at these creatures as long as you want. Whenever you're having a bad day or you're not feeling well or... Your idea is stupid. Thoroughly mixed response there. Wait, is that one of them? No, that's not one. Oh, sorry. I forgot the rules, sorry. I don't think I can give you that within the rules of just a minute. I forgot for a moment there. An entertaining interruption, however, Kinsey, you gain a point. For being wrongly interrupted, you have 22 seconds remaining on my startup idea. Before I was rudely interrupted by my teammate to the right of me, I was talking about my startup idea. Repetition I? There was a lot of I's. So that's completely correct, Steve, you gain a point. And control the subject for 13 seconds, starting now. My startup idea is so complicated, it cannot be summed up in the short amount of time afforded. Kinsey? Hesitation. Yes, definitely hesitation there. So Kinsey, you gain an additional point. You have 3.7 seconds remaining, starting now. Anyways, back to my startup idea. So that's Kinsey and I'm showing fine fighting form, currently in the lead with 3 points. Okay, we're gonna move on. Adam Cuppey, it's your start and your subject is user stories. User stories, Adam Cuppey for 60 seconds, starting now. As we begin to speak about user stories, it reminds me of the first user story I happen to write myself. It always begins with if I want to do something of great importance and meaning, I will begin by looking specifically at the way in which the user story is structured for the user. If nothing... Kinsey? I was gonna say a repetition of story, because it's stories. Ah, did he say story twice? Yeah, it's very definitely in the rules that plural and singular are different. Hey, he said story, it's not story. Adam's got some friends in the audience. That was... That was a technically correct challenge from Kinsey and Durham. Gain a point. I don't make the rules. Hey, I wanna win. They don't like you, Kinsey, but you have 36 seconds. Hey, I was right. It doesn't matter. It was right. So you had 36 seconds starting now. I use a tool called Pivotal Tracker to write user stories at my current company called Ghost Spot Check. I really like the application and it's built in my hometown of Denver, Colorado. It's really nice to use and I can easily accept, reject. Repetition of I. Yes, that was the third I. So can I use that? So Adam, you have regained control of this topic for nine seconds starting now. I particularly prefer the use of Jira for its simplicity and raw ability to really hone in on the... Adam, speaking at the end of the minute there. So currently we have Kinsey in the lead with four. Adam trailing just behind on two. Steven's got one, Nadia's still to score. So, Steven, you're at first to speak. Your subject is how many arguments is too many? How many arguments is too many? Steven's sure, starting now. How many arguments is too many is an interesting question. It could be that you're talking about arguments with your significant other or arguments passed into a function also known as a method. Ruby has... Hesitation, yeah. That was hesitation. Man, just breathe. Give genius room. You gotta really get in there on that buzzer. You do need to breathe, but you definitely did pause. So, Adam, you have 46 seconds remaining. How many arguments is too many starting now? I believe that arguments can be summed up in a correlation between the arg and the ment of reason. Now, as we look specifically at what might be too many, we can ask ourselves, most importantly, is too many too many or is too many right many? Too many is part of the topic sentence. What? So, I didn't explain that properly at the start. The topic sentence is basically, for a game, you can repeat as much as you like within that realm. So, because that was my fault, I'm not going to award a point this time, but I am going to give control back to Adam Cuppey. You now all know the rules, so they will be kept from now on. Okay, so Adam, you have 27 seconds. How many arguments is too many starting now? Looking back at how many arguments is too many, I reconsider the notion that too many can be too many if really, arguments are summed up as part... Repetition of summed. Summed. Yes. Summed. Who thinks that was a repetition? That's a few here. Who thinks it wasn't? That is now not my fault anymore, so Adam, you gain the point and have 14 seconds remaining. How many arguments is too many starting now? Repeating back to too many arguments, I continue to add my... Repetition of I. Yes. So, Kinsey, yes, you gain the point. You currently have five and eight seconds remaining on how many arguments is too many starting now. How many arguments is too many is a very good question, and when I refer to... BUZZER Excellent, so Kinsey, you are still in the lead with six. Adam, you're trailing with four. The other two, you can join in the game soon, I'm sure. LAUGHTER So, Nadia, you're up first. Your subject is naming variables. Naming variables at Nadia starting now. I hope that I can speak very well for a minute on naming variables given that there are zero points by my name right now. When coding, it is important that your intention is very clear when naming variables. Some people like to name variables with very long descriptive names. For example, if you are coding an application to do with dogs and there are many different breeds of them in your work, then you may have a variable, which is something like German Shepherd, Terrier, Puppy... LAUGHTER ..101 Dalmatians in... No points yet and you were sitting on that. Woo! Amazing, that is absolutely so. Nadia, you gain a point for speaking at the end of the minute and another for speaking uninterrupted for a full minute. That happens very rarely and has not yet happened on Tech Jam at all. You are the first one to achieve that particular accolade. It's amazing. OK, how do you follow that? Kinsey? You are up next. And your subject is who you should be following on Twitter. Who you should be following on Twitter. So that's Kinsey and I am 60 seconds starting now. I have a very long list of different software engineers that you should be following on Twitter and they are as follows. Adam Cuppey, Nadia, Steven, Sandy Metz, Rachel Ray. LAUGHTER Hesitation? Yes, that was a hesitation. Adam, you gain a point for that. You have 38 seconds remaining. Who you should be following on Twitter starting now. I believe the people you should follow on Twitter are the attendees here at Goruko, amongst many other conferences. Please feel free to yell those out at will. First and foremost, I believe Tender Love is a great example of someone you can follow on Twitter. You can also follow, of course, Jim Bransky, Bill Jordan, Susan Sarandon, Kelly Powell, Kelly Ripa... LAUGHTER Repetition of Kelly. LAUGHTER For what it's worth, you all missed the fact he said follow more than once and the subject is following. Oh, yeah, yeah, yeah. So, you know, I'm calling you out on that one, but nobody else did. So, Kinsey, you have 10 seconds remaining. Who you should be following on Twitter starting now. Once again, as I was saying before, I was... ..I. So, Nadia, you gain a point and you have six seconds remaining. Who you should be following on Twitter starting now. I think that you shouldn't be following anybody on Twitter. So, Nadia gets quite speaking at the end of that round. And the next one's a bit of a curveball. Adam, you're at first to speak and the subject is how to write a regex. This is going to be fun, I can tell. So, Adam Cuffee, how to write a regex starting now. The first step in writing a regex is to open up the computer. From that point, you will select the IDE that is the most appropriate for the task at hand. I prefer to look specifically at the beginning of the line followed by the second character, the third character. Kinsey. Repetition of character. Repetition of character, of course. Then again, you've got to take over the subjects. Kinsey, you have 40 seconds remaining. How to write a regex starting now. How to write a regex is something that I learned from one of my fellow co-workers. His name is Ben Horn and he attended Turing School or... Deviation. Deviation. There's nothing to do with regexes. So, Nadi, you have 23 seconds remaining on how to write a regex starting now. I am going to tell you about how to write a regex. When it is time to write a regex, open up something called rubular.com. It gives you a playground where you can practice different ways to write your regex. Repetition you. There was you and there was your. Oh, those are different? Yes. So, that was the incorrect challenge. Nadi, you have an additional point and 3.6 seconds on how to write a regex starting now. It was correct, but there is less than two seconds to go. So, Kinsey, you do gain a point and you have 1.3 seconds on how to write a regex starting now. I feel so cruel for that subject. Okay, so currently Kinsey is in the lead with 10. Nadi has got 6. Adam slipped a third with 5. Steven currently on 1. Now, Steven, you are at first to speak and your subject is going to New York. So, going to New York, Steven Shaw starting now. Hesitation, correct. Help if you speak. So, Nadi, you've gained a point and the topic of going to New York for 59 seconds starting now. I really like going to New York. Let me tell you about going to New York. I go to New York for one purpose only and that is to attend Garuko, which is a fascinating conference at which all of you people are attending. Last time I was in New York was to attend Garuko. And I just realized... Kinsey. Repetition of Garuko. Of Garuko. And I. And I. And attend. And attend. Completely correct, Kinsey. So, you're currently on 11 points. You have 35 seconds on going to New York starting now. Going to New York is one of my favorite pastimes because there are a lot of people that I know here between friends like Tara, who some of you met last night, and family members that live here in Brooklyn. Going to New York is exciting. There's a lot of humans walking around. It's very crowded, unlike Denny. Repetition of Barry. Repetition of Barry, correct. So, Adam, you've regained the subject and 3.9 seconds, nearly enough four seconds, on going to New York starting now. My favorite thing in going to New York is to visit... We will never know the end of that sentence. We will never know. Okay, Nadia, you're up next. And your subject is My Talk at Garuko. So that's Nadia on My Talk at Garuko starting now. My Talk at Garuko was all about code hospitality. I want to tell you two stories about My Talk at Garuko. The first one is about the time a friend came to stay with me. She messaged saying that she wanted to move to London. I said, great, tidied up my flat, went to pick her up from the airport, created a guide for her. Repetition of her. Repetition of her, correct. That was like eight times. That was good. Sorry, I feel bad. So, yeah, Kinsey, you've got half a minute remaining on My Talk at Garuko, which hasn't happened yet, starting now. My Talk at Garuko is happening right after this panel, and I will be talking about code readability. And earlier when... Yeah, there's lots of answers there. So Nadia, you've gained a point and regained the subject for 17 seconds on My Talk at Garuko starting now. Let me tell you some more about My Talk at Garuko. Which hopefully... Kinsey. Hesitation. Hesitation, definitely. So, Kinsey, you have nine seconds. Just to be clear on repetition, you can't see anything you said earlier this round. So, nine seconds on My Talk at Garuko starting now. You all should be very excited and enthusiastic. Repetition on very again? Very again, yes. And and. I said and when you left. So, Steven's got a point. Richly deserved. Be ready to speak quickly. So, Steven Shaw has 2.5 seconds on My Talk at Garuko starting now. My Talk at Garuko has not happened. Excellent. Kinsey, you're up next. Your subject is Stack Overflow. Stack Overflow. Kinsey and Durham for 60 seconds starting now. In office in Denver, and I have the pleasure of going over there to talk to their developers, but mostly I use Stack Overflow to research things that I... Spasm in my hand. Well, that's correct. It is not one of the rules. So, Kinsey gets a point from being possibly tactically interrupted. So, Kinsey, you have 45 seconds remaining on Stack Overflow starting now. Stack Overflow for researching problems that I don't know. Repetition, that's a third eye. Yes, yeah. I'm not sure you might have repeated research. Was it research or researching? I'm not sure. Okay, that would have also been valid. Okay, Stephen. You have 39 seconds on Stack Overflow starting now. Stack Overflow is a lightweight, extensible framework for making me look more intelligent to my boss, coworkers, parents, and significant other. Not only that, but I can go home looking my son in the eye after using Stack Overflow. It's a wonderful website that provides answers to commonly posed questions in the software development community. They have a reputation for being difficult to get a job at, but have a very rewarding dental care system. Adam. Repetition of have. Have, correct. No, I cannot. For software reasons and for the rules. So, Adam, you have 2.7 seconds remaining on Stack Overflow starting now. Stack Overflow is a great story. So, Adam Cuffey speaking at the end of that minute gains a point for doing so, gets into second place, just ahead of Nadia and Stephen, and Kinsey's quite a long way ahead of all of you. Okay, Adam, you're up next to speak. Your subjects. Matt's is nice, so we are nice. We have a rule in tech jam that the real just a minute doesn't. I should explain now, you are allowed to use common short forms of the topic. So, in this case, minus one or minus one, however you choose to pronounce it, is also for gain to repeat. Of course, any of the words in the topic. So, Adam, Matt's is nice. So, we are nice. 60 seconds starting now. Minus one, minus one, minus one. However you choose to pronounce this as an acronym for Matt's is nice, so we are nice, is entirely up to you. However you choose to start. Repetition of you. Yes, repetition of you. Nadia again a point. You have 45 seconds remaining. Matt's is nice, so we are nice starting now. I have a very interesting story about minus one, which stands for Matt's is nice, so we are nice. I was at RubyConf last year in Atlanta and Matt's gave a keynote presentation about new things coming in the language and he had a slide which had minus one. Repetition had. Had, there was a few had there. So, Stephen, you gained a point and you have 21 seconds remaining. Matt's is nice, so we are nice starting now. Matt's is nice, so we are nice. Also known as metiswan, is a thought that's given out in the Ruby community and accepted as common wisdom. I've heard it echoed by fellow developers such as Joshua Knowles, Brian Helmkamp, Mike D'Alessio, and my favorite human being in the world, Luke Julia. Excellent, Stephen Shaw clawing back some points there. Slowly but surely gaining. Stephen, you are up. Accidental puns, they are the best. Okay, Stephen, you are up next to speak. Your subject is the elevator pitch. So, Stephen Shaw, 60 seconds on the elevator pitch starting now. The elevator pitch is an idea... Nadia. Hesitation. Hesitation, definitely. So, Nadia, you have 56 seconds on the elevator pitch starting now. I think we can draw interesting parallels between the elevator pitch and a just-a-minute speech. In a just-a-minute speech... Kidding? Just a minute speech. Yes, repetition of just a minute and speech. Kinsey, you gained a point. You have 46 seconds remaining on the elevator pitch starting now. The elevator pitch. The elevator pitch. The elevator pitch. The elevator pitch. That one's buzzing. I would have actually accepted a repetition challenge by that stage. We have to have some interest in the game. So, Nadia, correct. You have 39 seconds on the elevator pitch starting now. The elevator pitch is a way that you sell your start-up idea to venture capitalists. What you do is go into an elevator on the zero floor. Then you go up. Repetition. That was the third you. Yes. Yes, there was. Stephen, so you've gained a point. You have 25 seconds remaining on the elevator pitch starting now. The elevator pitch is an interesting idea in the American economy. A lot of my fellow attendees have had the opportunity to give the elevator pitch because not only are they developers, but they're entrepreneurs. Entrepreneurs such as Josh Knowles. You've been challenged. Adam. Pick one of the three. I would have gone with hesitation. Yeah, me too. Yeah, hesitation. Adam, you've gained a point. Broken into double figures. You have 12 seconds remaining starting now. An elevator pitch begins with four primary components. First, you position yourself inside of an elevator with another individual. Second. So Adam Cuppey speaking. At the end of that minute has tied once again for that all-important second-place space. Kinsey's still ahead, Stephen. Just a little bit behind. You're next to speak. Your subject is microservices. You like that one? Nadia, you have 60 seconds on microservices starting now. On microservices. Because when working at Pivotal, I was on their Cloud Foundry team. When on that... Hesitation. Hesitation. You're definitely running out of steam, I'm afraid. So, Kinsey, you have got 49 seconds on microservices starting now. Microservices is something that we are trying to implement on my team at GoSpotCheck and it's kind of been a complete mess. So I've been learning a lot and seeing different libraries such as Kafka for sending messages between different services. There's also another library called Kinesis. I haven't done anything with, but interested in checking out what it does and why. Repetition of and. There was a few answers there. So Adam, you have 12 points and 13 seconds on microservices starting now. Microservices cannot be confused with either Microsoft or Microfridges. It's important to note that as a... Nadia. Hesitation. Hesitation, definitely. So Nadia, you have 4.1 seconds on microservices starting now. At RailsConf last year... Adam. Derailment, I don't know. No H. H. Hesitation of H. Hesitation of H. I should give a point to that fellow on the front row there. Not for the topic on the board though. If you shorten microservices to DHH, you have problems. It's one word. It's not one word. There is an established form here and yes, it was repetition of H. You're not popular, but you are right. So Adam Cooper, you have half a second on the subject of microservices starting now. I would have accepted a challenge if it had come before the minute. The minute happened. 13, that's higher than 12. Yeah, so it's 14 for speaking at the end of that minute. Feel the hate there. Beautiful. Kinsey, you're next to speak. For the start of the round, your subject is Games for Developers. Games for Developers, Kinsey Andoram, 60 seconds starting now. Games for Developers is a confusing subject, but I recently watched a talk by Ernie Miller at Nordic Ruby about video games and how they relate to developers and the tool of that developer. I think the audience has it. Once again, not my fault. So Adam, you've gained a point. You are just creeping up on Kinsey at this stage. It's getting interesting. Adam, you've got the subject of Games for Developers and 44 seconds starting now. The available Games for Developers are quite extensive, but I'm not going to bother to go through that list now. Instead, what I'll talk about is the start of Games for Developers begins at the point in which you have an idea, and then that individual chooses to move on to the next thought within the framework of the game itself. For Games with Developers and for Developers, I've decided to sit on the topic of what involves the game that you chose. Kinsey. Repetition of game. Repetition of game is absolutely correct. So, Kinsey, you've regained the topic with 13 seconds to go. Games for Developers starting now. Games for Developers could be any game such as World of Warcraft, Halo, anything that makes you... That was an incorrect challenge! So, Kinsey, you've gained a point for being interrupted, and you have 90% of a second remaining on Games for Developers starting now. Impressive. Adam, you were doing so well, and you just handed that away. One minute left. So, yeah, Kinsey gains a point at the end of that round. Adam, you are up first to speak, and your topic is DHH. Doesn't actually fit on the screen! If you're wondering who to blame for that, it's me. I will accept the correct long form, which escapes me right now. However... So, Adam, you have 60 seconds on DHH starting now. DHH is the initials for David Hanna-Meyer Hansen of Denmark. David Hanna-Meyer Hansen is an individual that has brought a lot of opportunity to this world in front of us. At Go Ruko, we have focused entirely on the opportunities that the Ruby community has as a result of DHH or David Hanna-Meyer Hansen. From Denmark, he started by... Nadia? Repetition of Denmark. I think I heard a repetition of Ruby as well earlier on. Nobody picks up on that one. So, Nadia, you have 35 seconds remaining. You've gained a point, and you have 35 seconds on DHH starting now. I'm very happy to have challenged Adam on the topic of DHH, given an earlier conflict when he interrupted me on another... Adam? Is it diversion? What's the word? Deviation. Deviation? Ooh, because that was about the challenge about DHH. What do we think? Nadia gains a point for audience support. And 23 seconds remaining on DHH starting now. I was for keynote on the differences between microservices and monoliths and how Rails was like a backpack for him, which included action cable and interesting... Repetition of Ann. Yeah. There was lots of Ann's. Interesting, Adam. You have 1.9 seconds remaining on DHH starting now. David Hanna-Meyer Hansen. That is Garouko all we have time for. Thank you so much for listening. You have been my favourite audience so far on this game. All that remains at this moment in time is for me to thank the Ian Messeter, the originator of this game, and Nicholas Parsons, who's been presenting it in the real world for almost 50 years. Thank you very much for listening, and please once again show your appreciation for the panel. Stephen Shaw! All right, we've got a five. Adam Coppy. And today's winner, Kinsi Andoram. Thank you very much. Goodbye.