I agree, you speak too fast, and use "like" and "basically" way too much. See if you can find a way to improve your diction.
Another thing, in most episodes, it seems like you have a list of questions that you want to ask, and you quickly go through them, as if you just needed to check them off the list.
And I get it, any application running in production consists of multiple pieces and involves many decisions, but just listing all of the components one by one, turns into reading the specifications on the back of a cereal box.
Maybe you could pick one or two particular aspects of the infrastructure and discuss those in greater depth. Ideally something that either you or your interviewee feel very strongly about. I'd also be interesting if you challenged some of the decisions that went into the infrastructure. All too often you agree too easily with your interviewee.
Overall however, none of these should be dealbreakers. I still listened to many episodes.
Thanks. Using filler words is one of those things where it's easy to notice when editing or listening to it later but near impossible to notice in the middle of a regular conversation. I do try.
You are right. I do come into each episode with a number of high level bullets. I always try to stay on track so each episode flows roughly the same. Basically (:D) learning a bit about the service, team size, how it's built, how it's deployed and lessons learned. If some of these get skipped, it feels like an unfinished story that goes against the premise of the show? It's interesting to hear you think otherwise and would rather go deeper on a smaller subset of topics. I thought maybe that would make it even more niched down.
I'm happy you brought up the part about tech choices. I do try to pry out the "why" on a number of decisions. There's a fine line here. I kind of wonder which episodes you watched because I thought I challenged them kind of a lot but I definitely keep myself in check to avoid coming off too combative even if they are asked in a friendly way. But I did try to always call out questions that I really feel most listeners would be thinking.
Another thing, in most episodes, it seems like you have a list of questions that you want to ask, and you quickly go through them, as if you just needed to check them off the list. And I get it, any application running in production consists of multiple pieces and involves many decisions, but just listing all of the components one by one, turns into reading the specifications on the back of a cereal box. Maybe you could pick one or two particular aspects of the infrastructure and discuss those in greater depth. Ideally something that either you or your interviewee feel very strongly about. I'd also be interesting if you challenged some of the decisions that went into the infrastructure. All too often you agree too easily with your interviewee.
Overall however, none of these should be dealbreakers. I still listened to many episodes.