What does it mean to be a leader in the Python community?
Does it mean you contribute to open source projects?
You speak at conferences?
You start the largest user group?
You write a book?
You be a core contributor to the language?
The answer is yes.
And that's why Jessica McKellar won the Frank Wilson Award
for contributions to the Python community.
She is the guest on this episode of Talk Python to Me.
It's number 30, recorded Thursday, September 24th, 2015.
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 @mkennedy.
Keep up with the show and listen to past episodes at talkpython.fm
and follow the show on Twitter via at Talk Python.
This episode is brought to you by Hired and OptBeat.
Thank them for supporting the show on Twitter,
where they're at hired underscore HQ and at OptBeat.
Hey, everyone.
I don't have any news this week, so let's get right to the show.
Let me introduce Jessica.
Jessica McKellar is a startup founder, software engineer,
and open source developer living in San Francisco, California.
She works at Dropbox and enjoys the internet, networking,
low-level systems engineering, relational databases,
tinkering on electronics projects,
and contributing to and helping others contribute to open source software.
Her motto is, be the change you want to see in the world.
And she has been a director for the Python Software Foundation.
Jessica, welcome to the show.
Thank you for having me.
Yeah, I'm really excited to have you on the show.
You've been a long-time sort of Python hero to me.
I've seen some of your talks that you've done at conferences and keynotes,
and they were really inspiring.
So I'm excited to talk to you.
I really appreciate that.
You're welcome.
I'm excited to talk to you about this.
Thank you.
So before we get into all the awesome stuff you're doing at the outer edge of the Python world,
let's maybe take a step back and you could tell me a little bit about how you got into programming
and how you got into Python.
What's your story?
Yeah, absolutely.
So I was not one of those people who was programming since birth.
I was a big science nerd in high school, and I actually declared chemistry as my first major.
And I actually have a chemistry degree.
That's my first bachelor's degree.
But I had a bunch of friends.
I went to MIT, and I had a bunch of friends who were pursuing computer science degrees while I was busy pursuing my chemistry degree.
And, you know, I would sort of look at them out of the corner of my eye, and I would look at what they were learning.
And it seemed like this, they were really learning this toolkit.
Like they were learning a toolkit full of tools for solving many different types of problems in the world.
And that seemed very attractive to me, and also, frankly, very different from what I was getting with my chemistry degree.
And I wanted to try out what learning that toolkit felt like.
And I ended up taking some computer science classes.
I was pretty immediately hooked and ended up getting a computer science degree and then also a CS master's.
That's cool.
What was your first programming class language?
Well, yeah.
So I was at MIT right when they were in the middle of this big transition from Scheme, which is a dialect of Lisp, to Python.
So my first couple of classes were in Scheme.
And then sort of the back half, many of them were in Python.
Oh, that's nice.
So my first computer science class was also in Scheme.
And I do wish it was in Python.
You know, no disrespect at all, but Python is just so much better, in my opinion.
I mean, Scheme is a very interesting learning language.
But I think that, so there was a very conservative, so the reason why there were, well, one of the reasons for this transition was, like, some pretty serious declining enrollment numbers in the computer science program.
So it was part of this big revamp to make the program accessible, A, to, like, a diverse set of backgrounds.
You know, I think that there had been a sense previously that you really sort of needed to have already been programming, you know, in high school for you to really seriously consider doing it at university.
And they wanted to open up the door towards a more diverse set of backgrounds and to make it also a more interdisciplinary curriculum.
And I think enrollment has been, you know, sort of skyrocketing since that change, which is exciting for me.
That's really great.
I don't know why, but it's definitely, I definitely get the sense that Python is more welcoming to people from different backgrounds.
And it just seems to bring greater diversity.
I do conference speaking.
I do training in a variety of languages.
And when I do Python, it feels like the people in the audience are much more representative of the general population.
I don't know why.
Maybe you have better insight than I do.
But it's a good thing for whatever reason that's true, you know?
Yeah, so certainly, A, the Python community has made very concerted efforts internationally to be a very welcoming community, in particular to first-time programmers.
And then also, I mean, the language, sort of this batteries-included philosophy means that if you're just learning how to program and maybe you're not sure if this is for you,
I mean, you know, the fact that after just a couple of hours of learning the language basics and then a couple of lines of code,
you can do something that is actually pretty exciting, it really hooks people.
Yeah, I think you're right.
I mean, programming is so fun and so interesting.
But when you're new, it's not fun and interesting.
There's all these little terrible details like, how do I declare a variable?
And why does a semicolon go there?
And why do I need to know how to declare a class to declare a function just to, like, print?
You know, there's, like, all these stuff you've got to make, sort of, make your way through believing on the other side and there will be something interesting and cool you can do.
But it takes a long time with a lot of languages.
And like you said, like, Python, you get to that gratification a lot quicker.
Yeah.
So what was it like doing computer science at MIT?
I mean, that's one of those schools that's definitely up there on a pedestal.
And I bet it's a pretty interesting environment.
Can you tell me what that was like?
Yeah.
Well, the pedestalization is funny because, honestly, the school is very similar to lots of other, you know, STEM-focused universities, you know, in the country and around the world.
And the thing that you really benefit from at MIT is the network.
But, yeah, you know, I received a nice, rigorous computer science education.
I learned a lot.
One of my fondest memories, although maybe it wasn't fond at the time.
So I had this, like, fairly compressed computer science education there because I spent the first two years getting a chemistry degree and then the last two years getting a CS degree.
And so I ended up sort of like the time from first computer science class to taking grad classes was rather condensed.
And I have this really distinct and fond memory of taking, there's this sort of famous operating systems class, 6828.
And, like, that was the class where I really learned how to be a systematic debugger.
Because, I mean, when you're building an operating system from scratch, and this wasn't in Python, but, you know, debugging is universal.
It's all programming languages.
But when you can't trust, like, your page table implementation, you can't, like, trust anything about your kernel, you really learn how to be systematic about these things.
And I look back on that very fondly.
It's, like, sort of very rigorous.
It was very hard for me at the time, but I learned a ton from it.
I can imagine that, you know, if you mess up the memory implementation or something, like, that's pretty critical.
It's not just, like, you're off a little bit, right?
Something goes really wrong.
So, yeah, that's really, I'm sure that was interesting.
Was that in C?
Yeah, and a lot of assembly.
Yeah, I'm sure it was fun.
Like you said, I'm sure the most important part is just being around a bunch of smart people, super excited about programming, just kind of immersing yourself in that world.
Yeah, totally.
The reason I reached out recently to you is you got a big honor in the Python community, and you won this thing called the Frank Wilson Award.
Yeah.
Yeah, congratulations on that.
Oh, thank you.
You want to talk about that a bit?
Maybe tell us all what it is first.
Sure.
It's mostly a recognition of a sort of sustained involvement and investment in the community in particular.
And that is pretty much my cup of tea here.
So I do, you know, I have contributed to the language.
I'm a maintainer for various open source Python libraries.
But a lot of what I'm invested in is the community side.
I guess some of the things that I've done over the years have included being an organizer for the Boston Python user group, which became the largest user group in the world.
How big is that?
Several thousand people.
That's pretty awesome.
You can't have everybody attend, right?
No, you can't.
But it's this really wonderful both sort of online and offline community.
And there are a bunch of people who deserve a ton of credit for this.
It's certainly not a one-person effort.
A big part of the growth was around us making a very concerted investment in attracting and retaining sort of diverse backgrounds in the community in Boston.
So Boston, it's a college town.
You have a ton of students.
There are a bunch of fields adjacent to just sort of pure software engineering that are very well represented.
It's a big biotech community.
The sciences are very well represented there.
Yeah, you've got all that high-tech stuff.
What is that?
Route 128 or something sort of on the ring out there.
There's a lot of really cool companies.
Yes.
So you have this opportunity to have a bunch of sort of really interdisciplinary, wonderful interdisciplinary discussions,
and then also to be very concerted about attracting diversity amongst other demographics.
So we had a very concerted push where it was getting more women into the community, for example, to get more students into the community.
And that was a big part of our growth.
And that model, sort of the model that we built out was starting with sort of an introductory series of programming workshops
and building that into a pipeline of sort of project nights where you come and you can get mentorship on whatever projects you're working on to intermediate Python workshops.
And then sort of being well-situated at that point to be just a general, fluent member of the community.
And so this sort of pipeline model has been emulated in a bunch of other cities and has proven pretty successful.
Sure.
I currently am not in Portland, Oregon, but I live in Portland, Oregon.
The Python user group there seems to be modeled very much like that.
They've got like a peer mentoring night.
And then once a month they've got like, you know, more formal speaking.
And then they've got a lot of different levels.
And I think that that's really pretty key to making it successful, like you say.
Yeah.
I've actually been to the Portland user group on a couple of occasions.
Oh, nice.
Yeah.
Very cool.
You know, it seems to me like if you're just a student or somebody, if you were to go to, I don't know, user group with some famous speaker talking about the nuanced bits of some advanced piece of the language or some library or technology, right?
That's sort of inaccessible to you.
But I think having this pipeline that slowly brings people more in is probably good.
Yeah.
And you want the super advanced stuff too, right?
I definitely want to be, you know, have an opportunity to talk with experts on advanced topics.
But having, you know, sort of having the beginner, the intermediate, and the advanced topics covering your attendee base is definitely important.
Yeah.
That's super cool.
Okay.
So Python user group in Boston, we're going to name some other things.
I derailed you.
I know you have a bunch more.
I spent a lot of time speaking.
I'm sorry.
I mean, I was a director for the Python Software Foundation for a couple of years, a co-chair for the Outreach and Education Committee, which is sort of specifically dedicated to bringing Python into schools and learning communities and attracting diverse audiences.
So what level were you focused at?
Was that university?
Was that high school?
In general?
It's really everything.
And actually, a lot of it is sort of learning opportunities and learning communities outside of the formal education system.
So supporting a lot of these, you know, workshops for sort of a diversity-focused workshops or perhaps like an after-school program for kids where they might not otherwise have a formal opportunity to learn how to program.
It was really the full spectrum.
Okay.
Yeah, that's cool.
A lot of international investments, which is really cool.
So we've definitely given grants to people on probably every continent except Antarctica.
Yeah, which is very cool.
Yeah, there's not a lot.
There's probably only scientists on Antarctica, aren't there?
We'll get them, though.
We'll get them.
They probably brought Python with them, actually, keeping it warm and somewhat.
One of the things that I really liked that you did was a talk, I think it was in New Zealand at KiwiPyCon.
Is that right?
I did give one of those, yeah.
Yeah, yeah.
And you said you titled it something like Choose Your Own Python Adventure.
Do you remember that talk?
I do.
Yeah.
Yeah, that was really, really good.
And let me see if I can summarize it.
We could talk about it a little bit.
So, you know, you kind of said, like, look, we want development and programming in Python to be wonderful and delightful.
And there's a lot of positive stuff happening, like you talked about, the adoption growth and things like that.
But you wanted to make sure that it keeps growing.
And there was maybe some challenges that you said, look, we need to address these things.
The number one issue that you brought up, which I thought was pretty interesting and resonated with sort of my experience as well, was Python on Windows.
Yeah.
So what's the problem with Python on Windows, even though it is getting better?
It is definitely getting better.
And the talk was a couple of years ago.
And there have been some, you know, there's been a lot of investment since then.
But this stems from, I think, an issue that is common in many communities and, you know, also, like, many startups.
Like, there are many contexts in which this is true, which is just that the developers are using a different environment than the preponderance of the users.
So the vast majority of people who are programming in Python are programming on Windows.
And very few of the people contributing to, like, the CPython code base use Windows.
And that creates a disconnect around, you know, you need to be, you need to have a good understanding of what the experience is.
In particular, sort of the early experience, the onboarding experience, the installation experience for the vast majority of your users.
And, like, take that empathy back and invest it in the language.
And so a lot of it stems from that.
Just not having a lot of people regularly experiencing what it's like to be a beginner in the language on Windows.
And so I think the key challenge is, A, like, attracting folks who do have that background and welcoming them into the development community.
And then also just being more conscientious about and proactive about addressing that very large segment of our user base.
And some of this is, so I come from sort of startup land.
I've been through a series of startups and acquisitions.
And I tend to think about everything in life, including the Python community, in terms of, like, a pretty standard, like, user retention funnel analysis.
And if you think about it, it's like, okay, Python wants to be a language that hopefully, like, many, many people are still using for a diverse set of, you know, in many diverse areas for many years to come.
And to do that, we need to be getting new developers and retaining them.
And it's sort of like, at your big top of the funnel is all of these new users, most of which are on Windows.
And then, you know, you get those folks to use the language, maybe in a basic way, maybe in school.
You want to retain them through them using it professionally.
And then you want to convert some of those folks, hopefully, into becoming active contributors back to the language and community.
And the thing that we can, it's easy to, it's easy to focus on things that impact a smaller set of the funnel, if you're not really conscientious of what the broader funnel looks like.
Because, like, there's a disproportionate impact for focusing on the top of the funnel, the widest part of the funnel.
So, like, investments that you make that make the first five minutes of using Python better are going to have an impact on, like, hundreds of thousands of people.
And then fixing, like, a particular bug that affects, like, some specific bug and some specific library potentially is still very important, but may impact a smaller number of people.
Which is not to say that we shouldn't do both, but we should be conscientious as a community about ensuring that we're investing enough in the top of the funnel.
Yeah, it's really interesting to view the ecosystem and lifecycle of a language through growth hacking terms.
But that's really cool.
Yeah.
But it makes perfect sense.
I can't help it.
No, of course.
And it makes perfect sense.
You're right.
There is a disconnect.
I mean, if you take the time and you make, let's just focus on Windows, but it could be basically getting started anywhere.
If you make getting started with Python on Windows better, you're not going to go to the conference necessarily and go, oh, that's the guy that made that better.
Because everybody there, like, doesn't hit that problem.
They're way past it.
Right?
But if you make, you know, coroutines just slightly more efficient, they might cheer when they see you or something, you know?
But like you said, the people that are coming in, they feel that pain.
And I've done a lot of training where, you know, there's 30 Dell and HP laptop screens or, you know, backs facing me.
And there's a lot of, well, it says Python is not found when I type Python.
It's like, okay, well, did you restart the command line, the command prompt after you installed it?
There's just all that friction, right?
Yeah.
And to be clear, I'm definitely not knocking.
Folks should do what they're passionate about.
And if the thing that people are passionate about is, in fact, like optimizing how coroutines work, that's fantastic.
It is sort of collectively as a community.
We should value and we should incentivize and recognize the efforts that do impact this big part of the funnel that has historically been underserved.
Yeah.
So, you know, I just, I totally agree.
And I guess I should recommend that people watch that video of yours, even though it is a few years ago.
I'll put it in the show notes because I think it is, like you said, it's a place to have where there's sort of low-hanging fruit that can have really big impact on people.
So, what do you think about things like IDEs and stuff like that that maybe do a little more hand-holding for getting people started?
This episode is brought to you by Hired.
Hired is a two-sided, curated marketplace that connects the world's knowledge workers to the best opportunities.
Each offer you receive has salary and equity presented right up front and you can view the offers to accept or reject them before you even talk to the company.
Typically, candidates receive five or more offers in just the first week and there are no obligations, ever.
Sounds pretty awesome, doesn't it?
Well, did I mention there's a signing bonus?
Everyone who accepts a job from Hired gets a $2,000 signing bonus.
And as Talk Python listeners, it gets way sweeter.
Use the link Hired.com slash Talk Python to me and Hired will double the signing bonus to $4,000.
Opportunities knocking.
Visit Hired.com slash Talk Python to me and answer the call.
I mean, in general, I think that that's great for people where it works and for environments where it works.
And it's certainly very common in schools.
I have a...
I don't actually know if this is a majority opinion or a minority opinion, but I have a strong opinion on this, which is that I think that...
So in general, with Python, it's like there's one...
Explicitness is better than implicitness.
And there's hopefully one obvious and good and correct way to do things.
One of the places where we don't sort of adhere to that philosophy is in how we recommend that people get started.
And I actually think that there's an opportunity for us to be more opinionated with new learners about how to set up their environment in a way that will sort of maximize their chance of being successful new learners of the language.
Like, if you currently...
Like, if you go to Python.org right now and you, like, try to follow the instructions for how to get your development environment set up, it's like there are many forking recommendations.
And we try to be this sort of neutral place.
And I understand why there's a temptation to present yourself as, like, neutral and providing all the options.
But the problem is that a new learner doesn't know enough to know what the...
Like, to determine what the right answer is.
And so, like, being opinionated about potentially an IDE...
I mean, maybe the answer is an IDE.
Maybe it's not.
And just, like, a super vanilla, like, sort of terminal-based education is okay.
But I think we should be considering having a more opinionated stance on what development environment we recommend for new learners.
Yeah, I think that makes a lot of sense.
I mean, you don't want to alienate some significant portion of the population saying, use EMAX, don't use EMAX, use PyCharm, don't use PyCharm, whatever, right?
But when you're new, recommendations, if you say, well, here's four good choices, and then, like you say, it's just...
It's tough.
So, do this, get started, then make your choices down the road or something.
Yeah, I'm not really sure what the choice is or the right choice is either, but...
But I think it's a conversation worth having.
Yeah, I definitely think it's a conversation worth having.
So, one of the things you did, as you said, for a while, you were the PSF director.
So, what does the director do, and what's that like?
I bet that's a crazy role to have.
And so, and just to clarify, there are several directors that work together, sort of as a committee.
And so, this is the...
So, the Python Software Foundation is a 501c3 nonprofit.
And it's sort of the stewarding arm for the community.
And it also, as this nonprofit, has the ability to collect and disperse funds towards investments in the community.
So, a big part of what we do is to sort of get funding and then reinvest it in the community in a smart way.
We also do things like underwrite PyCon.
So, those are the two big things that we do.
And there's also sort of an aspect with this investment of...
And so, like, what are you investing in?
You want to invest in accelerating development of the language.
Invest in development of the popular libraries and maybe new libraries.
New initiatives.
Not new anymore, but, you know, back in the day, we gave a big grant to PyPy, for example.
So, you know, potentially new initiatives that would accelerate the language or broaden the set of domains in which Python is an excellent language to use.
And then also investing in, like, local community initiatives, which includes everything from local workshops to regional Python conferences.
Okay.
Yeah, that's really cool.
Does trying to promote Python 3 fall under that banner?
Yes.
Yes, I would say yes.
We tend to...
I mean, so, just to be clear, the PSF doesn't try to dictate sort of details of the language.
But definitely, Python 3 is important, A, because it's the future of Python, and B, because it's important that as a community, we communicate a clear direction externally.
Like, it can be very confusing, again, potentially to new learners and maybe companies that are thinking about,
what languages they want to use for a new software stack.
Like, they want to be confident that the Python community knows what it's doing and has a clear sort of future direction.
So, to the extent that that is a part of sort of the outward communication mission of the PSF, yeah, that's definitely important to us.
And we also, like, we have funded...
We've given away grants to port, like, major libraries to Python 3 and things like that.
Right, sure.
I had Chris McDonough on the show, and he's talked about, you know, you guys, I don't know if you were involved directly, but, you know, PSF sort of nudged him to get Pyramid to run on Python 3, where he was...
Yeah, totally.
You know, not exactly.
Rushing in to get it done, because he was actually working.
Things like that.
Right now, professionally, you're working at Dropbox, right?
Out in San Francisco?
Mm-hmm.
That must be a pretty awesome place to be.
Yeah, it's been a lot of fun.
So, as I said earlier, or as I alluded to earlier, I come from sort of a series of startups and acquisitions, and the latest startup and acquisition have landed me at Dropbox.
And I had been in Boston for 10 years coming out of university, and sort of the inexorable pull of Silicon Valley finally got a hold of us.
We all moved out west.
And, yeah, so I'm a director of engineering at Dropbox.
I run the engineering group that is responsible for all of the sort of platform software.
So, this includes the desktop clients, our mobile apps, and web as a platform.
Incidentally, Guido is a part of this group.
Yeah, that's awesome.
So, what's it like to work with him?
Yeah, I mean, he's...
Well, if you've ever...
For anybody who lurks on the Python dev mailing lists, it's about like that, but at work.
But, you know, Guido has, you know, he has such expertise with...
Like, when you think about, like, what developing a language...
Like, what skills developing a language entails, those are skills that are incredibly useful when architecting complex systems, like thinking about abstractions that need to be very long-lived, perhaps with API design, for example.
So, you know, he's a very...
He brings a lot of excellent expertise to the table at Dropbox.
I'm sure.
We also tend to get...
We get into an occasional Python-related flame war, but that's par for the course.
Yeah, I'm sure.
Yeah, I mean, one of the really valuable skills that I can think of is, like, simplicity.
Yeah.
People see something that is simple, and they think, well, that must have been easy to build, because it's simple.
Right.
You know, that's hard with languages.
That's hard with complex software.
But it seems like he's at least nailed it for Python, the language.
I haven't seen the Dropbox codes.
I can't say for sure, but I bet that skill transfers over.
Yeah, definitely.
Well, and, you know, so the Dropbox desktop client is written in Python.
It's one of, if not the largest, you know, pieces of desktop client software that is out in the world.
You know, Dropbox has 400 million users.
There aren't that many pieces of desktop software that aren't sort of bundled with an operating system distribution that have that level of user base.
So that's all in Python.
It's not in Python 3, although we periodically...
You know, it's a very large historical code base, but we do periodically revisit, if we're going to...
Make the jump to Python 3.
That's super interesting.
I did know that, and I thought it was great.
So I'm glad you brought it up.
Can you talk a little bit about, like, just, you know, the internals, the libraries you're using, how you build it, how you distribute it?
Like, what's the story with that?
I don't actually think that I'm allowed to.
Sorry.
Okay.
I don't want you to do anything you can't do.
But, you know, a lot of people build, you know, little utility scripts, or there's a ton of web applications and data science apps.
But the sort of, here's the thing with the UI that I can ship in Python is really interesting.
Yeah.
Well, Python has taken us a long way.
I mean, Dropbox has been around since 2007.
And, you know, Python gives you this cross-platform desktop client software that you can develop against pretty rapidly.
You know, we've certainly benefited, I think, quite a bit from making this early language choice.
I mean, there are pros and cons.
Like, there are definitely alternative models for desktop client development, but it's definitely served us pretty well.
Yeah.
It seems like it has served you guys really well.
And when I think of companies that are, like, making major use of Python, well, Dropbox, maybe along with Google and a few others, is right there at the top.
Can you give us kind of a sense of, like, all the things you're doing with Python there?
Or you and other people, obviously.
In addition to our desktop client being written in Python, the majority of our server-side code is in Python as well.
So we pretty much use it for everything.
There's a little bit of Go.
I mean, our mobile apps are written in the languages you would expect, but Python is definitely the majority language.
So do you want to talk a little bit about some of the open source projects you work on?
I saw your core contributor to Twisted, for example.
Yeah.
So, and I have to admit that sort of there's an ebb and flow to how much of my time is spent on sort of the community and the people parts versus the technical parts.
Yeah, so I, the first open source project that I ever contributed to was Twisted.
It came out of an internship that I was doing at VMware.
I was using Twisted.
So Twisted is an, I mean, maybe everybody knows it, but Twisted is an asynchronous networking library written in Python.
And I was using some of the primitives and some of the documentation was a little unclear to me.
And I thought, oh, hey, this would be a great opportunity to, like, try my hand at making my first ever open source contribution.
So I created a little tiny diff for, like, a little bit of a documentation change.
And, like, very nervously, I, like, quadruple checked all of the instructions, like, contribution instructions.
And then, like, you know, opened up a ticket and, like, quadruple checked all of the ticket fields.
And then, like, sort of sweat a little bit with my hand hovering over the submit button.
Like, finally press submit.
And, of course, everyone was super nice.
So Glyph, who was the creator of Twisted, who incidentally, this is what San Francisco is like, incidentally, he lives in my apartment complex now.
Oh, wow.
What a small world, huh?
Right.
So Glyph, who's the creator of Twisted, and a bunch of other folks were super friendly, very willing to handhold me through the process.
You know, I ended up making some more small documentation contributions.
Like, ended up sort of getting pretty involved in the community.
Ended up becoming a core committer.
I ended up writing a book about it with O'Reilly.
So that first little, like, nervous documentation contribution ended up being a very important...
A, it was very important for me because that was such a positive first experience with contributing to an open source project.
Like, I want everyone to have that positive first experience.
It was very important for me.
And hopefully, also, it's been a good investment for Twisted, given that I've managed to stick around.
So that's one of them.
And then OpenHatch is...
Well, it's both a website and a nonprofit dedicated to lowering the barriers to entry for open source contribution.
And I've been fairly involved with them as well.
And then I just, like, miscellaneous patches here and there to various other projects.
Yeah.
Core Python.
Yeah, that's really cool.
I think that's one of the nice things about the Python community.
They seem pretty welcoming to new folks.
Whereas, you know, if that was like a C++ project, they might have, I don't know, not been as welcoming, right?
It could have been, oh, you did this wrong or whatever.
Well, I hope that all language communities and all sort of libraries are recognizing how important it is to provide a good initial experience for potential contributors.
Because it's so important for you.
Like, if you want your language or your library to continue to evolve and be popular, like, you need to be ingesting new contributors who can pick up some of the development.
So hopefully people are learning that.
That's for sure.
And I think things like Git and GitHub and Bitbucket are really sort of opening the door to make this feel, you know, less threatening as well, right?
You're not cruising around SourceForge trying to use some old clunky tool to get a check-in to go in or something.
Yeah, definitely.
Do you have a favorite open source project?
Whether you contribute to it or not.
Geez.
Or how about one, you know, one or two of your favorites?
You don't necessarily have to exclude, be exclusive.
I mean, that's, I feel like I can answer this question on a number of different levels.
So I have used Django at this point through several startups.
And I think that Django was a very important thing to have flourished in the Python community.
Like for, you know, it really was a big part of opening up Python being a serious language for many types of website developments.
So A, on a personal level, having used it quite a bit.
And then B, because I think it's had like a very material positive impact on the community.
That's probably a choice.
Yeah, I would say Django definitely has had a really big impact.
So that's a good one.
Yeah.
You know, Python itself.
But that's kind of assumed, right?
Sure.
Yeah, yeah.
And having contributed to CPython, my challenge for us would be that I think we haven't quite cracked the nut on getting really good, sustained new developers to core Python.
And that's a thing that we should, that's nothing we do need to crack.
Yeah, absolutely.
And Guido actually made a, you know, that a key part of his keynote at PyCon, right?
Yeah.
So it's tough, though.
You know, it's a very different world than Python.
And people are drawn to Python, the language.
And then you go look at CPython, and it's, to some degree, a totally different type of programming and skill set and so on.
Yeah.
One, it's a very mature project.
Just in terms of it's been around for a while.
It, you know, it's, it is the language.
So sort of the commitment to quality needs to be very high.
Like, we can't sort of regress, regress functionality for the hundreds of thousands of people who develop against it.
And then, you know, millions of people who end up sort of using the end software that's developed.
So it's like, it's very mature.
There's like a fair amount of process.
And that's all important and necessary.
But figuring out how to balance that, again, making it an accessible environment for new contributors.
Yeah, sure.
I mean, if you're writing software used by that many people, you've got to deal with every edge case.
Be just super careful.
And then on top of that, it's C, which means it's a little harder to do.
This episode is brought to you by OpBeat.
OpBeat is application monitoring for developers.
It's performance monitoring, error logging, release tracking, and workflow in one simple product.
OpBeat is integrated with your code base and makes monitoring and debugging of your production apps faster.
And your code better.
OpBeat is free for an unlimited number of users.
And until recently, it's only been available for Django developers.
But I'm happy to tell you they are launching Flask support.
Visit opbeat.com slash Flask to be amongst the first to join the Flask private beta.
I think it's important that people that work in Python kind of at least have a conceptual understanding of what's happening down in the CPython layer.
There's a guy named Philip Guau who did a really cool thing.
He took his graduate class that studied the CPython code base and then took that and put it on YouTube.
So there's this thing called, he called it the CPython 10-hour code walk or something like that.
And then I had him on show 22 to talk more about it.
So I totally recommend people check that out if they want to know more about CPython.
Yeah, totally.
And I also, this is such a who's you.
So I know Philip.
We were actually, well, I actually know him through a couple of channels.
But then we were at this, how would you describe it?
So there's a community that used to be called Hacker School that is now called Recurse Center.
Which is, it's sort of like an artist in residence program for programmers.
It's sort of, it's a fairly unstructured environment where you go and you sort of invest in your programming skills for several months.
And I have sort of been a visiting speaker at that program, as has Philip.
So, and we've actually crossed paths physically there as well as on the internet.
So small world as per usual.
It definitely is.
Where was, if that was a thing in person, where was that?
Oh, so Hacker School and now Recurse Center is in New York.
So, you know, I brought up your video, the Choose Your Own Python Adventure.
Are there other videos that are out on YouTube or other places we can find that people should check out if they're interested in more?
Like, of me?
Yeah, I mean, of like talks that you've given that you think, hey, people should check this out.
Or I guess other ones as well.
I mean, so many of the talks that I've given at various Python conferences are online.
And you can find them on PyVideo.
But maybe one of the most gratifying things for me is, so for a couple of years at PyCon US, I did an intro to Python tutorial.
So, you know, it's a three-hour tutorial for absolute beginners as soon as no prior programming experience.
Like, we do, we walk everyone through everything, like, from the installation and environment setup on through the first couple of hours in the language.
And that's, I've read something like 200,000 people have watched those videos, which is, like, that's a lot of people.
Like, that's incredibly gratifying to me that there are that many people who were, like, wanted to learn Python and then took the time to have that first experience watching, you know, like, sort of watching that PyCon tutorial.
So that's the one that I maybe was proud of.
Okay, that's really cool.
I mean, just the thought that you've, you know, influenced that many people down that path has got to be gratifying.
Yeah.
And I, you know, I really, like, the beginners are where my heart is.
And I think some of that comes from being, I mean, comparatively, sort of, comparatively, quote, unquote, late to learning how to program.
So not starting until university.
And then being, you know, honestly, being surrounded at school by people who had been doing it for a lot longer and really sort of feeling like I was catching up for a long time.
I think that built up a lot of empathy that has stayed with me through the years around, like, what it's like to be a new programmer, what it's like when everything maybe feels foreign and you maybe are surrounded by people who it feels like have been doing this for longer than you.
And it's really wanting to provide an excellent experience for those people.
That's really interesting.
I hadn't really thought of it that way before.
But I didn't get into programming until, like, a ways into college.
And, you know, super deep into it until kind of my senior year almost in college.
And I think it does help you teach people who are new because the sort of pain of learning is fresh.
Like, if you learn it when you're 10 years old, it's like learning language.
Like, I don't remember how I learned English.
I just know English.
Right?
So I feel totally unqualified to teach English.
But I do remember learning programming and all the mistakes I made and so on.
So that's quite an insight.
What else would you like to talk about while you're on the show?
I think there's maybe a call to action here.
Yeah, absolutely.
Listeners.
Well, and I'm not sure, you know, they're probably listeners from many, many backgrounds.
But I would encourage everyone to think about sort of what they get out of Python, the language and community.
And to consider, if you're not already, giving back in at least one way, either technically or in a more community-oriented way.
And if that is, like, taking the plunge and making your first open source contribution, if that's volunteering with your user group at an upcoming workshop, you know, whatever it might look like.
I would definitely, you know, one of the important things about Python is that it is almost entirely community-driven.
There is not a giant company or consortium behind the language and community.
Most of the conferences are volunteer-driven.
And so it really is, like, sort of the success of the community and requires us all working together to drive the language and community forward.
So I'd encourage everyone sort of to take that opportunity seriously and, you know, pick at least one thing that you'd want to get, that you'd want to contribute by the end of the year and go ahead and do it.
Yeah, that's a great call to action.
And I definitely second that.
I'll throw a few more ideas out there in that vein.
Hour of Code is coming up in December.
You know, volunteer at your local school.
It's surprisingly easy.
There's actually a lot of Python sort of online Hour of Code-focused things.
So, you know, you could maybe help push a kid in a direction that they start down the programming path where they might not have otherwise.
Last year, I volunteered at my daughter's elementary school.
And we did programming for first, second, third, fourth, and fifth grade.
We did a whole bunch of little classes throughout the week.
And then three or four months later, I saw a kid who was in third grade walking to school with a JavaScript book.
And I talked to his dad.
And he said, yeah, that's because he did that Hour of Code thing with you.
How awesome is that?
Oh, that's awesome.
Right?
So, I mean, that's, like, a few hours once a year you can do that.
And if you learn something, you're exploring some new library and you're having a hard time finding documentation or it didn't seem clear, record a video and put it on YouTube.
Right?
Of what you figured out and just, like, to teach somebody how to get started.
Right?
A lot of ways to get back.
Jessica, let me ask you a few questions.
Put you slightly on the spot before I let you go.
Sure.
Yeah.
A question I always ask my guests at the end of the show is, what's your favorite editor?
If you're going to write some Python code, what do you open up?
Sure.
I mean, I'm an Emacs user through and through.
Yeah?
Learned it at MIT and that was that?
Yep.
Pretty much.
Hey, you can, look, you can run a web browser inside of Emacs.
Why would you not want to do that?
Of course.
That's awesome.
And then, you know, there's so many awesome packages out on PyPI that people can just go and grab, you know.
What are some of the ones that you think people maybe don't know about that you'd like to highlight or talk about?
Gosh, I think my answers to this are probably, unfortunately, quite niche.
There are lots of, there are libraries that facilitate, how do I even describe this?
I do, I participate in a lot of capture the flag events.
And so there are a lot of like Python bindings for various types of like program introspection that you would do.
Like if you want to disassemble something and then like trace flows to the program, there are like there are Python libraries that facilitate that.
So like where, or to automate some of those processes.
So where you might use like IDA pro or whatever to be disassembling and analyzing a binary for a capture the flag event.
Like you can actually do a lot of this stuff in Python.
But that's like a super niche answer that is maybe not what you were going for.
No, that's good though.
I mean, everybody has their own specialty and it's cool.
It's like, otherwise we'd hear NumPy, we'd hear requests, we'd hear SQLAlchemy.
Yeah, right.
I mean, so that's exactly what I was looking for really.
Although the other thing I would say is that it's very, very cool that there are such strong,
there are such strong communities around certain various disciplines.
And that's very exciting for me.
So it's like astronomers have all kinds of like super sophisticated astronomy focused packages on PyPI.
Like basically all of the science disciplines for like finance, there are a bunch of like very sophisticated Python packages.
And it's like the fact that we've gotten to that level of specialization and like the ability to support these domains in this very sophisticated way.
I think that is very cool.
That is.
Yeah, right.
That's an absolutely huge win for the Python community.
And I think it's just accelerating the diversity of people coming from these different disciplines.
Yeah, that's great.
Final call to action.
People get out there, contribute, donate your time, give a little back.
Jessica, thanks for being on the show.
Thank you so much for having me.
Yeah, you bet.
Talk to you later.
This has been another episode of Talk Python to Me.
Today's guest was Jessica McKellar.
And this episode has been sponsored by Hired and Optbeat.
Thank you guys for supporting the show.
Hired wants to help you find your next big thing.
Visit Hired.com slash Talk Python to me to get five or more offers with salary and equity presented right up front and a special listener signing bonus of $4,000.
Optbeat is mission control for your Python web applications.
Keep an eye on errors, performance, profiling, and more for your Django and Flask web apps.
You can find the links from today's show at talkpython.fm/episodes slash show slash 30.
Be sure to subscribe to the show.
Open your favorite podcatcher and search for Python.
We should be right at the top.
You can also find the iTunes and direct RSS feeds in the footer of the website.
Our theme music is Developers, Developers, Developers by Corey Smith, who goes by Smix.
You can hear his entire song on talkpython.fm.
This is your host, Michael Kennedy.
Thanks for listening, everyone.
Smix, take us out of here.
Staying with my voice.
There's no norm that I can fill within.
Haven't been sleeping.
I've been using lots of rest.
I'll pass the mic back to who rocked it best.
you
.