How we started a podcast

A week ago my friend Pablo and me released the very first episode of Code && Beyond. None of us had any experience in podcasting or ever worked with voice and audio. But we did that!


Almost every weekend for the last couple of years Pablo and I meet remotely to talk about all sorts of things. We discuss software, productivity, creativity, books and podcasts, and many other topics. Recently I suggested an idea to record our discussions and release them as a podcast because I was heavily inspired by Raabe & Kampf podcast. Pablo was kind enough and agreed to participate in this crazy adventure.


Every good project needs a name, and naming things is one of the hardest problems to solve. Options like “Life in development” or “Code and whatnot” were discarded in favor of short and beautiful “Code && Beyond” (AND operator is supposed to hint at software development 😉).


As none of us had any idea how to make a podcast, it was necessary to learn at least the basics of the process. After watching lots of videos on YouTube and reading many pages on the internet, I could highly recommend the following resources for anyone who aspires to become a podcaster:

Kudos to everyone who makes educational resources. You rock!

Final result

The podcast is online and available already on Spotify, Apple Podcasts, Google Podcasts, and other platforms.

Give it a listen at Any feedback is highly appreciated.


It took some time to learn the basics, record, and mix the first episode, but it was a lot of fun. If you are thinking to start a podcast, I can recommend pursuing this idea. You should try not because of possible opportunity to earn money or fame, but just because it’s fun and will make you happy.

Keep trying new things! 😄

Read next

Recently I had an interesting conversation with colleagues on the topic of writing tests for code. In particular, it was about tests for hotfixes that need to be deployed as soon as possible. In this post, I’ll leave the results of that conversation aside and focus on what it inspired me to think about. On the question “Why do I write tests for code?”