Today we’re happy to announce our new engineering podcast, The Buffer Overflow Podcast. And, our first episode is now available for streaming!
How to Listen
The Buffer Overflow Podcast is now available on all major platforms today, so if you open your podcast player of choice and search for us, we should be there! Here are some direct links:
So, Why Start a Podcast?
It’s built into our D.N.A. here at Buffer to try and be transparent about the things we know, are learning or even have struggled with as engineers. Those are things we want to talk about more openly, and that’s one of the goals of our new podcast.
We plan to talk about topics common to engineering (how we do plan application architecture), to operational things (how do we plan the same features across many platforms) or even remote work topics (how to structure your day).
To kick things off, Joe and myself will be hosting the beginning episodes as we get things off the ground. Expect to hear from more members across our engineering team soon, though!
We hope you find some value from our new podcast, and thanks for listening!
Try Buffer for free
140,000+ small businesses like yours use Buffer to build their brand on social media every month
Get started nowRelated Articles
Every year since 2016 we've closed Buffer for a week at the end of the year. It’s like a reset, except across the whole company.
In this article, the Buffer Content team shares exactly how and where we use AI in our work.
With so many years of being remote, we’ve experimented with communication a lot. One conversation that often comes up for remote companies is asynchronous (async) communication. Async just means that a discussion happens when it is convenient for participants. For example, if I record a Loom video for a teammate in another time zone, they can watch it when they’re online — this is async communication at its best. Some remote companies are async first. A few are even fully async with no live ca