Often, the most important lessons we learn are what not to do.

Today we'll be talking about bad Python code and Python antipters with Andreas Duvez.

It's show number 18 recorded Thursday, July 1st, 2015.

I'm a developer in many senses of the word because I make these applications, but I also use these verbs to make this music.

I constructed line by line, just like when I'm coding another software design.

In both cases, it's about design patterns.

Anyone can get the job done.

It's the execution that matters.

I have many interests. Welcome to Talk Python to Me, a 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 a show and listen to past episodes at Talk Python.com and follow us on Twitter where we're at Talk Python.

This episode will be talking to Andreas Duviz from Quantified Code about Python anti-patterns.

This episode is brought to you by Code Ship and Hired. Thank them for supporting the show on Twitter via

at CodeChip and at Hired underscore HQ.

I don't have any major news for you this week, so let me introduce Andreas so we can get right to the show.

Andreas is a physicist and software developer with a passion for code quality.

He leads the development of algorithms and software at Quantified Code.

Andreas, welcome to the show. Thanks for having me. Yeah. It's great to have you here. We're going to

talk about design patterns, both good design patterns and bad design patterns or anti-patterns,

with the stuff you guys have going on at Quantified Code.

Exactly. So you've built a bunch of awesome tools, both visual, anti-patterns with the stuff you guys have going on at quantified code.

Exactly.

So you've built a bunch of awesome tools, both visual and static analysis.

...