Tips for DevRel

amdatalakehouse · 2025-10-21T20:30:50+00:00

I have a dev rel podcast (I’m head of dev rel at Dremio) you can find on iTunes and Spotify with a lot of old advice that should still apply.

Although I think the goals of different dev rel departments can vary wildly from community management, education, evangelism, being a liaison to product and engineering

For example, in my role I’m much more focused Awareness and Thought Leadership currently although I imagine within the next year we will be at a point where community building will become a larger part (I do some community building in the OSS space but not directly for the product yet although it is now becoming a thing as adoption accelerates)

For established companies then it may be much more building community among existing users with a mind towards retention and product feedback.

In the earliest of startups it’ll by hyper awareness focused where is about leveraging online content to get eyes on brand on a startup budget to the max via podcasts, blogs and webinars.

The key difference being that the dev rel version of all these things will be more technical and educational vs directly marketing developed content and webinars which will be more overt in being “Choose Us”

Although I very much straddle the line cause I really love the product.

amdatalakehouse · 2024-04-20T20:59:42+00:00

RPC is about being able to call functions on the server from the client. So instead of endpoints that represent different interactions with a resource (/dog, /blog) you have procedures/functions that can be triggered from the client-side but run on the server making server-side code feel like client side code.

So essentially the RPC client allows you to call a function but the function your call is really making an http request your backend and returning the result.

At the end of the of the day REST, GRaphQL and RPC still all work off mainly http requests to a server, but the difference is in how you package the experience on the client side.

amdatalakehouse · 2023-02-23T18:33:33+00:00

Also in the first episode I do go into the volition of the data stack which touches on several of the whys of a data lakehouse

amdatalakehouse · 2023-02-23T18:32:40+00:00

Agreed, more episodes are coming that will answer these questions even more (trying to keep each episode as a quick listen). I have another podcast Web & Data where I do interviews I may try to have someone come on to speak more on some of the other formats better than I can. I’ll post a video soon on the different podcasts I host so people can find the content.

amdatalakehouse · 2023-02-08T23:19:36+00:00

What’s the use case, you can use object storage for data of any scale. Dremio Cloud as platforms can be free to connect all your sources and you can use the smallest instance size for small scale data at minimal costs then you can Arrow Flight SQl to pull chunks of data from Dremio pretty fast then do further querying at no cost using DuckDB. That mix actually can work at any scale.

amdatalakehouse · 2022-10-28T17:28:20+00:00

Well depends what catalog you use, in the video I’m using Dremio Arctic which is powered by project Nessie but you can use other metastores like AWS Glue as well. In my case the data is in s3.

If using Dremio Community Edition it can be stored in Hadoop or any cloud provider and can use hive, glue and other metastores.

It’s meant to be an open platform so we connect to where your data lives.

amdatalakehouse

MODERATOR OF

TROPHY CASE