Developer experience for developer events

Speaker 1: I'm gonna tell you a little bit about creating events and, making them really great for developers and give you an idea, so if you were in the sessions earlier, you know I've been doing developer relations for almost fifteen years. I've actually been doing events for over thirty years. Yes, I am old enough to be some of your mothers. I actually did my first professional event thirty years ago. It was, three days long for 3,000 people.

Speaker 1: I had a quarter of a million dollar budget, and I ended up doing that for three years before. As I often have done, as I get really burnt out because I work way too hard, and I travel way too much, and I work way too many hours, and then I took time off and I traveled around the world. And, actually I'm kind of in the same state right now. I'm a little burnt out right now. So, what I'm going to be doing, and I'm I'm the more I tell people I'm going to do this means I really have to do it, and I'm feeling kind of nervous and indulgent about it.

Speaker 1: But I'm actually taking January and February as a sabbatical. And I'm going to Barcelona and I'm taking Spanish lessons. How excited is that? I'm so excited about it. And then we'll come back and we'll do DevRel again.

Speaker 1: So I've been doing events for a really, really long time, and I've done huge events that were like two weeks long with tens of thousands of people. And I've done, you know, hackathons and workshops. And it's always really you know, it's it's it's interesting how many events that you go to that the people who organize them just think about themselves and getting their message across, and they don't really think about who their audience is. So I'm gonna walk you through a process that I went with, actually, Samsung earlier this year. Did anybody go to the Samsung Developer Conference in San Francisco in April?

Speaker 1: One person. Yay. So I was part of the organizing team, for that one, and, we we actually, like, were very systematic about going through developer experience. So this is gonna be show you sort of a big event and how and what we went through, but it's equally applicable to any kind of event, you know, even like this one that you're doing, a hackathon that you're doing, or even something, you know, a workshop that you're doing in terms of what you really need to think through. So I'm gonna start off with just showing you a couple of my pet peeves about events.

Speaker 1: One of them is this, something like this. So how many of you actually host events for your own organizations? Good, good, good. How many of you do like super big ones? Like we're talking really big sized ones.

Speaker 1: How many want to do really supersized ones? I would say, yeah, 500 to a couple thousand people. I mean, those are really big. Once you get over 100, it really changes the dynamics on things. And it certainly changes your budget too and the number of people that you need.

Speaker 1: So this is always one of my pet peeves, especially at developer events. And one of the biggest faux pas, I guess, I saw of this was an event that I went to, I think it was in Nice, probably eight or nine years ago, with the device company that doesn't exist anymore. And it was a developer event. And we went to register, and the developer the registration line for developers, you know, started over here and went all the way down there and snaked around the corner. And then over here was a nice little registration area for all the VIPs who were getting served very quickly.

Speaker 1: It was all the executives, and it was all the media. And it's like, this is a developer event. Those are your VIPs. So one of the things to think about is, you know, when developers are first coming into your event, when your attendees are first coming in, what are you showing them? What kind of experience are you giving them?

Speaker 1: Are you showing them that they're not important enough that you're going to give time and you're going to consider your time? Think about that when they come in. This is a pet peeve of mine. So if it's going to be VIPs, your developers are your VIPs. Make sure that everybody is getting through fast enough and quickly enough when you're really thinking about them.

Speaker 1: My next pet peeve is how many of you this is actually my closet, but it looks pretty darn close. How many of you have had bags like this that you've collected over the years? And especially a lot of these big bags, are just mostly kind of useless, and then you see the branding on them. Do you really wanna rock around with all that kind of branding and all these logos? You really don't.

Speaker 1: So I mean swag and and, you know, how you present yourself, that becomes a part of developer experience and and what you need to to think about too. Please do not give me another bag. Does anybody actually have a really good conference event app that they like? I haven't found one yet. I I truly haven't.

Speaker 1: I've been to so many events, I've tried a lot of different apps. Go to conference. Yeah. Go to conference? Yeah.

Speaker 1: I just find that they're really kludgy, or else they they tend to be a decision that people make at last minute. So the information doesn't quite get in. It it doesn't change fast enough. It doesn't allow people to really interact with it. So that's something else that kinda really gets me all the time.

Speaker 1: But so what is developer experience at events? It really is about that end to end experience that developers are gonna get from start to finish. What it does, it affects how they feel about you and your product, and how they're gonna engage with you later on. And if you don't get it right, you're gonna hear about it on Twitter, but they're not gonna come back and they're not gonna engage with you. And when I mean end to end, I really mean end to end.

Speaker 1: So, you know, think about it prior to the conference. So how are they actually learning about your event? You know, is it is it through a developer portal that you've come up with especially for the event? Are they finding out about it because they just happen to stumble across something even though they're part of your community? They've actually been involved with a number of different groups where, they've actually got a mailing list.

Speaker 1: But it wasn't until, like, two weeks before that they thought, you know, we should probably send an email out to our mailing list and let them know that we've got an event going on. You know? So it's really, again, right from the very beginning and thinking about it far enough in advance, you know, what is that message that you're gonna send and how you're gonna send it? Because that way, you know, they decide to sign up. They probably need approvals.

Speaker 1: You know, I work with a lot of really large companies, and it's like, yeah. This year, we don't want just people from the valley. We're gonna get people from London coming and Berlin, and we're gonna get people from all over the place. Like, k. But these people need enough notice so they could book a flight and so they can get approvals, so they can find a hotel room that doesn't cost $450 in San Francisco.

Speaker 1: And so they've got really time to plan. So you need to, again, sort of think about those things prior to your conference. And, yeah, so they're locking down their travel plans. You know, yes, a lot of you think about what's happening on-site, but you need to think about prior and also about after. And I'll go through a little bit more of the on-site stuff, but the registration, how they sort of navigate even through your venue, what that feeling is all about when they actually come into the venue.

Speaker 1: I know when I I often, again, sort of help companies plan their big events. So I put the t shirt on, and I become Samsung at the event, or I become Intel event, or or whatever it is. And if I see garbage on the floor, I'm gonna pick that garbage up because that reflects on what the event is all about. And actually, was in a at a conference in Palm Desert a couple of weeks ago for entrepreneurs. And I was standing there eating this biscuit, and, all of a sudden, this employee comes up to me.

Speaker 1: He goes beside, and he's picking up a crumb. I'm like, I'm sorry. I didn't mean to make such a mess. And he goes, no, it's mister Marriott. He's coming down the hallway.

Speaker 1: So it was a good, you know, mister Marriott shouldn't have to be coming down the hallway for you to think about how this event is really affecting how people are thinking about your particular company. You know, how are there the exhibits are gonna be a part of it. And also just, you know, how are people connecting with each other? And so I'll show you some of the things that we did, at this past event and how we just made it much more accessible to everybody else. And then post conference too.

Speaker 1: How quickly do you actually get the slides up? Do you actually get the slides up? Or is there a way for people to interact with you afterwards? How do they actually sign up for your program? And, you know, how and how do they, you know, sort of download your API, your SDK, or whatever it is?

Speaker 1: I pulled this off, so you're not gonna be able to read this. Yes. You'll get the slides afterwards. I am what I started to do when we were doing this, for Samsung is we created a started off with a really big spreadsheet and walked through. So you literally walked through every piece of it from the pre conference stuff.

Speaker 1: So, you know, what are people experiencing? What it's gonna look like? And to the from the registration to how people are signing up to which sessions they're gonna go to. So you'll get a copy to see this. I downloaded it offline and then went and sort of recreated something that worked for us in Excel, which didn't work very well up there.

Speaker 1: But it's when you're thinking about experience, it's not just about creating, you know, sort of one more activity or, you know, having some nice stickers that people are gonna take. It really is very much end to end, and you need to be very prescriptive about doing it, especially if you're doing on something on such a huge basis. So again, some people think it's like, well, we'll just add a couple more activities in. We'll have a beer night. You know, that way it's gonna be this great developer experience.

Speaker 1: You really need to think about how to enhance those basic conference operations that that everybody does. Again, whether it's sort of registration or, having room monitors, that sort of thing, and how that flow is. And, you know, think about it, like, how well do you know your venue? How many times have you organized an event and never been to the venue ahead of time? You really need to make that walk through and see how it is and and get a feeling for what those developers are gonna get when they come through the door and and experience things.

Speaker 1: So first thing you're gonna do is think about how developers are gonna interact with your event for all those regular things. Then what we do and what we did is we segmented. We were, again, very prescriptive about who we thought our audience was gonna be and who we wanted our audience to be. And I'll show you some examples of that. And then we carefully selected, you know, sort of a couple of activities that directly spoke to those segmentation and those personas that we came up with.

Speaker 1: And then it's about staff too. You've got to have the right amount of staff, but you've got to motivate the staff and make sure that they become quite high touch in things. Oftentimes, you'll find staff another pet peeve of mine at events is, you know, the developers often are not really great at reaching out to each other and talking to one another. And so you'll get all the staff sitting together at the event or at the lunch, and they're all sitting together at the same table. And meanwhile, here's the developers that the event is actually for, and they're not interacting with them.

Speaker 1: So the staff that is gonna be part of your event and the volunteers that are gonna be part of your event actually need some really great training to to to understand. And if there's a way to incent them to be more frontline, more hands on, more evangelistic, you're gonna need to do that. And it's not all necessarily you know, if you've got some of your product engineers there, it's not necessarily in in their natural behavior to go out and talk to people. But sometimes you just need to give them goals and say, you know, just meet two new developers today, and you don't have to meet anymore. And often you'll find once they start to meet one or two, it makes it much easier for them to just go up and go, you know, hey, I'm Bob.

Speaker 1: I work on such and such a product. What do you think about it? And you may actually have to be very, again, prescriptive about it and go, I know you don't really like talking to people, but here's a script for you. Here's what you need to do. Just say, listen.

Speaker 1: Here, I'm Bob. This is the product that I work on. What do you think about it? Or what could we do better? Great.

Speaker 1: Doesn't that make it easier for you to go and do that? Yes. So make sure that the staff becomes quite high touch as well. So you're gonna have to come up with some corporate event objectives. And so here's some of the things that I I've tried to genericize some of this so it wasn't sort of a direct copycat of everything that Samsung was doing.

Speaker 1: But, you know, usually an event is about generating awareness and strengthening your relationship with developers and getting them really excited about what you do. Maybe you're launching some new product, some new information. So make sure you know what your objectives are upfront, and make sure you share that with the rest of the staff. Then next comes measurables. We're all really good at that now.

Speaker 1: Right? Here's again, I kind of changed things around a bit. But some of the measurables that we came up with for this event. We wanted so many people to register. We wanted some of them that were just not from the Bay Area because you tend if you ever held an event in the Bay Area, you tend to see a lot of the same people.

Speaker 1: No matter who's doing the developer relations event, it's a lot of you know, 25% would be the same people. You know, we wanted to get make sure that there was a really good survey rate. Wanted to make sure that the sponsors were well taken care of, which is another really big piece of developer experience as well. We wanted them to re sign right away. And we wanted to track the number of impressions across a number of different ways.

Speaker 1: So, you know, your measurements may be some similar topics, some different ones, but you definitely need to have them because then you're gonna it'll help you in terms of how you put your event together and then how you measure it afterwards. You really need to to come up with some goals ahead of time. So when we're thinking about sort of the the developer experience, again, it's about those touch points and it's about everything that they're gonna experience. And I didn't put taste up there, but, you know, actually food makes a really big difference. And and I've held more events in the Valley than I've had in other places, but the food at the Moscone is like really bad.

Speaker 1: But you've gotta you've just gotta kinda, you know, work with that a little bit. But, you know, so think about what are what are developers gonna see when they first come into your event? And, you know, certainly for a lot of the bigger companies, they spend a ton of money on, you know, you know, big pillars and lots of color. And if you've ever been to either the Google IO or the Intel events or any of those kind of things, they spend a lot of money. You don't necessarily need to, but you need to be really thoughtful about what they are gonna see.

Speaker 1: And signage is just is just such a big one. Another pet peeve of mine too is when you're going through events and you have absolutely no idea where to go. That's such simple signage to do. It's just such absolutely simple signage to do. These are developers.

Speaker 1: They want to get a chance to touch something and play with something and find out with maybe you got some new devices or they want to learn and do coding. So make sure you're adding that into your sessions and you're making the time for it. Surprised at how many developer events that are out there, and all they want to do is talk at you. That's not a developer event. Developers really want to get touch and feel and try things.

Speaker 1: But they also very much want to meet you. They really do wanna meet you. And, I know we talked about hackathons yesterday at at the at the workshop. And, you know, if you really need to have a dedicated team, again, that's gonna be those people that are gonna make sure that, you know, that you're shaking as many hands as you can. Think of yourself as politician a little bit.

Speaker 1: You really gotta go out there and kiss some babies, but people want to meet people. That's why we hold events. If you didn't wanna meet people, you know, hold a conference online or, you know, do something on a Google plus channel. Don't spend all that money on big events if you don't want to meet people. You really need to be able to do that and make sure that the teams are in place and that they're really prepared for it.

Speaker 1: Well, that didn't turn out so well based on these slides. But everything attendees see, hear, perceive, learn really affects the way that they are excited about you, feel empowered to do something, get recognized for what that they do, and really motivated to work with you. And that, you know, helps support your corporate goals in the end because that's what this is all about. Right? So firstly, it's about getting the basics right.

Speaker 1: So, again, it's that communication. You don't want a lot of marketing speak. This is a developer relations event. Why do you want people to come? What are they gonna come and learn?

Speaker 1: What are they gonna get out of it? Be very, very clear about that. Make it really, you know, clear about what it is and and who else is gonna be there. And so, you know, make sure you're talking to developers. Make sure it's not just your marketing team that's coming up with marketing speak.

Speaker 1: It really should be developer relations people that are involved in it. Know, emphasize technical benefits. It's not just about, you know, coming and having fun and hanging out. It's it really is about things that they're gonna learn. And, again, we target it to personas.

Speaker 1: Registration, as I talked about, some of my pet peeves are those really long lineups. So think about, you know, what is that process? How are people being greeted? For this particular event, we hired this company that had what they called the Disney way of doing things. So if you've ever been to Disney, you know, gets a smile.

Speaker 1: Everybody gets a hi. How are you? And that's what we wanted to make sure too. Everybody that gets involved with scene developers, all the volunteers at the front, hi, how are you doing? Really glad to see you.

Speaker 1: That is such an important thing to do and goes a long way in how people are going to feel about your event. Signage, boring swag, of course. So, yeah, we had the greeters and really easy to read maps, schedules that were really clear, signage that was really clear. Within your keynotes, your workshops, and that sort of thing, I was gonna try and do it with Phil, but but we didn't didn't quite do it as well. But another thing that kind of is a is a pet peeve of mine and really important for developer experience is is introducing the speaker, you know, and welcoming people to the session that you're at.

Speaker 1: Again, how many times I've been to, and you've probably been to sessions where you kinda, you know, you sit in sit in the room and you go and all of a sudden the speaker starts talking. They don't even say hello to you. Like, does that make you feel welcome? It really doesn't. So every one of your speakers and what we did is we we put together, not just speaker information that says, you know, you've gotta be here at 09:15, and please, you know, spend take fifteen minutes for questions.

Speaker 1: It's like, here's what your introduction is gonna be. You know? Please say hello. And it's also great too if you've got somebody that's introducing you because it just, you know, just makes again the room feel a lot better and to thank you for being here rather than just, okay, my my session's done now. You know, everybody kinda looks around going, okay, does that mean we leave?

Speaker 1: Do we you know, what do we do? So, you know, thinking about having all those pieces in place, and it takes a lot of extra people, but the the feeling that that creates and that experience that creates is just so well worth it. And, you know, especially for a lot of you with bigger companies, use your developers to do it. They a lot of them actually like to do that sort of thing. They wanna be what we call door monitors or greeters.

Speaker 1: Let them do it. You know, if you've got enough money to hire people, great. But often, it's it's some of those developers. You know, give them a free pass and an extra extra bag you've got in the back or whatever it is. Or, you know, and, you know, invite them to a VIP party because they've been really helpful for you.

Speaker 1: But, you know, giving them the opportunity to participate in that sort of way is great. And we've certainly done that. Has anybody been to one of our whip jams that we used to do over the over the years? Thank you, Rod. We used to do big developer events ourselves and used a lot of people from the developer community to to help us be room monitors.

Speaker 1: And they were just they were so excited to help out. And, you know, those are some of your greatest advocates that can be supportive for you too. I'll show you some of the stuff we did too with helping people actually meet. You know, again, having your staff be prepared, but there were some other ways that we went around doing that too. And again, sort of thinking about, you know, what are those meals?

Speaker 1: You know, you you you can't change the menu at the Moscone, but you can certainly make the experience better than than just the way it is. So you'll get these slides, and you'll get a chance to look at it. But I got a few more that I that I wanna go to. So, you know, after you've thought about just some of those basic pieces, it's really important to think early on who actually has come into this conference. Is it just it's developers.

Speaker 1: But what kind of developers are gonna be there? So, you know, what kind of skills are you focusing on? Who are these people, and what kind of you know, what what do they want to see from you? Are they interested from Samsung? Was it, you know, was it wearables?

Speaker 1: Was it IOT? Was it some of the new devices? Really, what was it that we were gonna showcase that was gonna be there? You're looking at big companies, small companies. Where are they coming from?

Speaker 1: And what are the roles in these companies? Because different roles, as we know, have got they've got to make different decisions about things, and they want to see some different things. So you really need to think through that. Once you've thought through that, you know, you start to then sort of form things into the personas of the companies. We happen to look at this going small companies, big companies, startups, enterprises, indie brands.

Speaker 1: Looked at the type of company it was, who from that company would probably attend, and actually what was their interest the company that we were representing. It's really important to think that through. And then what we did was went and looked at all those different sort of four personas of them and said, okay, so an indie developer's coming. What does he wanna see? What does she wanna see there?

Speaker 1: Interested in any kind of new technology? Definitely wants to see some demos? Oh, we haven't thought of any demos yet? We better get some demos happening. What does a brand wanna see?

Speaker 1: They're probably not gonna send a lot of their, you know, developers that are there. They wanna actually talk talk to you as a partner. They wanna have some more meetings. They wouldn't wanna see demos. They probably wanna see a private demo.

Speaker 1: So have you thought about that? If you're if you're talking about bringing enterprises in, you know, who is it from the enterprise that's gonna be there, and and, you know, what kind of angle are they looking at? So they're gonna all these different kind of groups that you're bringing in and you're thinking about for your personas are gonna wanna see something different. They're gonna wanna touch something different. They're probably gonna wanna learn something different or learn about it in a different way rather than, you know, coding versus finding out more about a product road map, for instance.

Speaker 1: And they're gonna wanna meet different people. A lot of the indies, they all wanna meet your rock stars. Right? Or they wanna meet some of the partner rock star developers that are there. So so bring them in, let's do some of that sort of thing.

Speaker 1: Your brand and enterprises could probably care less about those kind of people. They wanna meet the decision makers in your company. That's who they wanna make, make sure those people are accessible. So to make it a little bit easier for for staff and for us thinking about things, we actually came up with some people. So we had coders, and, when we thought about what could we actually do specifically for these folks, we had hands on coding sessions for them.

Speaker 1: Very specific times on some specific things that they could do. For the startup entrepreneurs, they wanted to have some pitch sessions. And so we organized some pitch sessions for them where they could actually get in front of some accelerators and and investment types. For the enterprise technologists, they wanted to see roadmaps. Know, they've got a plan what they're doing and that's what they wanted to see.

Speaker 1: So we made sure those kind of sessions were set up for them. For partners and sponsors, again, they wanted to see execs. So I'm just gonna run through then a couple of other of the sort of generic things that we ended up doing that enhanced that overall experience, but weren't just done because it was kind of fun. They had a very, very specific meaning and and reason behind what we were doing. So we had something what we called the flare program.

Speaker 1: And so these are little buttons that we made up. And we put them sort of strategically around all the different levels of the Moscone so people could go and get them. And we had them for different roles. We had them for different expertises. So anybody who was in IoT from wearables to whatever.

Speaker 1: We also had them for some different interests. So, you know, were you a beer drinker? Were you a wine drinker? Were you a gamer? Were you, you know, into skateboarding or cycling?

Speaker 1: And then some some specific for Samsung ones based on partners, and they were actually at partner booths, you can go and get those. And we did it for a couple of reasons. I mean, we wanted to showcase partners, so they were really excited about it. But we really wanted to give developers and and other people too an opportunity to go, oh, hey. You're really into wearables too.

Speaker 1: It gives that, you know, people an opportunity to have to start a conversation where sometimes it might be a little more uncomfortable to do that. Because for you know, I'm I'm not scared to go up to somebody and go, hi. I'm Carolyn. You know? How's it going?

Speaker 1: But not everybody is like that. So if you give somebody a little bit more opportunity to talk about things, you can do that. And we actually did this at an at an AT and T conference a number of years ago, but, this time we made it much more really sort of really more specific, and it was something that we had over the course of the whole conference. So not all the badges went out at all of the same time. So people really got into it.

Speaker 1: Like, they really like, you know, they started to collect them, and they got really excited about it. And just a couple more slides, I'll show you something we did called dev dollars. But what we ended up doing too is, you know, I'd have a bunch of dev dollars in my back pocket, and if somebody was having a lot of badges on them, it's like, give them a dev dollar, they could go and spend that on something else. So people tweeted about it. So in terms of, you know, what did it do for the conference?

Speaker 1: For developers and their experience, it gave them a chance to meet people. It was something exciting. It gave them a chance to win prizes as well, really make those connections. For the company as a whole, it was great for social media. It was great actually for measuring which pins were more exciting than others.

Speaker 1: So there wasn't a level of measurement that happened there. And people just were really excited about it. So, you know, every time we bring out a new bag of pins, we just had people following us all over the place. It was really a lot of fun. The other thing people don't often think about is what they do at the developer parties if there is gonna be one.

Speaker 1: And time and time again, and if you've been to any of our events and some some of the ones we've done for others, we always do a paper airplane contest. And I know for a lot of your companies, and I'm a big rocker from way back. I love bands. And I'm always the one that gets right up at the stage, and I'm rocking. But you know what?

Speaker 1: Most developers aren't like that. They're the ones that are still in the hallway wanting to, you know, do some of the different activities. And a lot of money is spent on bands. Like billions of dollars can be spent on these bands that maybe 5% of your audience is actually gonna watch. At this particular conference, we had hundreds of people participating in the paper airplane contest that cost a total of like $5 worth of paper.

Speaker 1: $5 worth of paper, and I also got some electric tape in some different colors to measure, like, you know, here's the starting line. And it was, you know, was a flip chart, and I drew a bull's eye. That was it. Comparison of millions of dollars that was spent on the band that, you know, kind of 50 people were interested in. So it again is you gotta think about what are some things that everybody can do that gets everybody really interested.

Speaker 1: And and interestingly enough, after the contest was over and the band had started, there was still more people still throwing paper airplanes around than there was listening to the band. And then we had some some champions that we got in as judges. So, you know, started to sort of integrate everybody working working together. And it was just a way again, we had a number of other things that we that we did at events. Giant Jenga still works.

Speaker 1: Do you believe that? It really does. Gets people talking, and it just really is a way for people to interact. We had some drone racing, which I think I crashed one of the earlier ones. I'm not very good at it.

Speaker 1: But there's a lot of other things that you can can do that are pretty inexpensive, but get people talking and get get people really interacting. That's really important. The other thing we implemented was something, again, with staff that we call the Staff Smile Program, is we incented staff. We incented them with what we call these dev dollars, which is my last slide. We gave them badges, so, you know, they felt a little more empowered to get out there and ask.

Speaker 1: But people always also knew that these are the people that I can go and ask. We tried to so this says test my superpowers. How can we help? I wanted it to be a little more edgy than that, but it didn't get my way. But they were kind of, again, fun rather than just, you know, here's my name tag.

Speaker 1: I'm here to help you. You know, laptop stickers, I'm sure a lot of you have that. Those are great things to to have as well. And then the last thing I'm gonna show you that we did is we implemented something we called dev dollars. And it it was crazy.

Speaker 1: So, you know, there's often like, how do you get people to visit your booths? And there's the passports and that sort of thing. And what we decided to do was have these dev dollars where people could collect certain values and then go and purchase things. And again, it got people really excited. It got people out to the booths.

Speaker 1: It actually got like really boring booth people to actually engage with the people that were coming to their booths, so that was sort of part of the initiative behind behind that one. The other thing that it ended up doing was they had to go and collect their prizes, which they turned these dev dollars in for at the store. And so it gave them an opportunity to see the new devices, to see the new wearables. And it actually wasn't a goal of ours to increase revenue in the on-site store, but it it was it did such a good job. It really worked out really well.

Speaker 1: So again, you know, met corporate goals, but also gave developers a chance to have some fun. And then we had prizes that was everything from, like, for 1 dev dollar, you could get, like, a back scratcher. Like, they're kinda little silly things like that, to if you collected enough of the gold ones, you got devices. So of course, everybody likes who doesn't like a free device? So there were two of us that were the developer experience police, and we did make sure that we went through every one of them, every piece of before, during, and after.

Speaker 1: We took a look at, again, the basics that you wanna take a look at. We we made up the personas and thought, you know, here's what we can do for these people. And for Samsung, it truly was the best event that they've ever held and sort of learned a lot in the process as well. So thank you very much. I hope you learned a little bit about developer experience.