Skip to content
466: All about keynotes with Aji Slater episode artwork

Jun 24, 2025 43 min

466: All about keynotes with Aji Slater

from The Bike Shed Hosted by thoughtbot

As the final RailsConf draws near Joël and Aji Slater sit down to discuss its varied and interesting history of keynote presentations. The pair reminisce on their previous trips and talks at RailsConf, share some tips on creating the perfect keynote, as well as discussing the strong community that’s rallied behind RailsConf for so many years and how to best connect with others at similar cons as an audience member. — Don’t miss out on the final RailsConf which takes place July 8th - July 10th in Philadelphia, PA! Get ready for by checking out Aji’s recommenced keynotes from previous years 2022 - 2017 Thanks to our sponsors for this episode Judoscale - Autoscale the Right Way (check the link for your free gift!), and Scout Monitoring. You can connect with Aji via LinkedIn and GitHub, or check out some of the topics they've written about over on their thoughtbot blog. Your host for this episode has been Joël Quenneville. If you would like to support the show, head over to our GitHub page, or check out our website. Got a question or comment about the show? Why not write to our hosts: [email protected] This has been a thoughtbot podcast. Stay up to date by following us on social media - YouTube - LinkedIn - Mastodon - BlueSky © 2025 thoughtbot, inc.

Episode details come from the podcast's RSS feed.

Embed this episode

Ready to play

466: All about keynotes with Aji Slater

0:00 43:36
of matches

Transcript Auto-generated, may contain errors

Have you ever set up auto scaling on your production app? Maybe you know how painful it is to use built-in auto scalers on platforms like AWS and Heroku, the confusing settings, unreliable metrics, and no clear visualization of what's really happening. JudoScale is the auto scaler built to make your life easier. With smart defaults and beautiful charts, you'll be auto scaling in minutes. The result? A much lower hosting bill and a bulletproof prod environment that easily handles traffic spikes.

You can use JudoScale on AWS, Heroku, Render, Fly.io, and more. It's free for low traffic apps and unlimited plans start at $25 per month. AutoScale on easy mode at judoScale.com. Hello and welcome to another episode of The Bike Shed, a weekly podcast from your friends at Thoughtbot about developing great software. I'm Joel Kinville and today I'm joined by fellow Thoughtbotter, Ajis later.

Hey there, Kessen Kittens. And together we're here to share a bit of what we've learned along the way. So, Ajis, what's new in your world? Well, right now my current client has an application whose front end is in Angular. This is not a technology I've really worked before.

The Rails backend, so I'm pretty comfortable there and we have to learn new things all the time, find ourselves in new environments, figure our way around. That's just kind of what we do as consultants. But because of the timing of where in the world this project is happening, it's been a fun experiment for me to try an alternate way to learn a new framework and a new environment. I've been using a lot of LLM tools to learn my way around, not necessarily the application itself, but learn my way around Angular, being able to ask questions to explain something that might not match up exactly what's in the docs. And it's been an interesting experiment, I think, things have done well as far as the project is concerned, but I've come away with a lot of learning as to how I can best interact with these new tools.

What's the experience been using LLM for effectively documentation search versus a traditional Google search? It is definitely helpful in that I don't need to know what keyword I have to look for beforehand, especially in a completely new environment. You don't always know those terms, right? And so it's been fantastic for that because I can put a line or two of code into it and be like, can you explain this to me? And give it the different libraries and packages things that we're using.

So it's certainly helpful for that. I have not found it to be very good generating new code for this environment. There are a couple of unique, probably not unique, but there's a combination of, you know, of libraries, the way that application works that is not part of the usual documentation for Angular things. So the LLM is not really interacting with those correctly, but it has definitely been able to point me in the right direction when I didn't know what direction at all. I remember reading an article by Avdi Grimm a little while back, and he was talking about the role of experience in knowing even what questions to ask.

And so in face with an uncertain situation, someone who has a sort of richer background or more years of experience can often get themselves out of an equally confusing situation more easily than a junior person. And a junior person could confront it and ask like, how did you know what to do that? What to search for? Or like, how do you even like ask a question and get ourselves out of this mess? His sort of musings on that was, yes, it was based on experience.

And then how do you build that experience to get to that point? And he'd been experimenting with LLM's as a way to do that in situations where he doesn't have experience. Yeah, that sounds pretty pretty much like what my most successful experiments have been with this or successful experiences rather. It reminds me of a, I want to say that was 2017 keynote by Justin Serals. This was at RailsConf in 2017.

He talked about how often we learn as part of learning programming what a program is and what the different components of a program might be, but we don't learn how to program. Like the thought process of making decisions in this work. And it is sort of left up to like vibes and mirroring of people earlier in their careers to see what more senior devs are doing as sort of critical thinking, their decision making process, the way that they uncover problems and work through different situations. And that can be sometimes an insurmountable barrier to getting into this work.

And then other times you'll let people that solve that gap in different ways than you might expect. And every so often that doesn't read properly to a team or different things like that. But he basically laid out a little bit of a framework. It was just kind of a fun thing where he did the Serals Briggs developer test. I love that.

Unfortunately, the online version of it is closed now. You can't do it anymore. But he walked through the way that he thinks about problems by using this riff on the Myers-Briggs test to describe the way that he thinks about problems. And that's one of my favorite RailsConf sessions. Speaking of RailsConf, at the time of recording, we're about three weeks away from the final RailsConf.

This is going to be the last one. Are you going to be there? I am going to be there. I'm pretty sure that you're going to be there as well. I think we have quite a few thought-butters who are going to be at the conference.

So if any of our listeners see us while we're there, definitely come say hi. Absolutely. I'm really glad that we have a nice little bundle of thought-butters going because thought-but has been part of the Rails community for a very long time. And I think it's appropriate that we have some folks there to kind of send off the last RailsConf. And particularly, I'm excited because there are a bunch of us who are going to be speaking on a variety of topics.

And so, yeah, if you are at the conference, come listen to some of those talks. Yeah, it's actually going to be my first time keynoting at a conference as well. That is a big deal. How did that come about? Well, the sort of cynical story that I like to tell is that I tricked the program committee into giving me this lot by saying keynote as many times as I could in my proposal.

But while my talk is about keynotes and kind of looking back at the history of keynotes over all the RailsConfs that have been, it maybe less cynically is that I've done a lot of speaking at Ruby Central events and I've gotten to know a lot of folks that are in the program committee and they saw my proposal and know my speaking style and have enjoyed my presentations and kind of elevated it that way. It's less social engineering than I like to joke. You weren't just priming them the whole time? I mean, it was, but I think there's more behind it because they wouldn't have just done that decision willingly. So you submitted through the regular CFP process and then it got picked to be a keynote?

Yeah, that's actually something that happens more often than I think folks recognize. Often, keynoters will be selected because they're folks that have a background in keynoting or they'll have an interesting topic that is very topical or they'll be someone from outside the community. That's something that RailsConfs has done really well in the past having someone with a completely different perspective or a different role that can offer us some learnings and being able to learn from the outside like that. But it is fairly common for proposal to sort of hit the nerve of what the conference organizers want the topics to be about and want the kind of theme of the conference to be.

And if that speaker is an established speaker is usually going to be pretty important to be handing over the main stage, then the then those talks can be elevated like that. Made sure that everyone at the conference is going to have a chance to see them. I like that. I guess I always assume that keynoters were picked by invitation. And so it's cool to see that they pulled people from the CFP as well.

Yeah, we did that for a talk when I was on the program committee of RailsConf Detroit, which was the penultimate one, the last one, not the last one, but the last one. And that is how we got the amazing talk from Irina Nezrada of Evil Martians. And that was one of the highlights of the conference for me. So I'm really glad that she submitted the talk that she did and that it was right where we wanted the conference to be. You said something interesting earlier about also sometimes if you get a talk that you think would draw sort of too many people in a session that sometimes that gets promoted to a keynote.

And I feel like I've definitely felt that I pass RailsConfs where, oh, you've got a session that's being given by Sandy Matts or something like that. Everybody wants to go to that session and it sort of drains all the other ones in the competing slots. Yeah. And that's sort of one where I guess the audience almost votes with their feet, right? This should be a keynote.

Yeah, that's true. I'm not sure that I've specifically heard of that kind of thing happening, but I can very easily see that because after the sort of blind selection and everything to make sure that you've got diverse and inclusive field is gone through that part of the process, then it really is much more an art about like shaping the conference and highlighting things that the community can respond to in that way too. So I can definitely see that happening. So in what way is, in your opinion, a keynote different from a session talk? Do you take a different approach to what you're trying to do with it or the way that you write or conceive of the presentation?

I think that there is kind of a different feeling to them a lot of times. There have been some fantastic keynotes at RailsConf that very easily could have been a session that wasn't keynote based on its topic. But I think there's something that kind of energizes the speaker a little bit to be a little more impactful in their focus or their takeaways or maybe that was just those folks that I watched were fantastic speakers and that just kind of happened anyway. But I think keynotes are kind of an elevated moment of conversations that the community are already having. So they're a bit of a punctuation on things that people are already thinking or talking about.

And sometimes they can drive those conversations as well, certainly for the small community that forms around each conference, those keynotes are going to drive conversations during the day there. And so that's something that organizers will think about. That's something that a keynoter is going to want to think about. Like, are people going to be inspired to talk about this because you probably don't want to do something that's going to shut down discussion because that's not going to be really helpful for anybody who's in the room there? You said something that caused me to think in a way that I hadn't before, which is the idea that every conference is a temporary community and the people that are present to form ad hoc community that exists for several days.

And the next conference we're going to create another and overlap a lot with the previous one but not necessarily all the time. But each conference is functionally a little mini community. And a key note is one of the few experiences that is going to be fully shared by that community. And it sounds like part of what you see as the purpose of a key note is to create shared conversation points for that community during those few days. Yeah, that's where I've seen the most successful keynotes live and what I've seen them do.

I've been going to RailsCon since 2016. I've only missed one since then. And very often the keynotes, especially for the opening keynotes, they get folks talking. And a lot of times other sessions could potentially be seen maybe through a different lens or with a different context because of keynotes that have happened earlier. And you're right, that sort of shared experience.

You can connect things that you've seen that perhaps other folks didn't see through that shared moment, that shared presentation. Yeah, the idea of it being a small little community is something that I sort of hit on as I was putting together my presentation because the kind of conceit behind my talk is to have watched every single key note from every RailsCon that has been and try and give some takeaways or some learnings from each of them and maybe all of them as a whole. And so I've seen even just within the microcosm of a conference that are the keynotes interaction and response and replies between the keynoters on stage where it's obvious that parts of a talk have been altered to match or to respond to something that has happened earlier in the conference.

That might on its own seem like an isolated thing that keynote speakers are doing, but it's actually a reflection of what's happening over the entire conference. If a keynoter two days later is still talking about something, guaranteed the people they have been talking about it the whole time. I think now I realize that some of the questions I asked you earlier, you were probably doubly prepared to dig into them when I was asking, oh, what do you think makes a good keynote or whatever? Because you've now gone back and watched every Rails keynote and have formulated thoughts about them and what makes them successful. It's very true.

I have more thoughts about keynote specifically at RailsCon than I think maybe anyone has ever spent the time to put together at this point. I've found myself often just in work and project situations, like trying to refer to these things as if they are shared experiences and common talking points that I can share with the team, but I forget that I just have this load of context that pretty much no one has done before. I don't particularly advise someone to do again. So this point, this is the final RailsConf. And lineup is already out.

I'm not giving a keynote. I will never give a keynote at RailsCon because it's now over. But I might give a keynote at another conference some other day. Absolutely. Have you ever tried to debug an issue in production while switching between your error tracker, log viewer, and APM tool?

Maybe you know how painful it is and you can see the error but can't find the relevant logs. Or when you see slow performance, but it can't connect to the root cause. Scout monitoring is all in one platform, built to make your life easier, with log management, performance tracking, and error monitoring coming soon. All of your data will be together at last. You'll go from bug to fix in one place.

The result? Less context switching, faster debugging, and monitoring that actually helps you ship code instead of distracting from it. No DevOps team? No problem. It works with your existing stack and gives you insights in five minutes, not hours.

From bug to fix in one place at scoutpm.com. What would be some tips you would want to give a future Joel who might be giving a keynote on how to give an effective keynote? Yeah, I think for the most part, especially while formulating your idea and digging into the topic and maybe starting your writing or whatever your process is, don't try to give a keynote. Don't try to be grandiose. Don't try to say everything that you've ever wanted to say.

You've still got to stick to one or two major ideas that an audience is going to be able to follow in real time. That's something that you have to always keep in mind with any talk, and audience members are not going to be able to rewind or go back and read the transcript of something that you said. You've got to make sure that people are with you all the time. I've seen in several keynotes live at other conferences during this process where I don't know what was going on inside the person's head, but it feels like they were trying to make the most of this opportunity and say something either very deep and got away from what they were trying to say or they've tried to say everything all at once because this might be their one opportunity to talk to the whole room.

Then the talk just bounces around without doing much, without coming to a point, without giving us anything to think about or walk away with. For the most part, you have to go through it like you would be normally giving any kind of that you would be presenting any sort of topic that you've got to show your interest and your excitement about it. Don't try to make it a bigger thing until maybe towards the end when you're wrapping it up or you've keyed on to something that maybe might flow into something bigger. I think shooting for that in the first place is a recipe for disaster. I feel like in my mind, I've always had a loose dichotomy where a session talk is more practical is making a point and a keynote is trying to build a little bit more broad.

It's looking to inspire rather than to push a particular practical point. It's not like you're saying that maybe that's where things end up, but if you try to go for inspirational with your talk, you might end up messing yourself up. Yeah, I think that's probably true. Unless the topic that you're wanting to present is something that is already broad and inspiring, then trying to force that in is not going to work out really well for you. I don't think there might be some people that can pull it off, but I don't think that's the direction you want to start from.

A couple of good examples of this is in 2022, I'm looking at my notes. Javier Noria gave a talk about the story of putting together Rails new auto loader site work and that could have been more like a normal session because it was technical, it was going through how he did problem solving, it was related to open source and how that work happens and I think because it was both a project that touched a lot of important parts about what Rails is and also because Javier has a lot of great things to say about open source that sort of came together and he had a much deeper message and impact and things that we took away.

But I think that's a combination of having a little extra time, Javier being a wonderful speaker and a great developer who thinks through these problems in a really fantastic way that I'm glad that he shared with us. It led to that coalescing around being a more inspirational talk. Another example is when Vaidhi Joshi talked at RailsConf, I think it was in 23, somebody correct me if I'm wrong there where that probably set out to be a little bit more inspirational and kind of on that half of the thing because she was talking about her experience with burnout and the way that she learned to support herself, support her team and that kind of process of a wider, more life and career moment for her and that's what she wanted to talk about.

So that was the topic. The topic was kind of inspirational and broader just from the jump and so it absolutely can be that but I think you have to have something that you want to say that's in that kind of field in the first place. Otherwise, you might end up not saying anything trying to force it. So you've mentioned how it's important that even for a keynote you should have sort of a focused takeaway for the crowd. Can I ask you what the takeaway is for your keynote or is that a secret?

Yeah, I think that's going to stem mostly a secret. The sort of interesting thing about how this came together is I kind of didn't follow the advice that I just gave a little bit because I didn't watch all of these keynotes before the talks were selected for the conference. I didn't start into this project of 93 hours worth of video until I knew that there was going to be someone that was going to listen to it. So I didn't have necessarily a story or a takeaway because I knew I wanted that to come from having watched the body of work of all of these keynotes. I didn't want to, you know, it's like if you're running a science experiment and you have a result that you think is going to happen or that you want to happen, then you try to fit the data to be that result, then it's disingenuous and it's bad science and I didn't want to do the same thing.

I didn't have an idea and then try to fit the themes of these other speakers into my story. I wanted them to tell each of their story and for something to kind of emerge from the whole. And so I mean, I guess I did have a thing and that was to present something from this collection of talks, but I didn't know what that something was going to be until it kind of spoke to me. And there were a couple of false starts there too that I started to fit to a narrative that I had decided on and I hadn't watched all the things yet. And luckily I noticed it and could throw that out and again let the recordings talk to me instead of the other way around.

I found that kind of thing sometimes happens to me even for like a regular session talk, where I'm writing a talk on a topic and I'm sort of driving towards a particular takeaway and then a sort of a different takeaway sort of emerges as I'm writing the talk and I'm like, you know what, that's a better one. So throw away the initial sort of final point that I want people to walk away with and sort of retool the talk around this newer point that emerged more organically based on the material that I had. Yeah, those moments are fantastic. I think good for you for recognizing those and letting them happen because I think those are often going to be more impactful and they might be what the audience was going towards anyway because if you kind of found that yourself that might have started to emerge without you needing to tell them and then if you didn't go the way that everyone was kind of thinking and feeling which you often always can't know beforehand, right?

But if it happened to you, it's likely going to happen to other folks. And so yeah, follow those instincts, follow those things that are interesting. It's another bit of supporting evidence for being interested rather than being interesting which is something that I've tried to honestly live by but definitely in my talks to be interested rather than trying to be interesting. I'd like to dig into that a little bit more. So this is sort of like you as a speaker should be driven by curiosity rather than sort of trying to put on a show?

Yeah, I think that's pretty close to just sort of another way to frame that. I think if it's not something that you have energy for a writing the talk is just going to be a grind. Also, audiences can tell that, right? How many times have you watched a talk or a show or something like that you've realized this is just a commercial and you've immediately disengaged? Those talks that are like, let me tell you about my company's product.

And it's like, if that's a sponsor talk, great, that's why you're there to find out about this product. But other times you kind of feel like your time is sort of hijacked a little bit. Yeah, it feels disingenuous. So having something that is at least mildly interesting to yourself, I think is really important to having an authentic talk. That's a very vague word that doesn't mean a whole lot because it's gotten pulled in several different ways by pop culture maybe.

You want to sense that the speaker is kind of like speaking from the heart? Yeah. Speaking from experience that they've had rather than experience that they want to have or wish they had and kind of creating a story for it, it's a lot of these weird connections are just happening to my mind right now. But it's a lot like Rails every time a feature has been kind of developed or proposed. That is based on a theory of what people want, doesn't make it into the framework or it does no one uses it and gets dropped from the framework.

That sort of thing, Rails is really strong and successful because it's mostly been extracted and upstreamed from real production applications that have alighted on a shared solution that maybe a lot of people were doing and so has kind of become a foundational thing of a Rails web application and it can be upstreamed into the framework. And so when it comes from a real need or real interest in the case of a presentation, then it's going to land better and it's going to fit. It's going to be more effective. Do you ever find yourself stumbling across an idea that you get really excited or that you feel like more people should know about this idea and then sort of shop around a little bit to find a place that will give you a stage to talk about it?

Is that how your process works? In a way, I have sort of a running list of ideas of things that I think could be talks and that's usually something that I think is going to be too long for a blog post or maybe that text isn't going to be the right format for it. It's not my favorite way to create material. So if something feels like it'll be best as a blog post, I'm not really drawn and interested to it. It's not my medium, so to speak.

But yeah, I'll have this running list of ideas that I am excited about and if I can get through the process of writing a whole proposal and I'm still excited about it, then I'll start sending that around to like Open CFPs and places that I think it'll fit. Is that similar at all to how you go about writing talks? It is. Additionally, sometimes what I'll do is I'll take very copious amounts of notes. I have a poll note-taking system for all these different ideas that I have.

They're usually I break down atomic chunks, so this is an idea for a talk and more of like here's an interrelated set of ideas in a general topic that I've sort of come up as I've been sort of working through a problem or thinking about something or experimenting. Then when conference season comes around and it's time to send it to CFPs, I'll scroll through like, oh yeah, what were the ideas I had in the past year or clusters of ideas that might make a good talk? And I might use some of those. But often I also have something that I'm like currently excited about. I usually have a thing I'm currently excited about or digging into.

And that thing will change with some regularity. And that has bit me sometimes because I'll pitch the thing that I'm excited about for conference during the CFP. And it shows in the proposal because I'll have one that I've written, one little bit more by the book and it's like really solid, really good. And 11th hour decide, you know what, I'm really excited about this other thing right now. Let me just throw something at the committee and they'll never pick it but I feel like I should throw a proposal in anyway.

And then it gets picked over the like really polished proposal I put in earlier. So I think the passion comes through. But sometimes what happens is that I'm really passionate about it. And then it takes a month or six weeks before like the acceptance goes out and everything's ready. I'm ready to start working on the talk.

And now I've got, I've already moved on to another topic I'm excited about. And I've got to go back and sort of reignite that a little bit. Like, oh yeah, what were the things that felt so important to share to others about this? Yeah, that resonates with me a lot. I have had both of those situations happen where that last minute thing really just kind of grabs your eye and you thought you submitted every CFP that you were going to do.

But oh, there's a couple hours left before the deadline. I'm going to throw this one in there. And it always seems like that one is the one that I'll go with. So yeah, there must be some quality in there that comes across. As for the other one, it reminds me a lot about how CGP Grey, the YouTuber and podcaster talks about his video writing process is that he is interested in a lot of various things.

And I think that kind of comes across in his body of work. And he talks about how sometimes a video can take a year to complete. And so he has to be very careful of which of these are just whims that is not going to be interesting enough to sustain him for a year of delving into that topic and which have that kind of meat. I love CGP Grey's content. It's been really fun to sort of see him evolve over the years.

It is sort of YouTube evolved, right? Because of very different place than it was in the early 2010s. But he's still putting out quality content. He is. He's still going strong.

So I think that even caught him by surprise a little bit. But yeah, I love seeing his content. I love that he's still going. So you mentioned you enjoy watching CGP Grey's content. Are there other places you like to watch that are inspiration for maybe your style of storytelling when it comes time for you to be on stage?

It might be a little nebulous to me because I have a background in theater and performing. And so I think a lot of the influences there have kind of subconsciously become influences to how I do a conference talk. So there are some that maybe I can't put a finger on. Hmm. So you can't say like, oh, I'm inspired by this particular Broadway musical or anything like that's like, or even this particular author inspires me in the way I write my work.

There's definitely a lot of that. I think a lot of how I try to write is influenced by this American life. I hear, try to hear my writing as read by Ira Glass. And that maybe is one of the reasons I don't like writing because that's not my voice. And so maybe there's just an incongruity there.

Yeah, some of my biggest influences just personally are silent film comedians. And I don't really know how my love of Buster Keaton influences my conference talks. But I know it does somehow. It's just, it's in my DNA at this point. One person that I can embarrass, I mean, shout out is Nick Means.

If you've ever seen any of his talks are fantastic. They are what I aspire to do, even though again, we have different voices. So it'll never come out exactly the same, which is great. I don't want to copy him. He tells stories that are compelling and interesting.

And he does it in a way that really grabs an audience that really hooks you and you want to go with him. You gladly go with him on the journey, even if it's not about programming or something that you've come to the conference for. But of course, understands what his role is and what he's there to do. And he has something that he wants to say. And it always relates around to shared experience of the people in the room.

Like a technology conference, it's going to come back around to something that is in the zeitgeist of the developers or whomever is in the room. And I know he's spoken at like tech leadership conferences. And so he'll choose some of his talks, I assume he'll choose some of his talks that kind of have those themes in them. So while he might tell a story, the story is really there to illustrate and provide a visceral feeling of an experience to the audience before kind of nailing that point home in the end. One thing I've noticed about your style for a lot of the talks that you've given is that there is a performance element related to it.

So you'll show up maybe in costume or the very sort of detail, the animated way you design your slides, they're meant to tell a story, they're meant to make a point. But they're also in some way a performance. Oh, 100%. This is definitely my outlet for the performer part of me that I don't get to do in the kind of day-to-day work. Conference speaking seems to be a little bit more what I was maybe trying to do anyway in performing, but because there wasn't a shared topic or I don't know what it was, that wasn't actually the right venue, but I feel like I'm very comfortable in these situations and performing in them, like you say.

There is often something in one of my talks that is fun for me to put together. And usually those end up landing really well with the audience, which I'm realizing as we've been talking about it's probably because my excitement for it comes through. But those are the things that can kind of get me through the days where writing and putting together slides can be kind of grind, can be kind of tedious or just you've been working on the thing for too long. And it just feels tiring. I can kind of go back to those moments and sort of revel in the play of it a little bit.

And I look forward to presenting those moments. And definitely each of my talks has something like that. There was talk that had a Dr. Seuss style poem about commit messages. There was a lot of illustrations in my enigma talk that kept me going and kept me interested.

And one that's been described as technologist slam poetry in another of my talks. So yeah, there's always something that's like, this is for me. And I hope when I share it, people like it. And based on audience reactions, when I've been present at your talks, the audience eats it up. They love it.

Thanks. I'm curious. You're going to be on a much bigger stage. And that can sort of elevate you as a figure. And so someone in the audience who maybe is feeling really compelled, loves the talk that you gave, but might feel a little bit intimidated to come up and speak to you.

What are maybe some ways that you would encourage people to come maybe see you later in the conference after the talk? Maybe even just what are some good questions they might have to ask you or to continue that conversation other than just like, hey, man, I love your talk. Because that's the obvious thing to say to a speaker, but it doesn't really lead anywhere. Yeah, 100%. I have been on the other side of that plenty of times.

Like I want to go connect with this person who just moved me or touched me with their presentation. And I just want to go and connect with this person. I think that's absolutely fine. And I love that having that happen after talks, but just knowing that you want to do the connect, and that's what you wanted to have happen. If you don't have a question, like that's great.

That's a fantastic experience. You can have that move along, have that be in sort of the group of people that might be discussing. So like, yeah, make those connections. But I think where I have failed is then waiting for a response after, hey, I like your talk. And beyond like, thank you, there's not very much to say there.

I think in this presentation, it will probably, I'm hoping it'll be fairly easy for someone to get hooked by one of the particular points of a talk. And while most of the points that I'll be presenting are not my own points, but kind of repeating and filtering the speaker that's come before, there might be something that you latched onto, you want to know more about that talk. I'm happy to tell you more about what went on. If you want to talk about what you're interested in, and if you should watch a particular talk, I would love to have that as well. If there is something that you feel I left out from a talk that you've seen in the past, I would love to talk about that.

Given the nature of individuals who have often talked at RailsConf, there might be things that people want to talk about. And I would be happy to do that as well, because boy, do I have thoughts after this project. So coming up then with sort of something that's a good conversation starter or a way to maybe dig into some of the background material, it's a great way for someone to connect with you after the talk. Absolutely. I think it's that interested rather than interesting.

Nobody has fun with an interaction where somebody is trying to come up and be like, well, look how smart I am. It's like, yes, I understand. Everybody in the room is very smart. I'm giving you that respect just as an assumption from the get-go. But yeah, have a question.

Have a question. Have something that you actually want to connect over. Have you found that having a question when you're an audience member helps you to maybe overcome the sense of intimidation to go up to the speaker? Yeah, I think it has helped me actually go up and talk to someone as opposed to doing that sort of just quick connection thing that I kind of wish I had done more than just having that tiny little bit of face time, that little bit of extra spark from a moment that was important to you. And I will often pass up the opportunity to do that because it feels maybe more awkward or like, well, that's not interesting for them at all.

But I know that it is. I know that it's great to have people come up and just say, hey, this was really special or something like that. But that will get me over the kind of activation threshold of actually going up and making a connection. I hear how the situation happened where you're like, maybe a little bit intimidating. I'm going to do it.

I'm going to go up to the speaker. I know they're talking about a famous person. How can I just like put myself into this conversation? It's like, oh, it's Ajini and Aaron Patterson. I can't go up there.

Yeah, I can. Yeah, that definitely happens unless they're like super good friends. And even if they are, they sort of, if they're a frequent speaker, they can't, they understand what's going on. They know that they're also there. Part of being around after their talk and stuff is to connect with people that want to connect with them.

And so if they're just kind of walling themselves off with somebody that they know or another famous person, I don't know. I think that might be a little rude, but it's probably not intentional. It's just that person was there in the room and wanted to do what you're trying to do, which is congratulate them on the talk, give a follow up point, have a question, something like that. Yeah, absolutely. Just so you recognize them, they're not just the person sitting next to you in the audience.

Yeah. Yeah. And I think to the credit of Ruby Central Conference Goers, which are the conferences I've been to the most, the attendees and the speakers is I haven't really ever seen that behavior. Like people are very open and generous with their time after their talks. And so it's always really a lovely experience when I do get over that activation threshold.

Well, Ajini, thank you so much for sharing about your keynote and sort of general thoughts on speaking and keynotes, how to be a good audience member. The conference is happening in a few weeks. It's the 8th to the 10th of July in Philadelphia. So if you're available and going to be there, check it out. Your keynote is on which day?

Day three in the morning. It's gonna be Thursday morning on July 10th for everyone who's out having fun on Wednesday night. Don't party too hard because the real party's coming in the morning. Yeah, I know that that early morning day three feeling at a conference. So I know where I'm at.

I feel you all out there. I know what's going on. I'm looking forward to seeing it. Yeah, I'm looking forward to doing it. I'm not terrifying at all.

No, it's gonna be a lot of fun. Well, on that note, let's wrap up. Great.

Frequently asked questions

How long is this episode of The Bike Shed?

This episode is 43 minutes long.

When was this The Bike Shed episode published?

This episode was published on June 24, 2025.

Is there a transcript available for this episode?

Yes, a full transcript is available for this episode. You can read the complete transcript on the episode page.

Can I download this The Bike Shed episode?

Yes. Use the download control on the episode player to save the publisher-provided media file.