Just A Ruby Minute

by Andrew Faraday

The video titled 'Just A Ruby Minute' by Andrew Faraday presents a unique and entertaining adaptation of the renowned game show 'Just a Minute' in the context of the Ruby community at RubyConf 2017. The event features a lively panel of speakers challenged to discuss various topics related to Ruby development without hesitation, repetition, or deviation for a minute each.

Game Mechanics: Andrew introduces the game rules and encourages audience participation throughout the event. Each speaker is tasked with discussing a topic while adhering to the constraints of the game, inviting challenges from fellow panelists if they notice any breaches in the rules.
Panelists: The panel includes notable figures such as Adam Cuppy, Tara Shona De La Fuente, Andy Croll, and Sam Phippen, each bringing their unique perspectives and humor to the discussion.
Topics Discussed: The topics of discussion include themes like speaking at Ruby conferences, coders in movies, visiting New Orleans, asking for help, error messages, hiring developers, and managing dependencies. Each panelist adds their personal touch, often leading to humorous exchanges and insights.
Key Examples: Notable exchanges highlighted the ridiculous portrayals of coders in movies, with Adam humorously stating that 'coders in movies is a myth.' Tara shared her experiences of visiting New Orleans, including a comical take on the Museum of Death. Their discussions often reference real-life experiences in Ruby development and community engagement, delivering both entertainment and insight.
Conclusions and Takeaways: The video encapsulates the collaborative spirit of the Ruby community, blending humor with reflection on common challenges faced by Ruby developers. The interactive nature of the game fosters a joyful and engaging atmosphere for both the speakers and the audience, reinforcing the importance of community, collaboration, and fun in the tech space. It serves as a reminder of how game-like formats can effectively engage participants while encouraging dialogue about technical topics.

Andrew Faraday concludes the session with gratitude, rallying the audience to appreciate the panel’s contributions and the legacy of the game. Overall, 'Just A Ruby Minute' stands as both a celebration of Ruby and an example of how playful interactions can stimulate meaningful conversations in software development contexts.

00:00:10.220 Thank you for that really well-prepared introduction. Okay, I need you to do something here. Good afternoon, RubyConf! We've got about 800 people in the room. I think I heard about 700—that will do! My name is Andrew Faraday and here's how the game works.

00:00:42.680 As you know, it's a game called Just A Minute. Now, this is where we get to see the Ruby community at play. It is not your typical conference panel; we're just going to have some fun. That means you are very much a part of the experience we’re about to have. You have my permission, RubyConf, to react. That means laugh if you want to laugh, cheer if you want to cheer, and cry if you want to cry. One thing I’m going to ask of you is that when I start the game in the traditional way, I’m going to boisterously welcome you to the show, and the theme music will come in. As soon as you hear that piano, I need you all to put your hands together, raise your voices, and raise this rather beautiful conference room roof! Can you do that for me? Here we go! Welcome to Just A Minute!

00:01:26.439 A very special edition of Just A Minute here in the fine city of New Orleans! Here’s how the game works: Each round, I will pick a topic that's of interest to Ruby developers and I will ask one of the witty, insightful, and currently terrified people before you to speak about that topic for a total of 60 seconds.

00:01:38.230 Sounds easy, but they must avoid three restrictions on how they speak. They must avoid hesitation, including pauses and hedging noises; repetition, where they repeat an earlier statement; and deviation, where they stray from the topic given. If the other panelists discover that these rules are being broken, they can challenge by pressing their buzzers. The timer will stop, and if their challenge is correct, they will gain a point and control the topic.

00:02:10.500 They will have to speak about that topic until the minute is over or until they are in turn challenged. Incorrect challenges give a point back to the original speaker, and whoever is speaking at the end of a minute gains a point for doing so. Whoever has the most points at the end of the game wins bragging rights, basically. And that's how the game works!

00:02:26.859 So let's meet the panel. Without any further ado, furthest from me, we have the CEO of Coding Zeal and the dirtiest player in the history of the game—please welcome Adam Cuppy!

00:02:34.329 Next up to his right, we have the creator of the one and only Goat User Stories; please welcome Tara Shona De La Fuente!

00:02:50.790 Next up to his right, we have the organizer of BrightonRuby and writer of One Ruby Thing; please welcome Andy Croll! And last, but by no means least, we have a developer at Digital Ocean, an expert maintainer, and a true RubyJam veteran. He’s been with us since the very first Just A Ruby Minute panel—please welcome Sam Phippen!

00:03:07.120 Now, that is a record, and Sam, your topic is pretty matter-of-fact: speaking at a Ruby conference. This is Sam Phippen, on speaking at a Ruby conference about hesitation, repetition, or deviation—starting now!

00:03:38.230 Right now, what I am doing is speaking at a Ruby conference. I spend a lot of my time speaking at Ruby conferences such as this one that we are currently at. When many people come together to speak at a Ruby conference, they discuss topics involving Ruby conferences. Thank you very much.

00:04:04.550 As much as I enjoyed that, repetition of 'conferences' is indeed a problem.

00:04:23.640 Yes, absolutely! So, Andy, you have 28 seconds remaining—starting now.

00:04:42.390 In my experience of speaking at a Ruby conference, it is unremittingly terrifying, to a degree that would be unsurprising to those of you who saw my talk this morning where I was speaking at all.

00:05:23.640 When I am speaking at a Ruby conference, I like to talk about things I know, like cats, goats, and walruses.

00:05:35.320 That list is pretty harsh, but there were four times that I managed not to curse; I count that as a win.

00:05:50.150 So, Andy, you have six seconds remaining—starting now. When speaking at a Ruby conference, it is very important that you keep your language clean.

00:06:05.340 The repetition here has nothing to do with this. If I get to brew someone else, then you can’t call them by your nickname.

00:06:15.240 That’s an incorrect challenge, and Andy gains the point. You have zero seconds remaining and a point for the end of that minute.

00:06:33.090 Okay, Adam, you are next up to speak. Your topic is coders in movies—starting now.

00:06:45.600 For starters, coders in movies is a myth. There are, in fact, no coders in movies, because most movies center around a protagonist and an antagonist who know very little about coding themselves.

00:07:07.550 Instead, what we look at is the insightful nature of coders in movies and how they think through problems to find a better and more ideal solution to overcome a world against robots and chickens!

00:07:23.870 That was a very elongated pause there, so I’m going to call hesitation. That was definitely hesitation.

00:07:52.170 You have 28 seconds remaining on coders in movies—starting now!

00:08:09.050 When we programmers observe coders in movies, we very quickly realize how ridiculous the repetition is. I noticed that Adam has not gained any points yet, so I’m going to give you that one.

00:08:32.140 We have 20 seconds remaining—starting now!

00:08:49.470 Coders in movies are vastly different from the rest of the people in those movies. The repetition of people from an earlier speech is what I’m noticing.

00:09:01.320 You have 14 seconds remaining—starting now. The thing about coders in movies is that often, they portray a very inaccurate depiction of coders, who typically don’t conduct practices like typing very quickly with two fingers.

00:09:19.210 Tara, you’re next! Your topic is visiting New Orleans—starting now!

00:09:34.850 I am currently visiting New Orleans, where I have been speaking at a Ruby conference about things that are not goats. Earlier, I talked about mentoring.

00:09:54.610 Definitely hesitation! I knew that was a challenge. Yes, yesterday, when I was speaking at RubyConf, I still did not curse! So, you have 45 seconds on this topic—starting now!

00:10:16.490 Visiting New Orleans has been an eye-opening experience for me. Walking the streets of the French Quarter, eating beignets—which, as far as I can tell, are just a bunch of icing sugar on top of a donut—but the levels of sweetness are beyond anything I could have possibly imagined!

00:10:45.290 Visiting New Orleans has surprised me because I’ve been to the actual Museum of Death, which is a genuine tourist attraction. You would be surprised at the stuff that is presented there.

00:11:06.170 Did anyone here expect to be surprised? The employees do their best to surprise the guests, but this is repetition of 'surprise'!

00:11:27.830 Yes, I feel like I’m challenging—that you’re coming after the spot of Sam. I’m not sure; I have to give Andy the point there.

00:11:45.390 Okay, Andy, you have 12 seconds—starting now. Visiting New Orleans has included elements of Voodoo in the culture, with a tiny house on Bourbon Street where you can go and see the shrunken heads and voodoo dolls.

00:12:05.500 Andy is getting away with repetition of 'Voodoo'!

00:12:22.610 Alright, your topic is asking for help—this is Andy Croll on asking for help—starting now!

00:12:35.190 I feel like at this very moment I am asking for help. I’m trying to give my talk, and it’s JooyConf, not Andy Kampf!

00:12:45.410 It doesn’t make sense for me to still be up here talking about repetition!

00:13:12.090 Tara, you have half the points, and you have 49 seconds—starting now!

00:13:32.090 I have been asking for help from a variety of people, like my friends, colleagues, and patriots.

00:13:56.099 I mean, hesitation—I just wasn’t ready for this. I still haven’t cursed!

00:14:16.300 So Sam, you have the question of asking for help—39 seconds starting now!

00:14:35.300 As I sit here on this stage desperately asking for help, it makes me wonder what we are all doing here and what does it all mean.

00:14:55.500 It’s important to remember that asking for help is something we should all do when facing troubles in our lives.

00:15:17.790 You may feel that you can’t talk to people about the things you are experiencing.

00:15:32.100 This is hesitation, with 21 seconds remaining. I can tell you want this subject back, so let’s get back to it!

00:15:48.000 I feel like my fellow panelists may be asking for help. For example, Adam Cuppy just reached across to Andrew Faraday and asked, 'What’s the deal?'

00:16:05.800 Is he still on asking for help? He only has one point!

00:16:20.100 On the bright side, my buzzer works! Yes, it does work!

00:16:30.200 I’m going to give you that point; it seems to follow along the theme.

00:16:39.400 Alright Sam, you're next to speak—your topic is something about the keynotes.

00:16:54.600 My good friends, showing Griffin and his wife Tess are sitting in the front row.

00:17:13.720 They have a child named Ruby, and it’s currently...

00:17:43.450 I am referring to it in this context. I feel I was probably not alone in this.

00:18:02.500 It wasn’t a challenge, but I don’t want to let it go. You give me a point!

00:18:20.030 That was clearly on topic. It was indeed on topic!

00:18:35.000 For those who don’t know, the child in question is named Ruby.

00:18:51.400 The mention of goats is dually relevant here!

00:19:07.700 I’m going to give Tara the point—oh, I really hope your child isn’t—well, you know!

00:19:20.300 Starting now! Asking the question: Is Ruby dying?

00:19:42.000 It's important not to bring up the potential death of children while on stage.

00:19:56.400 It is, however, a difficult and challenging topic!

00:20:09.000 As I was saying meanwhile, Ruby dying is a very difficult matter to discuss here on stage.

00:20:25.600 Just a reminder, we are all dying! So, let me transition to everyone.

00:20:43.000 As I mentioned in my talk yesterday, I almost got a PhD in English.

00:21:02.700 You can see how that accuracy can fade.

00:21:16.500 Was that a correct challenge?

00:21:24.300 You just talked about the topic, so we should end that challenge.

00:21:45.000 Now, Adam, you have 33 seconds remaining on error messages—starting now!

00:22:00.000 I am very well aware of error messages—not only in my code but in my own life.

00:22:18.000 For starters, about two minutes ago, I think I faced a total system failure!

00:22:35.800 It was something I was not overly familiar with, but this reminds me of a time writing Ruby and reading the error messages.

00:23:05.850 You have 39 seconds remaining.

00:23:24.500 When I receive error messages, I like to take them as opportunities to learn about the system upon which my team is working.

00:23:44.400 Those error messages often indicate a potential underlying issue in the system, such as how it is processing transactions.

00:24:06.870 Tara, you have 16 seconds remaining—starting now!

00:24:32.400 When I think about error messages, I often notice the error codes they begin with, like 401 or 402.

00:24:51.300 It's intriguing, as understanding that seems smart, but when I begin to notice them, they become a form of repetition.

00:25:07.150 Yes, that sounds fine, but many people challenge you to think of them.

00:25:20.900 That's just standard procedure!

00:25:39.200 So Sam, you have eight seconds remaining—starting now!

00:25:57.000 Hiring developers is a complex process that results in a lot of...

00:26:07.460 Alright, your next topic is hiring developers generally. It's a complicated process that can often lead to trauma for the developers being hired.

00:26:30.300 One of the most critical elements of the process is determining qualifications.

00:26:45.390 Tara, you have the floor—49 seconds starting now!

00:27:00.000 In my experience, when I was in human resources, I focused on hiring developers.

00:27:17.070 The Boston Symphony Orchestra, where I was recruiting musicians and coordinating benefits, required me to eyeball resumes full of errors!

00:27:40.450 I frequently came across resumes where it said 'I am a sign language interrupter.' You know what that means!

00:28:01.230 That’s a whole different error in understanding job roles.

00:28:20.600 As we engage in this process, we're also managing the complexity of dealing with candidates.

00:28:34.400 Sam, you each have eight seconds starting now.

00:28:52.950 When we are hiring developers, we need to assess their resumes very carefully.

00:29:07.300 Repetitions and errors become red flags; we have to ensure they stand out.

00:29:27.900 So each resume can hold subtle cues that help form a judgment.

00:29:45.000 So, our next task is managing dependencies—Andy, on managing dependencies starting now!

00:30:10.200 There are many ways to think about managing dependencies; there’s bundler or Gemfiles.

00:30:40.300 Managing dependencies is essential because we need to keep a track of which package or library versions we use.

00:30:55.400 Every dependency can lead to other dependencies; hence we need to approach this issue.

00:31:10.000 Sam, you have 15 seconds on managing dependencies—starting now!

00:31:25.490 When I think about managing dependencies, there are many programming languages I can consider, such as Go, Ruby, Rust, and many more.

00:31:44.650 Managing them accurately will enhance your productivity.

00:31:54.010 In the exhaustion of all discussions, if there's repetition, I'll play off jokes, and you can respond with challenges.

00:32:26.000 Whenever you're managing a conference or session, you need to manage those dependencies.

00:32:47.200 Working with tools is key.

00:32:51.660 Thank you very much for joining in this great conference!

00:33:05.000 You’ve been an amazing audience.

00:33:12.100 It remains to me to thank you for participating in this game, created so many years ago, and to Nicolas Parsons who hosted it for many years.

00:33:36.690 Thank you very much! I’m Andrew Faraday, and please join me in appreciating our panel: Adam Cuppie, Tara Shona De La Fuente, Andy Croll.

00:33:45.350 Thank you all!