Thread by @SerCeMan

Tech podcasts are great. You can't read a book while biking (I tried), but you can listen to a podcast! So here's the list of podcasts that I listen to, as well as my favourite episodes. Maybe you can find something interesting to listen to. 🧵

The first to mention is @corecursive by @adamgordonbell. It's one of my favourite podcasts. It's full of deep conversations. When listening to it, you know - it wasn't just a recorded conversation, the host actually worked hard to make it a story worth listening to!

The Birth of UNIX corecursive.com/brian-kernigha… is a great episode to start from. And I'm sure that if you finish it, it will definitely not be your last episode of the podcast.

You might have heard of IEEE before! They also have their own podcast, which @seradio will soon be hitting 500 (!) episodes. Not every episode might be relevant to you, but surely you can find some out of these 500, given that each one of them is an interesting conversation!

Usually, the conversations on the podcast are based around specific technologies, and many of them might be irrelevant to you. But some are relevant to everyone, e.g. technical writing. You get the taste of the podcast and find some tips in this episode se-radio.net/2020/09/episod…

@software_daily is another classic one. Given the massive number of episodes, more than 1000, and that I've only listened to some of them, I won't give a recommendation and instead just point to the "greatest hits", everyone can choose one of themselves. softwareengineeringdaily.com/category/great…

Inside Java inside.java/podcast/ is a podcast from the Java team at Oracle which means that they have access to the same exact people who build Java, so the content is often very unique. If you're a Java engineer, this one is a must!

Listening to inside.java/2020/11/24/pod… by @chadarimura and @pressron is a good start that can not only give you an overview of the future of lightweight threads in Java but also the future of concurrency in general.

A relatively recent discovery - Software At Scale, softwareatscale.dev/about by @utsav_sha. Lots of insights into the experience of people who've been involved in building large software projects.

The episode with @fnthawar softwareatscale.dev/p/software-at-… is a good example. The whole episode is full of insights, where each insight comes from experience working with large software systems.

@changelog is a beast of a podcast, it explores topics you might've never heard about before. It feels like the hosts run the show primarily because they like these conversations themselves. As a result, you not only learn a lot from each episode but also enjoy the conversation!

It's likely that you've never thought about what it's like to be a maintainer of a font that is hosted on Github. Damn, I'd never even thought about how fonts are developed before listening to changelog.com/podcast/401. Many @changelog episodes give you that "Damn..." feeling.

Have you ever been woken up by a flood of alerts realising that everything is down?! If you have, you can compare your experience to others with the @OnCallNightmare podcast by @jaydestro. And if you haven't, you can learn what it's like to be a part of some of the worst outages.

What kind of outages are you prepared for? How about water pouring down to your servers in a data centre? Listen to podomatic.com/podcasts/oncal… with @tkyocum to see how they responded to the incident.

Tired of tech podcasts? What about true crime? Not just random true-crime podcasts, but in the industry that you know by heart - meet @DarknetDiaries (darknetdiaries.com). You'll change at least some of your passwords after listening to a few episodes.

darknetdiaries.com/episode/85/ is a perfect episode to start, a comprehensive deep dive into the carding industry. And don't forget to support @JackRhysider on Patreon - if anything, the bonus episodes are definitely worth it!

🧵🔚 If you like the list, then the chances are I'll like yours, so I'd appreciate it if you send me your favourite podcasts and the episodes that I should start from.