The One Question bounty closes Thursday 10 December.

Join in
We Them Media logo We Them Media Support us

Developer Experience Done Right: Proven DX Strategies to Onboard and Retain More Developers - Joshua

The picture loads from YouTube. The player loads only when you press Play. Turn on captions in the player if you need them.

Joshua, a developer relations engineer at Hive Partners, talks at Web3 Lagos about attracting and keeping developers. He says to know the product, build a persona or audit the current developer experience, drop ego, simplify steps, offer sandboxes and example projects, keep articles short and reward active builders. Each tactic should be measured.

Not by We Them Media Channel: Web3Bridge. Published Tuesday 9 September 2025.

Titles are the owner’s. It plays from their channel.

Transcript

This transcript may contain errors. This video belongs to Web3Bridge. Letters mark each change of speaker.

These are the speakers’ own words. We have not checked their claims.

0:02 A: Please, a round of applause for Joshua as he comes on stage. Thank you very much.

0:06 B: Hi everyone, good evening. Oh yeah, um, I'll start with an introduction. My name is Joshua, I'm a developer relations engineer currently working with Hive Partners, uh, where we provide DevRel as a service to, um, literally- I'm not supposed to say that, but we provide DevRel services to a lot of Web3 companies, big protocols that you guys know. And yeah, that's pretty much about it. So this topic is actually meant for developers, but for some reasons I missed, they moved my flight, so I came in late and that's why we're having it now. But yeah, I'm going to be talking about how to get and retain developers. I think it'd be really helpful if you put up the slides so they follow through. Yeah. So first thing, I have very little time, so I'm gonna rush through it. So first thing, we're going to talk about what is developer experience and why should you improve it? And then lastly, how do you do that? All right. So first, developer experience is how people feel or the result they're able to get out using your product as developers, right? Like I mentioned earlier, this topic is for developers. But yeah. And the reason why- there are a few reasons why. Yeah. All right. Next slide. Next slide. We've passed this. Next, next, next. Yeah, this is where I'm at now. All right, so this is what a typical developer journey looks like for most people. You have ditches from your discovery phase to the scale phase, right? You have a lot of obstacles they have to go through, but your goal as, um, a developer engineer, even a product builder yourself, is to streamline this process and make it as straightforward as possible. Thank you so much. Appreciate it. All right, so but why, why should you even do that? Why do you need to bother to improve developer experience, right? Um, a couple of reasons, some you can define yourself, but for me there are 3 main reasons. First is to attract new developers, right? Then second is to retain and certify existing developers. And thirdly is to meet your KPI so you keep your job. This is a joke for DevRel guys. So, but now how do we do that? Okay, how do we do that? First thing is that you need to understand your product, right? You need to understand the ins and outs of your product. from the business standpoint to the developer perspective to even like a normal community user. Let's say your products also have like a user-facing side where nobody needs to write any code, they just come to use the service, right? You also need to understand that part of it, like every single aspect of it, like deep down, like you own the product. Most of the times it's usually very important if you're the one that owns the product. Then after understanding the product, first thing you need to do- there are 2 things you can do, right? If you don't have an already existing developer experience, let's say it's a brand new project You need to create a persona. You can't really target everybody. It's very tempting to do, but most of the times you figure out you're just wasting time and resources. So create a persona if you're creating your developer experience for the first time. Then the next thing you need to do is to audit. If you already have like an existing developer experience, audit the current developer experience that is existing. See where there are loopholes, things that are meant to be fixed. Then let's- This is the current templates we use at Hive Partners to audit clients', um, developer experience or create new ones when we want to create. So I can share this with any of you if you need it later. Sorry, I'm being very fast. Now moving on next to the solution. So how do you actually- we've talked about why, but how do you actually now do this? You've audited or you've created a persona, how do you now improve your developer experience? First thing is to drop your ego. Most of the times developers have this ego. They try to show that they are really smart, they are building one abstractive stuff, one very amazing technology and they want to dunk it on other people. They want to dump it on other people. And the truth is that people don't care. Most of you don't know the technology that OPay is built on and you don't absolutely care about it. Like, you're using WhatsApp, you most likely know it's React, um, they use React on whatever, but you actually don't care what they used to build those applications. And that is how it should feel in the hands of developers, any product you're building. So first, you need to drop your ego, build for human beings, use everyday terms, use everyday user experience. Then next thing you need to do I just guess I'll just look from here straight. So next thing you need to do is to abstract anything abstractable. I know it's a bit of tautology there, but yeah, you need to really, really abstract. There's no need for you to, um, give your developers or users 10 different steps on how to just achieve one thing. So we need to abstract everything. Let it be that they just need to take one action and then you help them make API calls behind the scene, right? Then the other steps you can follow, you can add CodeSandbox, which is simply a simple tool where They just get to test out your products and see how it works in real time before deciding to build on your own. Of course, there is SDK and there are build kits so they can easily set up and start building whatever product they want to build in minutes. And a very helpful one is to open source example projects so they understand what kind of use cases can be built on top of your protocol or your application. Then, um, yeah, this is a very important one. So you have to make your article concise, right? And make your videos very fun and educative. Now, attention span is very, very little these days. So If you're making videos, you need to make them very, very interactive, very, very fun and educative. Then make- don't write article like you're submitting thesis for approval in a university, right? Very, very short, uh, but, um, helpful articles, right? So the other, uh, method, the other things you can do by adding feedback button to each of your page, each on your documentation site. This has really, really improved developer experience for a lot of our clients at, um, Hype. So when you add this, you notice that people tend to give you feedback on things you wouldn't even notice, things you didn't- your eyes couldn't catch. So it's very important to add like feedback button or feedback functionalities on your documentation site. Then next is to have a dedicated channel for technical discussions, right? A lot of times you go into communities, let's say you're trying to build on a particular product, you go into their community and you're trying to ask a question, but your question is getting overshadowed by people asking about, um, TGE and all that. So you need to have like a dedicated channel where people who are actually building on your product, like technical guys, can ask questions. And yes, you need to host AMAs or workshops. Just host, have a time for developers where they can bring their question and ask you so they feel connected. Then I think for now, last is to recognize, uh, reward active builders. This goes a long ways, like you replicating yourself into different persons. Because when you recognize active builder, what happens is that every single step that you've taken, they go on to do it on their own. That's why you see a lot of people make videos about projects that they are not affiliated with, just because they enjoy working with that project, they tend to make videos, write articles about it, and post because they feel rewarded. Those rewards can be things as little as just shouting them out on Twitter. You don't necessarily need to give them like financial incentive. Then of course, another way to improve this, uh, for big projects is to create ambassador program, right? This is where you now have people representing you in different places where you wouldn't normally reach. And, um, yeah, what gets measured gets done. So you need to actually measure each of these strategies, even the ones that I haven't mentioned here. Whatever strategy you use, you need to measure them to see what actually works and what does not work. If not, if not, you end up wasting time and effort. So I think that's it for now. I'd like to take any question. Does anyone have any question? I guess no. Yeah, that's it. Thanks for listening. My name is Judy, and I'll see you guys next time. Thank you.

More from this hub

Something wrong, or a video you want off this page? Write to wethem.xyz@gmail.com and it is fixed or taken down within 48 hours.