 y gw повid erbyn o'r argyfan o gyfnod, a felly i chi yn gynlyniad, a'r tyfn y cyfan ymlaen nhw'n eich gwybod y rhan. Felly rydyn ni wedi bod a'r wneud yn Gweithio Gwybod, rydyn ni'n gallu rhoi i gyd yn gwaith. Nw ddim ta'n iawn, Gwbod! Felly, rwy'n gweithio'n Gweithio'n Gweithio, ac mae'r gwbl sy'n ei ffordd rydyn, sy'n dweud ni mewn pi foldedegol yn y Lai Gweithio i'r Lai Gweithio, Maddwn i'r ymddun yn aeon ddiwedd yn i'r rai gael i Anglawn a'r i Anglawn, ac mae gennym eich benderfyn yn ei gael i panel. Yna yn ymwrapod panel, ac mae'n enwedd yn y shwyl i'r uniongymar o fwy o'r gallu cynnig... o'r ymdyn yn gwmwy. Mae'r panel o gael, mae'n gweld i gael i'r ymddun ac i'r ddiwedd... i'r finding o'r pannel. Ond yn mi'n iawn i ddweud i'r gael i'r gael i'r fydd. Rydym ni'n gwybod ychydig wrth fy hun, i fynd i'r panel, i gyda'r cyflwyfrwyr rwybi, ac i enwedig i'r panel yw'r gweithio'n gweithio. Wrth fynd, mae hynny mae'n gweithio'n gweithio'n gweithio'n cyflwyrwyr, roedd mae'n ddweud. Mae'n ddweud hynny, oedd yn delwch, oedd yn reirio, oedd yn defiant. Mae'n gweithio'n gweithio, oedd yn gweithio'n gweithio'n gweithio'n gweithio'n gweithio'n gweithio. Felly, nid ar gyfer amser yn ym兴 iawn. Swy Hall Aberffordd ddim nhw'n cael ei gyddiad ychydig sy'n gallu'n gweithio. Roedd yn ysgrifennu i ni'n pwysig yn ymweld, ac yn fawr, yn gael'r hyn byw'r gand ymlaen. Mae'r ganddwys yn unu', bod ni'n ddigwydd. Mae'n cael ei ganddwys yw'r panflaen. Mae'r panflaen i'r llïdd o'i wagfaint oherwydd mae'n ymweld mae'n dyfanc o'r bwysig. Ac mae'r gweithiauws ar gyfnodd. Wrth gynradd, mae'n ddiwedd o'r gael ychydig ar gyfer y byddol hyn o gael yma. O'r gweithio, mae'n gweithio o'r 3rd pieffordd o dechrau'n gyflwyno, ac mae'n gweithio ar y gwerth o'r gweithio, ac mae'n gweithio ar gweithio'r gwaith yma. Mae'r gweithio'r gweithio, yn allan o gael, yn y ddweudio'r gweithio'r cyfnodd yn y fwyaf mwyaf. ac ydy'r pionio mewn teimlo sy'n cyhoedd. Felly, mae'r pionio mewn teimlo sy'n cyhoedd yn meddwl. Rwy'n hi'n rhoi i wych i chi'n gwneud yn ysgrifennu i'w rhan a byddwch yn ei wneud yn ysgrifennu. Felly mae'n gwneud yn ysgrifennu. Rhywbeth i'r Rhubie-Colff? Rhywb! Welcau i ffyrdd yn ei wneud! Mae cymryd ymwysig ymwysig o Rhubie-Mynig, yn Llanantogdiog, texas, ymwysig ymwysig ym 2015. Felly, rydw i'n gweithio'r ffordd Fyrede, a wedi'i srifwyr i'ch bod y gadeau ffordd Gwyrdegwyr yn y ffordd Gwyrdegwyr yn y ffordd Gwyrdegwyr. Felly, i ddechrau'r gadeau, rydw i'n gweithio'r ddweud o'r ffordd Gwyrdegwyr yn cyffordd Gwyrdegwyr, a olygu'n gweithio'r ddechrau'r ffordd Gwyrdegwyr yn y ffordd Gwyrdegwyr. Dwi'n cael ei ddefnyddio'r thawr. Felly, dim ond, oes byddiwch yn ymweld, yn 60 sg, oherwydd am hyn o'r anhygoel, a oes bydd hwn i'r panlwys yn ystod yn ymweld, i'r anhygoel a'r oeddan nhw'n gweithio'r tawpig i fod yn gweithio'r hynny o'r hyn o'r hesfyn, o'r ymddiwch ymweld, neu o'r gweithio'r anhygoel, o'r anhygoel o'r llwyll ymweld, oherwydd yn y tawpig sy'n gweithio'r llwyll wedi'r rhaid, o strange ond oes byddai yw pwysig sydd yn ty privatei? Ond fel ydych chi'n ddigwethaf, mae'n cael eu hwnnw gan uchaf gweinwyr gweinwyr i'r lyricul, nad ymweld i iconiaeth ydi'r llwyl i'n tu. Felly ydych chi'n ddigwethaf ac mae'n registerd anghofol ymlaen arwmi ac mae'n ddigwethaf, gallwch yn gweld i ychwaneg y llwys yw ychwaneg. Os ydych chi'n ddigwethaf, mae'n gweinwyr bryd ac mae'n ddigwethaf ac yn fydddo i'w hollu cyfnwys ar ystafell, yn deall, a'n gyfnodd. Yn y gymhredu i gyfnodd, byddwch yn gwneud y cyfnodd iawn i'r olygu a fydd yn gorewn o'r ffordd cr返. Rwy'n cael ei fydd yn fydda'r ffordd o'r gwrddfodur, oedd gwneud yng Nghymru o phryg, ac nid efallai gwybod sefydlu yn gweld i'n fydda'r ffordd a dda'r ffordd, iawn i'n fan y ffordd trwy angen, yna'n gwybod unrhyw, Caerwch. Rhaid i'n rhoi ystyried â'r tairwch cydnod. Ychydig mae'n teudion! Wrth fynd i'n gwneud eich peth o amser oeredd hynny, maen nhw'n dechrau ar gwell, maen nhw'n teudio allu. Edrych chi, chi. Ychynodd gyfnod o gwneud hynny'n hefyd! Awfyn droi, yr hyn. Dwi'n haf oedd 60 ysgwrdd. Mae gwyfnodd angen a phoesio'n broi o'r anfoliadau o bruddion rhai. Dwi'n rhan o'r arddangoddi. Rhaid i'n ddweud. Yn y rôl yma, mae'r rôl yn ymdilladd iawn. Rwyf wedyn, mae'n rôl i'r bwysig yr yddydd. Rwyf wedyn, wedi bod yn ymdillad gyda'r eich bwysig? Mae'r rôl wedi bod yn ymdillad gyda'r eich bwysig! Rwyf wedyn, mae'n rôl i'r bwysig! Mae'r bwysig? Rwyf wedyn, mae'n rôl i'r bwysig yma, mae'n 55 sefydlu o'n rôl o'r gyda'r cydweithi. Archwisio rôl yma, dwi'n gwybod a'r cyfrifwyr. Erdwyd yn wybod y rhaid, bwysynt cyfan hynny ddim dda. Kezi! Covid-19 swyddeth. Yn deffinitio hefyd erdoedd. So chi weithio ar gyfer yr hoffa? Yn y ddiddordeb yw i am ddod. Mi'r ddiddordeb yn cyflawn eich cyflwyno ar leir. Mae'r first application that I built was a dog park finder. I am obsessed with Harley. I have a tattoo with her paw prints. She is awesome. She is my best friend. Repetition of she? Yes. Did I say it wrong? No. You said she is twice. It's just very simple. I'll give you that to sell. 30 seconds you are back with something that is starting now. I think a lot of developers when they get started on their first application can feel a sense of abject terror. The responsibility of writing code that is going to eventually face a customer can be very very dull. I did that in the practice as well. Yes. Such hyperbole. Hinting a challenge? Repetition of very. It's not very. Lost the heart of dogs to keep. It's back with you for 15 seconds on my first application starting now. My first application that I built. Repetition of built, isn't it? Yes, repetition of built from earlier on. It's almost exactly the first sentence you said before. Andy, you have 12 seconds starting now. The first application that I built. I disagree. He spoke through the laughter. He went through the laughter. He spoke straight through the laughter. I'll give you the point for the challenge at 8 seconds starting now. My first application on Ruby on Rails was a masterpiece in unprepared mess. Yes, it was hesitation, but nobody was deter. Okay, Alan, you are first up to speak next. Oh, no. Alan, your topic is my favourite text editor. My favourite text editor. Alan Patterson, 60 seconds starting now. My favourite text editor is not textmate or Emacs or Vim or editor. Repetition of all. So not said all, that would have been amazing by the way. Okay, Sam, you have 51 seconds on my favourite text editor starting now. Vim for life. Hesitation, sorry. Hesitation, yes. You have 49 seconds starting now. I also like Vim right now. I'm using a text editor called RubyMine though. And it's really slow. And the debugger is shit. But now it's still a great product at times. And I can easily... Sam, repetition of and. There was a lot of Alan letting go. They started booing me after 3 hours last time as well. It's great. However, it was correct. It was harsh. I give that to Sam, so 31 seconds starting now. In all seriousness, I think it's acceptable to use different text editors depending on the language, framework or system that you're working in. It's often the case that sometimes you want an IE, sometimes you want... Repetition of sometimes. Yep. Correct. I've got some guys at times. His 18 seconds back of your own are my favourite text editor starting now. My favourite text editor is the text editor that I like to use every single day, including weekdays. Sometimes I use it on weekends. But that's when I'm just coding for fun. I think that using a text editor is an important part of it. Round two and it is anybody's game. We're going to have a three-way tie with three and our custom is two. Pinty, you're up next to speak. We've got a technical topic, concurrency for you. One minute on concurrency starting now. I wish I knew more about concurrency so I could talk about it intelligently while I'm up here in front of tons of people. So this is a little embarrassing, but not really because I can just talk about something related to concurrency but not have to technically explain it. And I might know more about it if I had a background in computer science or went to a coding school. I'm sure they teach that there. There are two coding schools in Denver. I'm going to call hesitation. Yeah, that was very elongated. However, that was 32 seconds though, nothing about it. Amazing, however, Sam does get the point at 28 seconds starting now. I know a little bit about concurrency, but inevitably when one is building a program which is concurrent, it ends up being an unending fucking nightmare. This is typically because concurrent programs are... Repetition of programs. Yes, repetition of programs. Yep, yep. So Pinty, it's about with you, 11 seconds starting now. I think that we should be teaching more people. I think it's repetition of teaching. I didn't say that. Did anyone hear teaching earlier? No. No. So that was an incorrect challenge. Pinty gets a point and those six seconds back starting now. As I was saying before I was rudely interrupting. Pinty was winning at this point in Brighton as well. Yeah. This time she knows the game. Okay. Don't jinx it, don't jinx it. Pinty is an absolute sniper. Pinty, leading on six. Andy, you're up next to speak. Your subject is Hello Ruby. Hello Ruby, Andy Croll starting now. Hello Ruby is a book by Linda, which was your start. Hesitation. Yes. Yes. Pinty, you have 55 seconds starting now. When I see the word Hello Ruby on the screen, I'm not really sure what it means. So I'm thinking about a song called Hello Dolly, which is by the great Dolly... Andy. Well, that's deviation, isn't it? That is deviation. We were talking about Hello Dolly and not Hello Ruby. What's Hello Ruby? I don't even know. I would say Hello Kitty, I wasn't that loud. I think Andy's going to tell us. Andy Croll, you have 45 seconds starting now. The trouble with a subject such as Hello Ruby is that it's difficult to know where to go with it. There is a children's book that was kickstarted in the recent past, and I am probably going to run out of words if I don't keep talking out loud like this. That's going to be deviation as well. Hesitation, deviation, talking nonsense. Pretty much everything. OK, Sam, you have 29 seconds starting now. I've just learned that Hello Ruby is a book written by the wonderful Lucas, and the thing that's interesting about that is I actually met Linda at the Frozen Rails conference in Finland the one time that I went. The conference was super interesting and someone's just coming on and they don't repetition of conference. Andy Croll, you have 14 seconds starting now. As a father of twins, I look forward to the day when I am able to pass them a copy of Hello Ruby, two of which I bought during the campaign when she was funding into... Oh. Yeah. Hesitation. Yes. And with two seconds. On Hello Ruby starting now. Hello Ruby is a book. It's only just behind. OK, Sam, you're up next to speak. Your subject is legacy code. Legacy code, 60 seconds starting now. I help make ASPEC. ASPEC is a really... Yep. Andy. I believe that was repetition of ASPEC. It was. Yeah, fair enough. OK. Andy Croll, you have 55 seconds on legacy code starting now. It has been said that as soon as you write code, it becomes legacy code. The times that you spend not writing legacy code are few and far between. It's very difficult to think about any code that I've written that doesn't somehow end up as legacy. Repetition of Britain. Was there a written earlier? I... Right and written. I think he's good. Andy, you have it back. 38 seconds. Right and written are two different words. It's the same word, it's just different. They have different letters and they sound different. The rules. This might be the American English language barrier. High Texas. The 38 seconds starting now. My first app was a PHP app about... Sam. Repetition of app. Repetition of app, of course. What? It could have been leading to legacy code. Code that was written some time ago. However, Sam got the best. So you have 34 seconds starting now. I like to describe myself as a machine for generating legacy code. I'm a consultant and most of the work I do is basically just screwing everything up and getting a pager. It's great. So, yeah, if you're... Andy. That's hesitation. Oh, I disagree. Yeah, it was definitely a bridging word on this. Filling that space. Yeah, I'm going to give you that one. We're not sure in the room. OK, I have 90 seconds starting now. Just as when you're on a panel game, it's easy to make enemies with the people listening to you. It's easy also to make... Repetition of easy. Repetition of easy, yes. I'm making... I was also about to say enemies, so... Sam, you have 12 seconds starting now. There are many definitions of legacy code and also code smells. There's a book by I think it's Martin Fowler who explains how to detect code smells. Sam, meet up. OK, we're going to have a tie in the lead between Sam and Andy, our British contingent on the show. Aaron, you're next. Yeah. Your topic is duck typing. Duck typing. Aaron Patterson starting now. So, I think that duck typing is a very interesting technique for ducks to use when we are typing at a computer because ducks also like to produce legacy code. Oh, Sam. Repetition of ducks, which is not in the tie type. Yes. The topic is duck and you repeated ducks. Technically correct. Technically... Technically correct is the best kind of correct. Can I repeat duck typing? You couldn't have repeated typing either. OK, so Sam, you have 50 seconds on duck typing starting now. Duck typing is a way of building a type system for applications such that when you pass objects around them, they respond to different method calls. This allows you to infer different behaviours. Aaron, repetition of different... Repetition of different... We'll have the topic back for 34 seconds starting now. As I was saying, duck typing is when a duck typing... Oh, I was going to say hesitation. It was hesitation then. Oh, you guys are going, so I didn't know if it worked. It was a very elongated version of the word typing. Kids, you have 27 seconds starting now. So, when I was first learning Ruby a couple of years ago, I was very confused by the term duck typing and everyone kept telling me the same slogan and it was, if it walks like a duck, if it quacks like a duck... Repetition of if. That was too if. I was pre-empting the next one. He pressed challenge into my life at three cognition circuits. He gained a point. I have 11 seconds on duck typing starting now. So, as I was saying before, I was so rudely interrupted by Andy sitting next to me. Repetition of I, that was three times. I'm creating 3.9 seconds on duck typing starting now. Duck typing is an interesting programming technique that I like to use. Interesting. Repetition of technique for your earlier speech. Yes. Yeah, and interesting too, I think. I have half a second to speak about duck typing starting now. Duck. I've got the point for speaking at the end of that round. I want to hear your next up to speak. Five fun things to do with Ruby. Five fun things to do with Ruby starting now. Five fun things to do with Ruby is a great topic because I've seen a lot of talks that are about fun things to do with Ruby. One of those is music. I've seen music presentations. Oh, music. Yeah, yeah. Repetition of music. Repetition of music. Absolutely. OK, Andy Crow, you have 45 seconds starting now. Given that I've chosen Ruby as my programming language, I like to think there are more than five fun things to do with Ruby. There could be 10 fun things to do with Ruby. Or perhaps 15 fun things to do with Ruby. And you can spend many hours, 20 hours talking about... Repetition of hours. Repetition of hours. We'll go into you at the top of the bucket. And 25 seconds starting now. Splice is an awesome company where they are doing fun things with Ruby, but they actually are not doing fun things with Ruby anymore. They actually right go. Repetition of fun things which is in the title. Yes. That was an incorrect answer. You could have had repetition of doing, but now it's too late. So, Kinsey, you have 16 seconds starting now. Wait, don't I get another point? You got the point. Oh, sorry. Andy, that was it. That was it. Are you busy trying to get additional points? I thought I was missing a point, so I just wanted to make sure that it was properly reflected. You gained the point for that time. OK, so I lost that one? Yeah. Andy, you get a point. That's 40 seconds starting now. Five fun things to do with Ruby would be an excellent name for a talk if I were to submit it as part of a call for proposal or something like RubyConf, or RailsBridge, or other things that... Some car got away with that third wall. I wasn't quite fast enough. Andy, your question is up to speak next, and open source software is your topic. Open source software starting now. I think it's clear to see that none of us would be here today where we're not for the principles of open source software. We all rely in our day jobs on software that has been open sourced by smarter people than ourselves who might find useful libraries that they build for other people to use and open source software. Has it hesitation? I think there are hesitations. So put me out of my misery. OK, Sam, you have got your point and 37 seconds on open source software starting now. Open source software can be accronimised in a number of ways, including O source software, open S software, open source S, O, S. Repetition of S. Repetition of S! I'm still dead fat for 25 seconds starting now. There are a lot of scary and kind of upsetting statistics around contributions to open source software. Currently, I believe, you don't quote me on this, there are 2% of open source software contributors, are women, and 98% of open source software are men. Yes, so you get the point, you're currently in the lead. Maybe you've got time for two more rounds. Sam, then you're next to speak and your subject is the Friday hug. Starting now. To my immediate right is the inventor of the Friday hug, one, Aaron Patterson, or Tenderlove on the internet. The great thing about the Friday hug is it encourages all of us to celebrate the end of the week and the achievements that we've made in the time that we've spent building our applications. One of the interesting things about the Friday hug is it encourages you to take a selfie when you... Repetition of encourages? Yes. 34 seconds in the slot of the onion, uniquely equipped to speak. Now, I invented the Friday hug. I think you have 23 seconds starting now. To be sharing a stage with the creator of the Friday hug at this venue where the Friday hug is unfortunately unable to be performed due to the lack of Fridays rather than the lack of hugs. Repetition of lack? Repetition of lack. So Sam, you have 10 seconds remaining. You're right, Aaron. 10 seconds starting now. What I've just discovered is that talking about the Friday hug is a good way to bring its creator to absolute hysterics on a panel of game shows such as this at Rooney's Golf Club. Our last round currently, Sam is in the lead. It's almost anyone's game. First to speak in this next round. Performance tuning is your topic. So performance tuning, Aaron, is starting now. Performance tuning is a very important topic that I like to talk about, especially because I enjoy tuning my piano and playing it very quickly. I'm going to suggest hesitation. That may well have been hesitation, sir. So Sam, you have 49 seconds of performance tuning starting now. Performance tuning aspect has been a really interesting exercise. Mostly we've been using allocation tracing to determine where objects are created within the library. This then enables us to make performance optimisations by removing object inside. Kinsey. Repetition of optimization. Or object, sorry, object. Which object are you counting on? Object. Okay, Kinsey. You have 32 seconds on performance tuning starting now. So someone who really inspires me in the space of performance tuning is Eileen. You might know her on Twitter, but I am not going to say her handle because that would be repetition. And she gives an excellent talk about performance tuning in tests and in controllers. And if you haven't seen it, it's a really great presentation. Repetition of presentation. Yes. An ant. I think I said ant a hundred times. So Aaron Petson, you have nine seconds to gather seven blanks. Sorry. Starting now. I really enjoy performance tuning of software and legacy systems. I actually win it. I just wanted to go before we finished. So there was no challenge. You get the points. You have 2.6 seconds starting now. 2.1 seconds starting now. Aaron's a nice man. 1.7 seconds. We are running over time. Starting now. I'll start you again. Starting now. Aaron hasn't said anything in about four seconds. Give me that point. Repetition. Is that incorrect, do you think? 1.1 seconds on performance tuning starting now. Performance. Thank you so much RubyConf. This has been amazing. So at the final scores, Sam Phippen is winning with 15 points. We have a tie for seconds and are very close for. So it only remains me to thank Ian Messiter, the man who created this game, and Nicholas Parsons who has been hosting it for nearly 50 years. I really am just keeping it a sequel. RubyConf please, one last time, join me and throw your appreciation for the panel. Aaron Patterson.