Developer relations

But I don't have to pay attention that closely.

And a lot of stuff I'm doing is one-shotting some side quests that I heard from a customer and trying to validate a sort of DevRel demo.

So I don't have to pay attention that closely.

So I've been watching old documentaries on the American frontier.

free tier? Massive free tier, maybe? Yeah.

also you need to remember that what it goes back to what those AI systems those LLM systems are right so they have been trained on the whole internet and they kind of like show you the most likely answer in principle so maybe neon has a very good Devrel story maybe they are very popular on on social media maybe they are mentioned often in the blog post and that's all those can so all this traditional dev rel things that that that you all have been doing can impact how those those agents answer and like what what what the what what are the main tools that they are choosing so yeah

I think also with just thinking about something to do with the reinforcement of it and that if you use something once, you know, it's then recalling memories.

And so if you say, I'd like to now build something else, it's going to kind of pick the same stack.

And especially with developer advocacy, this is the bit that got lost by the wayside.

I think the internal communication, the being there for developers inside your company, And to allow them to shine outside as well is to me a huge part of developer relations.

But when you talk to people at DevRelCon, for example, they're all like, yeah, I've worked for this startup for three weeks and now I'm working for that startup for three weeks, that startup.

And I'm like, that's just marketing.

You're not doing developer relations there because you don't even get yourself time to get into the relations.

It takes time to understand the product, the platform, the nuances, and also the other people.

Like you said, there are people who are experts in specific parts of the product and also what interests them as well.

And so even if you had four, so we've got a team of four DevRel's, But we're all very different.

I'm just saying, okay.

But you said that you're actually working in this space as a DevRel person.

What is that like? Do you come up with the use cases that you showed or did you have some customer information, some case studies that you could show here as well?

Sure.

Now, one of the things in terms of your career, how you ended up where you are right now, you told me before there was a wild thing.

You had your startup, you did this.

How does that compare to like, I have my own thing and then I'm now doing DevRel for somebody else.

Is it more relaxing? Is it less stressful? What is the career that you would tell people is a better thing to do?

relevance to the...

Because DevRel is my marketing strategy for my startup.

So it is...

makes sense.

That is not as fun as building a game.

No, absolutely not.

But there is a lot of automation value that comes from AI that that is, anyway, that is the next thing on my to-do list because DevRel, well, I do think most conference talks people are giving are just We're in a new generation of Devro.

And so the experience of the former entertaining people has gone away.

And then I said, OK, we should call it something more boring.

And then some of our DevRel people were like, no, absolutely not.

It needs to be called Quack.

I was like, OK.

Mm.

Where we put people, like, from product mindset, from design, engineering, even now some DevRel in the same room-

Mm

... um, so that, um, multiple people can touch the product.

Like, our product velocity has exceeded our ability to talk about these products.

[chuckles]

That's why I'm saying, like, we're starting to embed DevRels into the same room as well.

Right.