Hello and welcome to Python Bytes, where we deliver Python news and headlines directly to
your earbuds. This is episode 198, recorded August 31st, 2020. I am Brian Okken.
I'm Michael Kennedy.
And we're joined by a guest. We have Annalena Popkus.
Yes, that's very correct.
Wonderful. She's been on Michael's Talk Python podcast a couple of times.
Absolutely.
Or at least once.
It depends how far out in the future. I think in the future twice. We've already recorded a
couple shows together, but we've got quite a buffer there. So this one will be out before.
So one and two times. And welcome to this show. Nice to see you.
Yeah, thanks for having me.
I'll kick it off with the first topic.
Give us something easy. Don't make it hard, Brian. Come on.
Yeah, actually. So when I remember, it's been a while since I shifted of thinking about Python
as a scripting language to as a full-blown language to do everything, big applications and stuff.
Of course, I still do both. I use it for a quick scripting language, but also more meaty
things. But back in the day when I was using Bash, if I wanted to have a little script to do with
arguments, I'd have like an example Bash file that I would just keep copying from. And I was thinking
about that because I would never remember how to do arguments and stuff and parameter passing through
into a little script. And the same is true for Python with arg parse. But we have Google now to find that
information out. But I was thinking about that when I saw this comment on Twitter. It's from Joshua
Schreiber. And he said,
every time I write a Python script, I have to go back to an old script of mine to remember how to set
up arg parse. For some reason, it just doesn't stick in my mind at all. And then Ken Yewans Clark,
and I think he's been on your show, hasn't he, Michael?
No, I don't think so.
Okay.
Probably should be, but hasn't.
He commented and he said,
I've got this little utility called the new.py. So I went and checked it out and I'm pretty happy
with it. It's not something you can pip install and we're going to link to it in the show notes. It's
just part of, he's got a repo for it. And I think he uses it in a book that he wrote, but basically what
it does is you, you run it and give it a file name and it gives you a little starter script with all
arg parse stuff with examples. You've got an example, positional argument, a string argument,
integer argument, file argument, and a Boolean flag. So you don't have to look that stuff up.
They're already there as dummy ones. And then you can, you know, add to it and whatever,
delete the stuff you don't want. So just in, if you've got this around, you can use it to
spin up a new script really easily. And he also just recently added test code for it. So if you
pass it a dash T, it'll generate a little stub test file so you can test your script with it too.
So anyway, if you're using Python for scripting, I think this is a good thing to look at.
I love that. I have the same problem every time. I always copy it from an old script every time.
I was thinking the same thing. Like what is one of the big difference between beginners and experts?
Experts have a whole bunch of these old things they can go copy from.
Well, I often use, so I'm usually using click or what's the other one that's...
Typer. Typer.
Typer's the business.
Yeah. So I'm usually using those for larger applications, but there's a lot of times where
you're passing, you have a shared script that you don't really want to have install anything extra.
So ArgParse is still something to use for a lot of stuff.
Yeah. Very cool.
Yeah. If you don't want arguments, I'm sorry, dependencies, this is a great example there.
Because if your script could literally run without a pip install or without a virtual environment,
except for that, you know, I probably would just have a slightly more cumbersome bit of code
and have it easy, easy to run, you know?
Yeah.
I've been thinking about how I should really be building more CLI-based applications.
And I have an insane number of these little, what I would really call scripts.
They're not applications.
They're like little tools that I just use to run all the stuff around my company.
So for example, one that I wrote last week was I had a company that did transcripts for the video
courses and then they stopped doing that.
You know, it's fine. They moved on to doing other things, but all of a sudden I had to figure out,
well, how do I get transcripts again?
So I wrote a little script that would go find all of the videos in a course,
see if it was missing transcripts, go and use AWS transcribe and just say the videos in AWS S3,
do this and then download it and turn it into sentences and subtitles and video.
So there's like 50 of these.
And I'm at the point where I almost think I might just make one command line option to run
every one of those scripts, right?
Like kind of like Git with sub commands, like TP space transcripts, TP space video and code,
right?
Like I'm almost ready to build this huge CLI thing.
And I probably won't use arg parse though.
I'll probably use typer.
Yeah.
Sounds like a good idea.
Yeah, exactly.
Cause I always forget.
I'm like, did I write that?
What's it called?
How do I run it again?
To track it down.
So this next one comes to us from a listener.
Exuma is the username.
I didn't get a first last name.
So thanks for sending that over.
And it's called D beaver, D beaver, something like that.
So it's for databases and has to do with beavers.
So D beaver database UI tool.
And something about working with databases inspires people to use animal names or creature names.
So this is D beaver.
And the one that I mentioned that started got Exuma saying, Hey, this is cool, but you should also check this other one out is I mentioned beekeeper at beekeeper.io, which is really, really cool.
So here's another cool free open source database GUI tool.
So if you got to work with databases, this looks like a really nice one.
Yeah, it looks pretty cool.
Yeah.
You know, it doesn't have the full on marketing, beautiful page.
Like if you go to beekeeper studio, sorry, beekeeper studio.io, man, that thing looks like it could be a VC funded startup like landing page, right?
Whereas D beaver is nice, but it doesn't have, it doesn't look like ultra polish, but it's based on a clips and it supports 80 different database types.
So obviously the popular ones like my SQL, Postgres, SQL lights, Microsoft SQL server, and so on, but a whole bunch of other ones as well.
So yeah, if you got to work with databases and you want some kind of UI tool, this looks like a pretty good option.
Do you have an idea why they called it beaver?
I have no idea why they called it beaver.
It's funny sometimes since in machine learning, they had a trend that they named the models like Sesame Street.
Do you say Sesame Street?
Yeah, yeah, yeah, yeah.
And they started calling them bird.
Like Grover and Big Bird and all this kind of stuff.
Yeah, and someone started it and then the others just continued naming the models like that.
It was a lot of fun.
Yeah, it's really fun.
Last episode, which isn't out yet, so there's no way you would have heard this, but we were talking about something on Debian.
It was going through the Python Docker script and understanding what it means to create a bare-bones Python system.
And you found out that Debian names their releases after Toy Story characters.
I like that.
Yeah, that's nice.
And of course, you were doing all of your stuff with 100 Days of Code and Harry Potter, right?
Which is also pretty awesome.
But there's not really releases for that, is there?
No.
So let's see.
So a couple more things that are interesting about DBeaver is it's got a nice GUI interface.
It has dark mode, light mode, and whatnot.
It has support for cloud data sources.
So if you're going to connect to, I'm presuming things like hosted databases like SQL Azure or something like that.
But it also has extensions that allow you to work directly between databases and Excel or databases and Git, which I think is pretty cool.
And it also will build UML entity diagrams, like show me the relationships of this table, you know, where the foreign keys go and all of the things like that visually, which is pretty nice.
If you're just like given a project, here's the database.
You're like, oh, what the heck did I just get?
Right.
You could open it up in something like this.
You know, PyCharm Pro has something along those lines as well.
But this is really an open source.
So that's pretty cool.
Yeah, I use the one for PyCharm Pro for and the diagramming helps a lot to be able to visualize what your data is doing.
Totally agree.
I use it all the time.
Yeah.
All right.
Well, that's it for DBeaver.
I think it's cool.
People can check it out and compare it with Beekeeper Studio.
Great.
So I want to talk about PDB++.
So I was always using the IPython debugger when debugging, but I recently switched from using IPDB to PDB++.
So PDB is the Python debugger, like the normal one that's part of the standard library.
And PDB++ is an extension of that.
So it's fully compatible with PDB, but it has some pretty nice features.
And I think they improved the debugging experience quite a bit.
It's very easy to install.
So you just type pip install PDBPP, since PDB++ is not a valid package name.
And I have two favorites.
Like it has quite a few additional commands and features compared to PDB, but it has all the usual commands that are also part of IPDB.
So it's very easy to switch.
But there is the sticky mode, which I like a lot.
So the official description is that when you're in the sticky mode, every time you change the current position, the screen is repainted and then the whole function is shown.
So when doing step-by-step debugging, it's very easy to follow the flow of execution.
And I find it very annoying to always type L or double L to see the code.
And with the sticky mode, you can just always follow along with the code and the flow of execution.
And then there is smart command parsing, which I also like.
So if you have or if you're using PDB, it always tries to interpret the commands you enter as one of the built-in commands, which can be quite inconvenient in some situations.
For example, if you want to print the value of local variable and that one happens to have the same name as one of the commands, for example.
Oh, no.
Yeah, that could.
And I had that quite a few times.
So, for example, if you call something P or C and then you want to print the value of that variable, but it is interpreted as the command continue, which is C is short for continue.
And I think PDB++ has quite a nice solution for that.
So when there is ambiguity, so if you have a variable with the same name in the current scope, then that variable is preferred.
And if you still want to run the command, you can just prefix it with two exclamation marks.
But if you don't have any ambiguity and you type C, then it will always be continue.
And I find that very convenient.
Oh, yeah.
That seems like a great little feature.
And it just runs in the terminal, right?
So you can run it anywhere that you have SSH access to or something to that effect.
Yeah, I think it's a very nice package.
Maybe this is a dense question, but why use this over like an ID?
Oh, I just always use Vim.
And that's why I got so used to using Vim that I find it very convenient to use PDB or IPDB or now PDB++.
I guess I would have to start using an IDE properly to really be able to appreciate it.
And yeah, I don't think I can switch back to an IDE for a while.
Yeah, it has some cool features as well down here.
Like one of the things is if there's an exception, you can ask it for a postmortem report and it'll give you like extra details in there.
You can also do stuff like break on set attribute.
So if some kind of attribute is set, which is, I guess, a little bit like a conditional breakpoint and say an IDE or whatever.
But yeah, it looks pretty cool.
I like the fact that it has syntax highlighting and color and all that.
Yeah.
And autocomplete.
I know that it can be quite nice in an IDE too.
I think on the last Talk Python episode, it was on the Python.
How was that episode called?
It was called the Modern Python Developers Toolkit by Sebastian Witwaski.
Yeah.
And you talked about Visual Studio.
And yeah, I know that it has quite a few features as well.
But when you're used to something like IPDB, this is a very nice addition.
Yeah.
Yeah, absolutely.
And you can also, what's the double exclamation point thing?
So you mean what I just mentioned with the command?
Yeah, yeah, yeah.
Like when would I run that?
So if you have like a variable C and that has some value, so it's a local variable, but you want to run continue in this case.
Oh, I see.
Then you would have two exclamation marks and the C.
Yeah, so that's why it skips it.
Okay, got it.
I understand now.
Cool, cool.
All right.
Yeah, this, you know, I live largely in the IDE world.
But if I needed to do some debugging outside of it, this is a really nice option, I think.
Like maybe in a Docker container.
And I don't want to set up like remote debugging and all that kind of stuff.
I just want to run it.
What's it doing?
Yeah, that's cool.
Nice.
Oh, yes.
Today's sponsor is us.
So thank you, us.
Thanks, us.
We'll probably have to edit that section.
Today's sponsor is both Talk Python training and Test and Code podcast as well.
I wanted to highlight.
I had some, I think last episode I mentioned that Adam Johnson, which hadn't actually, he
hadn't actually been on our show yet.
But the last episode of Test and Code 128, I did have Adam Johnson on.
He is the maintainer of pytest randomly.
And so we talk about what the importance of randomizing your tests to make sure that you
have order dependent, order independent tests.
So that's a good episode.
But we talk about all sorts of stuff on Test and Code, including things like tips for working
from home.
That was on episode 127.
So check it out.
I think people are doing that more than they used to for some reason.
I'm not really sure why.
Working from home?
Yeah.
Yeah, definitely.
Yeah, no, that sounds great.
And Talk Python Training.
Yeah, we just released a brand new course, Move from Excel to Python and Pandas.
So if you have been trying to overdo all the stuff that you do around data with Excel
or people you work with are, we created a course written by Chris Moffitt from Practical
Business Python to basically go through all the main use cases of Excel and show how much
easier it is to do that in Jupyter and Pandas.
And I think it'll help a lot of people get their foot in the door in the Python world.
I think that's really cool.
I always wanted to learn Excel, but it's so much nicer with Python that I never got around
doing it.
Yeah, that's perfect.
That's the good side to be on, not the other side.
Yes.
So Brian, tell us about Markdown.
I really like Markdown.
I use it for a whole bunch of stuff.
And when I mean, I so much so that I just kind of assume everybody's using Markdown now.
But sometimes people have trouble getting up to speed or you want to share something.
Anyway, I came across, I was actually having a Twitter discussion with somebody and they
brought up this HackMD.io tool.
And HackMD, I've never heard of that.
So I went to check it out and I'm pretty impressed with it.
It's pretty cool.
It is a paid service, but there's a free option too.
So of course I'm on the free option.
But the idea is just sort of, I've got the similar, there's a lot of tools that do this.
So you've got a two panel system where you, on the left, you, you're Markdown and on the
right, it shows up and you can hide one or the other.
But the, what I really like is some of the stuff that I always forget, like how to do,
how to insert a picture or do a table of contents or put reference links in or, or footnotes.
Those things are just sort of in there with menu items.
So I don't have to remember what all those Markdown codes are.
They just added, apparently you can collaborate and have multiple people editing a document
with this.
So that's pretty cool.
There's some fancy extra things like a UML diagrams that you can add in.
And I'm not sure if you're exporting it, you'll have to try to figure out what sort of extra
tools you need to actually generate those.
But it's pretty fun.
The thing that I like that they just added recently, apparently is you can sync with GitHub.
So you can keep all your Markdown documents in GitHub and edit them with, with HackMD.
And that's pretty, pretty fun.
That's awesome.
The other thing I found was this thing called Markdown Guide.
And it is just a, just a really good, clean reference for Markdown.
So I'm going to, there's, I had, you know, a handful of different references that I was
using, but I think I'm going to switch to this one because there's tabs that have like a getting
started page that I can send people to.
And a couple of cheat sheets.
One of them was, is the most common things.
And I think it's pretty, pretty indicative of common things you'll use.
And then an extended syntax page with, and then a bunch of tools you can use.
So a couple of Markdown references for people.
Have you ever used Pandoc?
Oh yeah.
I love Pandoc.
Yes.
Since I recently started using it and I'm preparing my presentations now with Pandoc every
time.
And I love it.
It's just great, great tool.
I love about Pandoc is it's not just from Markdown to HTML, but you can convert to Media
Wiki or lots of, or I use it a lot of times to format my emails correctly in the Microsoft
Office.
I will write them in Markdown and then use Pandoc to generate the WordDoc version and then
copy and paste into an email.
I know it's backwards, lots of steps, but it works for me.
Yeah.
You know, it'd be nice to have just an email editor that just takes straight Markdown.
Wouldn't that be cool?
Yeah, that would be cool.
Yeah.
And I'd really like an extension to Microsoft Outlook that had Vim key bindings.
That would be awesome.
So the programmers are invading Outlook.
Yeah.
Some other cool stuff about Markdown or hack Markdown, hacked MD is it has a VS Code extension.
And like you said, the GitHub integration is cool.
It has a browser extension.
You could turn your notes into a slide deck.
You can turn it into like a research project into like what they call book mode.
Yeah.
It looks pretty interesting.
And the collaboration is definitely needed around Markdown these days.
Like there's not really a great collaborative place that I know of.
Although I'm sure listeners are going to send us five examples, which is awesome because they always do.
But for example, like we use paper.
You can do slides with this?
Yes.
You can export paper from Dropbox paper, paper.dropbox.com as Markdown.
But it's not full fidelity.
It's like 85% that you can edit what you get.
But it's still, it's better than nothing.
But yeah, this looks cool.
Nice.
You know what's not cool?
Python malware.
That's not a thing, is it?
Apparently it is now a thing.
So, Connor Fester, Fester, sorry, sent in this interesting article, which was done.
Who was this done by?
It was, one second.
Cyborg Security.
So, these guys wrote a pretty cool article about how Python malware is starting to show up.
Now, you may have heard articles or mentions of certain package management stores getting infected with malware.
Like we talked about some researchers putting some kind of malware onto PyPI.
JavaScript had this at NPM.
Ruby had this with their gem store.
So, that's not what I'm talking about here.
That's an issue, but that is not this.
This is about what are people doing to create the runtime environment, just the viruses basically, with Python.
So, traditionally, this has been like a C, C++ type of thing.
But there's some interesting parallels just to go through here.
I don't want to encourage anyone to do this, but I want to put it on people's radar to be aware that it could be being done, you know?
So, for example, one of the challenges, if you build a C++ app, you can just send a binary around and run it.
Not so easy with Python.
The standard library has to be there, or CPython has to be there.
But they talk about, well, people are using Py2exe and Py2app to package up their Python viruses and send them around.
Isn't that weird?
I mean, I guess people will do weird things.
Yeah.
So, there's an example of Python malware called C-Duke that was used against the Democratic National Committee back in 2015 and 16.
There's other tools that might be just generally useful to people, regardless of whether it's in this context or not.
Like, un-compile 6.
This is the successor to decompile, un-compile, and un-compile 2.
I don't know where 3, 4, 5 went.
But un-compile 6 is a native Python cross version, a Python version, I guess, decompiler and fragment decompiler.
So, what it'll let you do is it'll take Python bytecode and turn it back into source code.
So, instead of taking a Python file and turning it into PYC, you take a PYC and turn it into a Python file.
Interesting.
Yeah.
Some people have been shipping PYC files alone, right?
And just knowing that those can literally be turned back into source code in, like, one line of commands should be something on your radar, right?
Because it looks safe, but it's not that safe.
There's also a PY installer extractor.
So, if you were to ship a library or application as a PY installer thing, here you can turn it back into a bunch of source files you can open up and stuff.
And then they also talk about, if you're given an executable, how to understand whether or not it was built with PY installer or if it was built to PY2XE or any of those tools.
Like, given an arbitrary executable, is this a Python packaged up thing, yes or no?
That's cool.
These are great tools.
The article looks really interesting.
I never thought about malware in Python before.
Yeah, there's a lot of interesting details and concrete examples of, here's how they did this with this one thing or that.
And I think it's an interesting read.
Again, not trying to encourage people to do these things, but just raise awareness, like, what the role of Python is in this, you know, less popularized space, right?
People always want to hide what they're doing in this world.
There's another application for some of these.
Sometimes businesses have, they'll be afraid or, like, not want to pass around Python files because of the problems with, you know, knowing what the interpreter is or something.
So they use PY2XE or something to make an executable for a tool for the company.
And then somebody, and then that gets passed around and somebody loses the source or you don't know who has it or something.
So using some of these reverse engineering techniques to get some source back, that'd be kind of cool to use for that purpose as well.
I have an example of that.
So one time there was this program we built.
And this was early in my career.
I must have been, like, not so good about checking in stuff.
And somehow the thing that I was working on had a file that somehow didn't get added to, it was SVN at the time.
So I had pushed all the changes, but I forgot to add this one file.
And then my computer died.
And the problem was, it was like my hard drive died.
And so, like, there was some part of the application that in the middle of the app used this library.
And then there was the rest of the app that was kind of below that.
And so it was really hard to figure out how to rewrite just that middle piece because it was like a weird jigsaw puzzle that had to fit together.
So I just went and disassembled the application, found the few files I needed.
They were named weirdly, but I just renamed them in a way that worked.
And then off it was.
I checked it into Git and we were good to go.
Or it was SVN and we were good to go.
And you probably never forgot to check in your files again.
No, I'm very obsessive about it now.
That's right.
Yeah.
Yeah, absolutely.
Anyway, that's all I got for this one.
It's an interesting article, though.
It's well done with some nice examples.
Yeah.
So I'm going to go on with, do you call it adders?
I call it adders.
Brian, what do you call it?
Adders.
That's really like American English.
I would probably say adders, like often and not often.
Okay.
Anyway, so what is adders?
It's so I only, I think I saw it a few times before, but I never actually looked into the
package.
But now a few weeks back, I've started using it for the first time.
So what is adders?
It's a Python package that simplifies writing classes.
So it creates a lot of the dunder methods automatically.
Yeah, that's cool.
Yeah.
And when I first saw it, I thought we have data classes.
So why do we need adders?
And only then I realized that adders is much older than data classes.
So PEP 557 added data classes to Python 3.7.
And they do resemble adders in many ways.
So when I started reading a bit on the documentation page of adders, I found out that the PEP was actually
inspired by adders.
And it was the result of the wish of the community to have a simplified way to write classes without
having to deal with the problems that name tuples have.
And I think the main difference between adders and data classes is that data classes are strictly
less powerful, and that certain features were sacrificed for the sake of simplicity.
So it's very easy to use data classes.
They are part of, I think, 3.7.
With 3.7, they come automatically.
But if you have 3.6, you have to pip install them.
But you don't have to get a new package for them.
And it's very easy to use them, especially if you have classes with many attributes.
But with adders, you have quite a few additional features.
For example, you have validators that you can use when you have your initializer in the class
and you want to perform some kind of validation of the input arguments, like checking that they
are an integer or some other type or more fancy stuff.
Then you can do that very easily with adders.
And it's a very powerful library.
So I think I need a lot more weeks to really get into the details and all its possibilities.
Yeah, this is a good one.
There's a lot of subtleties around creating classes that can be a little bit annoying.
Like, wouldn't it be great if you could have it print out something other than just the name of the class
at some memory address?
Automatically, that would be nice.
If you create a dunder equal, dunder EQ method, well, you got to remember to create the not equals.
That is the opposite of that.
And oh, if you create equals, maybe you also have to implement hash as well.
Because all of a sudden, if two things are equal, you put them in the dictionary, but then they're not the same thing.
That's going to be all sorts of crazy.
It just starts to cascade.
You're like, wait a minute, doing this right, it's not so easy.
And so I think that's kind of the zen of the adders.
Yeah.
I found it a bit confusing in the beginning with the syntax, how it looks like if you declare an attribute,
like it's a decorator adders, but then for the attributes of the class, you have this, is it adders.s or something?
And I found that a bit confusing in the beginning, since data classes are, I think, more beautiful when you write them
and you don't need this extra bit.
But once you get used to the syntax, it's very nice and easy to use.
I have to agree.
I like the data class syntax better.
The dotness of the adders syntax is cute, but bugs me a little bit.
Like attrib, the attributes are attr.ib.
And it's not something I really enjoy, but it's not difficult either.
The main switch for me, I think, is now that data classes are here, I use data classes all the time.
But when I need a validator, the validation mechanism in adders is pretty darn cool.
So if you want data validation, adders is still a great thing to pull up.
I agree.
I really wish that validators were in, or at least maybe we could have an extra package that we could pip install or something that would make data classes have validators, hopefully.
I know there's other things that you can do to validate schemas and stuff like that.
Yeah, I feel like there's a little bit of a paradox of choice.
Like you look at all these things and you want all of the features that like kind of in this impossible combined way.
So adders is cool.
They've got things like you can say that these attributes can only be set as keyword arguments in the initializer and not as positional arguments.
And just KW only equals true, stuff like that, which is pretty cool.
And then you've got the Pydantic models, which have like built-in validation for all sorts of types, which is cool.
You've got data classes.
Those can be frozen, which is kind of nice.
There's a lot of stuff going around here, and I feel like I'm underutilizing all of it.
Well, grab what you need.
It's good.
Yeah.
Throw some tests around it and switch later.
For me, it's sometimes just easy to forget what's out there since there are so many nice packages.
And I sometimes hear like I listen to a podcast and then I think, oh, that package sounds cool, but I don't have an application for it right away.
So I forget about it again.
And then in some context, I hear about it again.
And I think, oh, yes, you always wanted to try that.
But I think at least with adders now, like I will use it again quite a few times.
Yeah, I have that same problem.
I get excited about all these things, but I don't have a chance to use them.
And then I forget.
Then I'll rediscover.
I'm like, oh, yes, that's why I thought it was cool in the first time.
You should create a Harry Potter style project yourself for trying out all these things.
That's right.
Like awesome Harry Python, Harry Potter Python.
I'm going to work on the naming.
I like Harry Python.
Well, it might invoke images that are not exactly the same what you're thinking.
Oh, yeah.
Okay.
Never mind.
Yeah.
All right.
Well, you guys got anything extra?
I don't.
Brian?
No extras?
No.
No?
How about you?
Anna Lena, maybe take a moment and just tell folks like what you're up to.
We didn't give you a really introduction on the kind of work and stuff you're doing.
Yes.
So I think the first time Michael and I talked on Talk Python To Me, I was still an AI resident
at Microsoft Research in Cambridge.
So I was doing a lot of machine learning research.
So working in the middle between a full researcher and a full software engineer.
And now I'm a machine learning engineer here in Germany in a company called InnoVex, where
I do like I apply machine learning to projects, proper real world problems, which is also very
interesting.
And I do all kinds of stuff now, data engineering.
So yeah, I'm always learning new things every day, which is really nice.
Yeah, that's very cool.
All right.
So I've got a couple of things really quick to share.
I was on a cool podcast TV-like show called TechNado, which was a cool experience.
It's a little bit like Python Bytes, but for the IT space.
So that was a lot of fun to be on there.
And on YouTube, you can check it out.
And we played the game Python, Python, Python, where we would get partial words out of a headline.
And we'd have to decide, is it Python the snake, Monty Python, or Python the programming
language that the article is about?
That was pretty fun.
So you could check that out over there if you're interested.
Sorry.
So did you win?
I completely got crushed.
I think I got last because I wanted everything to be about Monty Python.
And they're like, no, that's about a snake.
I'm like, oh, come on.
That would have been so funny if that was about Monty Python.
But no.
Yeah.
I let my hopes and dreams get ahead of me.
Maybe next time.
Exactly.
I'll come back for the championship later.
Brian, what do you think about this joke?
I haven't looked at it.
Oh, perfect.
Then you got to open it up.
Anna Lena is, well, this one is, as per usual for us, a visual joke in an audio format.
But I think it's going to work great.
So this one is called the only valid measurement of code quality.
And I know, Brian, you're very passionate about high quality code and testing and stuff like that.
Have you seen this metric built into any of the software you used?
Well, you can't.
Maybe with some voice recognition and some AI.
Anna Lena could put something together for us, like starting the code review now.
Yeah.
It looks so funny.
I love that.
Yeah.
So this is the only valid measurement of code quality is WTFs per minute.
I'll try to keep this without the explicit tag, but WTF.
So there's a comparison here.
On one hand, we've got the good code review, which is still, it's like a door that's closed.
And you can just see like statements of what people's going on.
It's going on the side.
You hear this, WTF, WTF.
What is this?
That's the good code.
The bad code is just full of them.
It's like WTF.
What the WTF is this?
A dude, WTF.
WTF.
I think this really captures code review pretty well.
It does.
Anyway, the only valid of measurement of code quality, WTFs per minute.
WTFs per minute.
Definitely.
All right.
Well, that wraps it up for this week.
All right.
Thanks, Brian.
Thanks, Elena, for being here.
Thanks.
It was a lot of fun.
Yeah.
You bet.
Bye-bye.
Bye.
Thank you for listening to Python Bytes.
Follow the show on Twitter at Python Bytes.
That's Python Bytes, as in B-Y-T-E-S.
And get the full show notes at Pythonbytes.fm.
If you have a news item you want featured, just visit Pythonbytes.fm and send it our way.
We're always on the lookout for sharing something cool.
This is Brian Okken, and on behalf of myself and Michael Kennedy, thank you for listening
and sharing this podcast with your friends and colleagues.