Learning about programming libraries and languages is useful and interesting, but sometimes knowing why

certain decisions were made or the history leading up to some change or a package being created gives

you a deeper understanding. And that's what this episode is all about. You'll meet Mike Driscoll,

who runs Piedev of the week. He also just published a really relevant book. Python interviews discussions with

Python experts. This is Talk Python to me. Episode weekly podcast on Python, the language, the libraries, the ecosystem, and the personalities.

This is your host, Michael Kennedy. Follow me on Twitter where I'm at M. Kennedy.

Keep up with the show and listen to past

episodes at talk python.fm. And follow the show on Twitter via at talk Python. Before we get to our

conversation, I want to tell you about a project I've been working on for the past three months.

Do you remember Bob and Julian from episode 140, where we talked about the 100 days of code

challenges and their projects around it?

Well, since then, we've teamed up and created a new course, 100 days of code in Python.

This course has 18 hours of video lessons and around 80 hours of guided exercise.

That's 100 hours, one for each day.

If you're considering doing one of these 100 days of code challenges, please have a look at our course over at talk python.fm slash 100 days.

Now, let's get on to the interview.

Mike, welcome to Talk Python.

For having me, Michael.

Yeah, it's great to have you here.

I've been a fan of your Python Dev of the Week project that you've had

going for a long time and things like that. How long has that been running? I think it's been going

on now for almost three years. Yeah, that's pretty good. That's like 156 interviews or something

...