People often ask me what podcasts I regularly listen to. Well there are many of them and I won’t enumerate them all here, but I wanted to mention one that I listen to almost every day nowadays.

Markus Voelter started Software Engineering Radio in January 2006. As he describes it on the website, this podcast tries to be a lasting educational resource and not a newscast. You won’t find new product announcements, no tech news of any kind. Only tutorials, interviews, and discussions about specific software-engineering topics.

When I discovered this podcast, about one year ago, I quickly downloaded just the episodes that appeared to be the most relevant to my work. But I found that almost all episodes had something in there for me. For example, recently I listened to the episode on real-time systems, a field I do not work in anymore. Well, at one point the interviewee discussed how jobs were scheduled in certain real-time systems, trying to optimize the total value or utility of the work done by choosing which tasks to perform and which to let slip past their deadlines. And that got me thinking about the Scrum planning process, when the Scrumaster selects, for the upcoming sprint, items from the product backlog in decreasing order of importance until the total estimated time fills up the scrum duration.

Now imagine for a minute that we could get the product owner to assign utility values to each product backlog item. Then instead of selecting product backlog items in decreasing order of importance, we could apply the same kind of decision process and optimize the utility created by each sprint.

(Later that day I went to the library to research this topic but all I found was an exercise from the classic Introduction to Algorithms in which the reader is asked to optimize such a job schedule. The chapter in question was the one about Dynamic Programming, in case anyone is interested.)

Anyway, back to SE-Radio. I’ve found the episodes’ quality range from good to very good, covering a broad range of topics. Perhaps they could be slightly improved with a little bit more structure, and also if the interviewer would stop regularly interrupting the guests with their own opinions. Sound quality has been an issue in the early days (ONE episode in particular was literally painful to listen to—I won’t say which one) but now it’s much, much better.

These days I listen to at least one episode a day, my goal being to listen to all of them. I can really recommend it.