A strong community is one of Python's superpowers, and that's what this episode of Talk Python to Me is all about.
It's PyLadies and Python Software Foundation with Lynn Root.
Episode number 15, recorded Thursday, June 6, 2015.
Hello, and 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,
and keep up with the show and listen to past episodes at talkpythontome.com.
This episode, we'll be talking to Lynn Root about PyLadies, Python Software Foundation,
Python at Spotify, and the Python community at large.
I'm really fortunate to have CodeChip and Hired sponsoring the show.
Let me take just a few seconds to tell you about them.
CodeChip is a platform for continuous integration and continuous delivery as a service.
They encourage you to always keep shipping.
Please take a moment and check them out at codeChip.com,
or follow them on Twitter where they're at CodeChip.
Hired wants to help you find your dream job.
Hired is built specifically for developers looking for new opportunities.
Check them out and get a very special offer at hired.com slash talkpythontome.
And you'll find them on Twitter where they're at hired underscore HQ.
Before we get to the show, I have a quick piece of news for you.
Thanks to everyone who backed my Talk Python to Me t-shirt Kickstarter.
This week is the last week to join and get your shirt and promotional slot.
Check it out at bit.ly slash python shirt.
Now, let's get right on to the interview with Lynn.
Let me introduce Lynn.
Lynn Root is an insomniatic software engineer for Spotify,
the founder of the San Francisco chapter of PyLadies,
a board member of the Python Software Foundation,
and a member of the Django Software Foundation.
Lynn, welcome to the show.
Oh, thank you so much.
Yeah, we have a lot to talk about today, a bunch of different topics.
And, you know, I've read a little bit of what you've written online
and checked out some of your talks.
And you have a lot of interesting things going on.
Yeah, I feel like I'm juggling a lot.
But thank you.
Yeah, the context switching is hard sometimes, isn't it?
It really is.
Yeah, but I think in the end, it's worth it to be part of a lot of exciting things.
So let me be one of the first podcasts to say congratulations.
I'm being reelected to the Python Software Foundation board.
That happened just a couple days ago, right?
Right, right.
Thank you so much.
Yeah.
Yeah, you must be excited.
How long have you been on the board?
This will be my third year.
So I've been on for the previous two years.
Okay.
Oh, very cool.
Very cool.
So I want to talk about that more.
But let's start at the beginning.
You've written a couple really cool articles about sort of your path into engineering
and into programming and into Python.
You know, you're doing a lot of work to help other people walk that path and take that journey
in their own way.
And I think it's really interesting to maybe cover some of that or talk a little bit about
it.
Can you maybe tell us how you got here?
Sure, certainly.
So yeah, I actually have a business degree.
I went to Babson College in Massachusetts.
And I graduated with like econ finance.
But I don't know if you remember, but in like 2008, the economy kind of sucked.
And that's the year I graduated in.
So it was really, really kind of difficult to get a decent job in finance.
But in terms of decent like paying.
So I actually I started working as an analyst for a small bank for a few years.
The economy is still crappy, but I wanted to get my master's degree in financial engineering.
And Berkeley here in California actually has a really good program, like a one year master's
of engineering or financial engineering.
And but in order to apply, you kind of had to like know how to code.
And me being a sort of a fresh graduate and like thinking, oh, I could still like learn
how to study.
Right.
I just how hard can it be?
Come on.
Right.
Yeah, exactly.
I decided to enroll in like a Harvard's extension program, just like their intro to CS class.
And so that was like the fall of 2011.
And let me tell you, C is really hard.
And I really sucked.
Like I failed like a lot, all the midterms.
I was crying a lot during the weekly homeworks.
And it was just it was really tough.
Were you wondering what you had gotten yourself into?
Yeah, seriously.
It was just like I literally just like was hoping to get a passing grade just to like get this
over and done with.
Yeah.
But like I couldn't who would subject themselves to this kind of thing.
And but but oddly enough, towards the end of the semester, I saw some Python code and coming
from C to Python.
I was just like, wow, I like actually understand what's being written.
I actually understand the logic.
Like I can see what's going on here.
So I actually decided to do my final project for the course in Python.
I made a little Django website app that looking back now is really crappy code.
But it worked.
And somehow I got like an A minus in the course, even though I failed both midterms.
That's amazing.
The professor must have thought, well, she's come a long way.
Look what she built.
You know, let's just forget about about those bad midterms.
Right.
Exactly.
I wonder if they ever questioned like the legitimacy of that code.
Like, how could she come from this to that kind of thing?
But like I really wrote it like I also wrote that crappy code.
But anyways, I found it a lot more satisfying to like stay up at like 3 a.m.
trying to like debug like this Django app than like looking at Excel spreadsheets,
you know, like eight hours a day, five days a week.
So I basically decided that I wanted to continue to learn but not pay Harvard another $2,000 for a course.
So at the time I was in San Francisco.
I still am in San Francisco.
But at the time I kind of approached Women Who Code, the local meetup group here,
and see who else could like would be interested in learning Python with me.
So I started like a study group with other women and kind of led projects.
Basically, I would do the project the week before and then sort of present it and we'd work through it together.
That's really cool.
And I think I recall from your article, there were quite a few people there, right?
It was like 40 women or something like that?
Yeah, exactly.
That's awesome.
Yeah.
To be honest, I don't know if they came for like the free food at Dropbox or if they really wanted to know Python.
But it was awesome to see them there.
And there's a lot of great interest in continuing on because I had only planned like eight weeks once a week.
And so that actually turned into like two PyLadies of San Francisco.
I sort of stole those women.
Not really steal, but like they helped me build sort of PyLadies of San Francisco.
From there, I was able to subject other people to wanting to learn how to code with me.
And I guess the rest is history.
I sort of just kind of started talking about what I was doing.
Kind of from the point of view of me being sort of selfish and like wanting to learn how to code with others with me.
But it sort of morphed into like getting women involved in coding and me speaking about that.
And that really helped me like land my first engineering job.
That's really cool.
You know, I do a lot of training for my job as well.
And I think this pressure to put together a presentation, to learn it well enough to like present it to others, is a super powerful way to learn for yourself, actually.
Right.
Yeah.
You better have the answer to the questions that you don't even think of right now, right?
Exactly.
Yeah.
So you think that really helped you sort of gain the skills you needed?
It definitely did.
At least like helped me like understand what was going on rather than just copying, pasting code, which is like not a really good way to learn how to code.
Sure.
I think that happens more in this industry than people really want to admit, to be honest.
I agree.
I mean, I fully admit that there are some like Stack Overflow posts that I just copied and pasted.
And it just happened to work and went on from there.
So yeah, I believe it happens a lot.
Yeah, I think so.
CodeChip is a hosted continuous delivery service focused on speed, security, and customizability.
You can set up continuous integration in a matter of seconds and automatically deploy when your tests have passed.
CodeChip supports your GitHub and Bitbucket projects.
You can get started with CodeChip's free plan today.
Should you decide to go with a premium plan, Talk Python listeners can save 20% off any plan for the next three months by using the code TALKPython.
All caps, no spaces.
Check them out at CodeChip.com and tell them thanks for sponsoring the show on Twitter where they're at CodeChip.
When you're doing C++ or C, it was just really frustrating.
And just the simplicity of Python really resonated, huh?
Definitely.
Yeah.
It's just like, oh, I can actually understand that you're defining a function and trying to do it, like, mangle the data in this way and return this.
Like, I actually got that in me to be able to, like, a couple months later, I sort of finally understood, like, inheritance when I was digging through, like, Django, like, source code.
And I was like, well, this actually makes sense to me than, like, programming, like, a Sudoku board in C where I just have no idea what I'm doing.
Yeah.
And pointers to pointers to a raise.
Like, yikes.
Uh-huh.
Right.
Let's maybe talk a little bit about PSF.
Sure.
I kind of know the mission statement of PSF.
And I know that there's a board.
But can you maybe tell all the listeners kind of what is the Python Software Foundation and what kinds of things do they do to help all of us?
Sure.
Yeah.
So this question happens a lot, actually.
And maybe it's a telling sign that we need to do better PR about who we are.
But the PSF, the legalese or, like, what we are about in formal sense is both protecting the trademark of the Python language and kind of, like, owning that and stuff like that, as well as furthering, like, the language of, like, becoming more widespread.
And that's essentially what it boils down to.
And the PSF has, like, has the board with 11 directors and then has, like, a membership model.
And there's a few different ways to be a member.
But basically, the purpose of the PSF is to, like, make sure Python as a language can, like, remain a popular widely used language and kind of get it everywhere.
And as a PSF board, we do a lot of both kind of just, like, answering simple questions, like, can I use Python here?
Can I represent the logo here?
Like, simple questions like that.
We get a lot of, like, requests for, like, funding.
Like, can you help with these, like, food costs for this, like, Python sprint or something like that.
We help a lot of workshops, especially, like, the, like, young coder workshops that Katie and Barbara have been doing since 2012, I guess.
And that is mostly based on, like, help getting, like, Raspberry Pis so that teenagers and young kids can, like, learn how to, like, program in Python and actually take home what they're doing.
PSF sort of supports Python in that sort of way.
And I guess that's as best off the top of my head of describing the PSF.
Yeah.
That's really cool.
And I think it's just good to raise everyone's awareness about that.
It's nice to have a single organization or group that is kind of can answer, like, public questions and make decisions and stuff like that around the publicity of Python and whatnot.
I also heard that they were doing a lot to help promote the usage of Python 3.
I feel like the PSF is usually, like, throwing, like, the money at it.
Like, if someone requests, like, funding to help porting stuff, we're definitely 100% behind that.
I feel like the louder voices of supporting Python 3 is more like Guido himself and some other core devs.
We personally, the PSF doesn't really outwardly, like, back, like, public statements.
But we're definitely, like, since, like, Python 3 is the future, we often get requests to help, like, funding, like, the porting of something from 2 to 3.
Like, a really, like, established, like, library, like, mailman or something like that.
Right.
Of course, I had Chris McDonough on the show.
I think that was show 3.
Mm-hmm.
And he talked about that story with Pyramid.
Oh, yeah.
The Pyramid web framework.
Yeah.
Apparently, he said, I'm dragging my feet on converting it to Python or, you know, supporting Python 3.
And the PSF came along and helped out and said, can we give you a nudge to make you go do this?
And he did.
Yeah.
That's awesome.
Yeah.
That's really cool.
So, as a board member, what do you do there?
The board member, being a board member is, it varies on how much work you want to put in.
And, like, we have monthly meetings or somewhat monthly meetings, regular meetings.
And we vote on stuff like, should we give money to these people or those folks?
That's actually a lot of our conversation is deciding who to help out.
As well as, like, let's see, like, sponsors.
Like, who can we invite to be a sponsor?
Who is applying to be a sponsor?
Things like PyCon and so on?
Well, so, that's actually, PyCon is, like, the only conference that is, like, directly supported by us.
But we just sort of have, like, a PyCon officer that's supposed to be, like, the liaison between the two, like, organizations.
And we definitely, like, a lot of the money comes out of the PSF and the sponsors of both the PSF and PyCon.
But we definitely stay out of, like, the day-to-day logistics, the planning and stuff like that.
Sure.
More high level.
That's cool.
Yeah.
And just trying to think of other things.
I just, like, it seems like every meeting we're voting on, like, five, like, new funding requests.
But it's definitely, like, just to, like, help kind of guide, like, the PSF.
Like, we recently started, somewhat recently, like, past year or so, started this, like, working group model where it kind of helps, like, people who want to get involved in the PSF and aren't, like, board members themselves can still, like, really contribute to the PSF.
Like, we have a working group around, like, elections and, like, how to better, like, the process of elections.
And the PSF's job is to sort of, like, recognize that working group and help provide the tools so that they can be successful.
That's great.
So if somebody out there is listening and they want to get involved, what kinds of things can they do and how do they go about that?
Good question.
So just to be a member, it's actually quite simple.
It's just, like, python.org slash PSF slash membership.
And there's, like, different membership classes.
The most basic, the lowest tier one is called Basic Members where anyone can sign up.
However, in order to be able to, like, vote and stuff, you'll either have to, like, be, like, a contributor in terms of, like, code or, like, sort of contributor in terms of, like, community, like a meetup organizer, like PyLadies organizer or something like that.
Or you can, like, give money either as an individual or as a company yourself.
And that's, like, how you can, like, vote in terms of, like, the board and, like, who to accept as company sponsors, stuff like that.
And if you wanted to get, like, if someone wanted to get involved beyond that, at least become a Basic Member and, like, join all the mailing lists that I can't even remember off the top of my head that are interesting to them.
And somewhere on our wiki, the wiki.python.org, is a list of all of our working groups.
And I'm sorry, I don't have the link up right now.
That's fine.
We'll put it in the show notes.
Oh, great.
And that way they can, like, ping individual people of, like, who they want to, like, help out, like, maybe, like, outreach and education or, like, sprint, like, committee or the elections working group or something like that.
And you can get involved in that way.
Just participate in the discussion as much or as little as one wants.
And then, yeah, we have a pretty active PSF members list.
And that's also a good place to kind of have your ear to the ground and know what's going on.
Okay.
Yeah, that sounds really great.
Basically, the starting points, go become a Basic Member and then go from there, which is just a matter of creating an account, more or less, right?
Right.
Yeah.
We have, like, there's information, like, everywhere.
And I'll be the first one to say or, like, to agree that it's really poorly laid out, like, where to find what information and, like, what could you be interested in?
Like, I don't even know kind of thing.
Is it, like, a new member or something like that?
So it's definitely really hard to kind of, like, figure out where to go and stuff.
But becoming a Basic Member and joining, like, the PSF members list is definitely, like, step one.
And then you can ask as many questions as you want from there.
Okay.
Yeah, that's really helpful.
Thanks.
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.
Opportunity's knocking.
Visit Hired.com slash Talk Python to me and answer the call.
Another thing I wanted to talk to you about is PyLadies.
And it sounds like PyLadies is sort of what became of your study group that you started.
Right.
Yeah.
And I'm really surprised.
You said that it didn't exist in San Francisco, but it did in L.A.
And you're like, why is this thing not in San Francisco, right?
Exactly.
Yeah.
I mean, that's the whole reason I have this podcast.
I went looking for a Python podcast.
I'm like, why is there no Python podcast?
What happened to them all?
Well, I guess if you really want something, you might have to make it yourself sometimes,
right?
Exactly.
Yeah.
So you started PyLadies.
That's awesome.
How long has that been going on, actually?
So the San Francisco PyLadies has been around since April 2012.
So a little over three years, I guess, if my math is correct.
And the first PyLadies in L.A. started sometime in the fall of 2011.
I don't know exactly when.
So it's pretty established in terms of communities.
And yeah.
Sure.
It's a little regional because this is an international show.
But for those listeners in San Francisco, where do you guys meet?
Oh, it varies.
I mean, tonight we have a meetup and we're going to the Uber office downtown.
But we have a lot of weekly meetups, like study groups that go to the LinkedIn offices down
in South Bay or Rackspace slash Geekdom up here in San Francisco area.
But I mean, we have so many locations worldwide.
And a lot of times it's just like regular meetups at a local coffee shop or something like that.
Yeah.
So if I wanted to see if my local city, like I live in Portland, Oregon, I want to know,
hey, is there one in Portland?
I think there is actually.
There definitely is.
Yeah.
How would I find out about it?
Certainly.
Yeah.
If you just go to like PyLadies.com, we have like a locations page.
And we have a list of all like locations.
There's some that aren't up there because in order to like have like your location up there,
you have to do like a pull request on GitHub.
And sometimes it's just too much for people to like do or too little of like a task item to
like remember.
So like that's not a complete list.
But it's definitely a very good place to start.
Now, if you find out that there is no PyLadies like locally, you're more than welcome to start
one kind of like how I did myself and how you did your podcast.
There's a nice little jumping off point, kit.pyladies.com.
Oh, nice.
Yeah.
That's our like starter kit of like how to bring PyLadies to like your location if you want it.
Cool.
Yeah.
We'll put that in the show notes.
Yeah.
I think it's really great that you're promoting more diversity in general and specifically about
women in programming.
You know, I have three daughters and, you know, I would like to see a world where they are excited
about these kinds of things and feel like it's a welcoming place.
Definitely.
I don't know what it is about Python, but it seems like it has a better story in terms of
diversity compared to other languages.
I would agree with that.
Yes.
Go ahead.
Yeah.
I was going to say, I have no idea why this is the case, but I do a lot of training and I'll
do training with like classes like MongoDB or C# or other things, JavaScript and so
on in Python, of course.
And it seems like the Python classes just have a whole, a whole different population that
just seems to represent society more correctly than, than the other stuff, which, which is
really nice, but I don't really know why.
Right.
I mean, I started to hypothesize this myself, at least comparing with like other like communities,
not necessarily like C, but like, like Ruby or Java or Node, whatever.
It really helps to have like sort of leadership of the community kind of really like buy in.
But it really helps us that like Guido himself is really passionate.
He was actually the first, one of the first speakers that I had at like my Women Who Code
Study group.
Oh, wow.
That's excellent.
Yeah, I know.
So he's like 100% behind this, these sorts of efforts.
And it's very convenient that he lives in the Bay Area for me, right?
Yeah, that's cool.
He had a really nice presentation that sort of touched on this at PyCon 2015 as well.
Right.
Yeah.
He, he asked, or he wants, he wants basically like women as core developers, because currently
there are none.
And I think he was like, he's like, I'll help mentor folks or help mentor women to be a core
developer.
And, you know, I think that's like really awesome.
And I'm, I'm actually, I have like a pretty good idea for a meetup here locally, since he,
since he's like down the street, practically.
So that's sort of help kind of get involved in committing to, to see Python.
But yeah, it really, it definitely helps when like leadership like him and the PSF organization
itself kind of set the tone of why it's important and, and people sort of just follow.
Of course, you know, there's always descending voices in any community in any stance, but it
really helps to see that like when leadership says that this is important, people will feel
more, more willing to like help out or to like just be proactive about something.
So I think that that's the difference between like the Python community and other communities.
I agree.
You know, there's probably a lot of people on these types of issues that are like sort
of just sitting on the couch, like, I'd like to do something about it, but whatever.
You know, those little nudges might be enough to actually make a change.
Right.
Exactly.
Another thing I'd like to talk about is a project that you're involved with called New Coder
at newcoder.io.
Right.
Yes.
What's the story with that?
That looks cool.
Thank you.
Um, yeah.
So this was, so I wrote this a couple of years ago, 2012, I believe is when I first
released it.
Um, and it's basically, taking, no, it was 2013, I think.
I'm basically taking all these sort of projects that I subjected to the people that came to my
study group and, and made it in like written form.
So like, not just like San Francisco piloties can use them, but like everyone who
want, who's willing to learn Python and wanting to learn how to code can, can reach.
So, the, the premise of this is like, say you, you know, did learn Python the hard
way or dive into Python or some other sort of work book, like, like sort of goes through
the syntax and a little bit of like logic of Python.
And you're like, all right, what next?
What can, like, I'm not going to get hired right now.
So, what can I actually do?
So, with new coder is, is there, it's five different, tutorials and, it sort
of, it definitely graduates in sort of, difficulty.
Um, but, there's no real order.
You can like choose whatever order that you want, but, it, the, it's meant to teach the
new coder, like various things at various points in time with certain noob friendly language.
Um, and like asides, like you might not know this term.
Like, or you might not understand what a class is or inheritance is.
So here's where you can read more information or, or here's a little blurb that you can just
go ahead and skip.
If you actually do understand this kind of thing.
Right.
That's really cool.
And I think one of the challenges people have, especially when you're a beginner is to put
meaning behind the thing you're struggling with.
So for example, if, if you're like having a really hard time with a for loop, foreign loop,
or you're having a hard time with like if statements or functions, those are all so small building
blocks that they're not interesting in and of themselves.
But if, but if you can see like, okay, if I force myself to learn these little kind of
trivial, not trivial, but you know, sort of fact based things that I have to just memorize
or understand, I can do something awesome on the other side of that.
And I think these projects are the key to like making that shortening that cycle, I guess.
Yeah.
Thank you.
Yeah.
That's definitely something I was trying to go for with that.
But yeah, I've got, I've gotten a lot of good feedback from people just like sending emails
saying, you know, like this is exactly what folks needed.
And like, I find that when I lead workshops explaining these sorts of things in the way
that I've written down a new coder, it helps people kind of like, like have those light bulb
moments, which are really needed, especially when you're a new coder, because there are a lot
of frustrating moments.
And to have like a little light bulb moment is really reassuring.
And then to have, and then to have something at the end of the tutorial that you can show
off to someone else, that's also rewarding rather than like some simple exercise from like
when Python the hard way, like, yay, I did a for loop.
Look at that.
Yeah, exactly.
Yeah.
If you have a tutorial with like, you know, data visualization, like from, map plotlib or
something, it can actually show that to someone.
Yeah.
I think that that serves a lot of purposes.
You know, I read somewhere, somebody had studied a bunch of entrepreneurs and people
in Silicon Valley that, that became successful.
And they said, it seems like by studying these people, we've, it's not necessarily the case
that the people who succeed versus the people who fail are the ones who are the smartest.
It seems like the, the most important skill is persistence.
The ones who just keep trying until they find their way through these, these types of things
that you have to power through when you're, you're getting started on stuff and, you know,
more complex as you start companies and so on.
It seems to be the most important skill.
Right.
Yes, definitely.
And I think tutorials and like concrete examples and stuff make it easier to be persistent because
you see what's down the tunnel.
You're not like, oh, I hate programming.
It's all these little facts.
It's like, it's kind of like learning math in the early days when, when nobody connects
any dots for you.
Right.
Exactly.
Yeah.
Cool.
So you have five tutorials up there now.
You've got data visualization, APIs, networks, web scraping, and GUI stuff, right?
Right.
Yes.
Yeah.
So those are fun.
And people, if they're, they're getting started or they want something more practical
than just language stuff to play around with, or they need to recommend a resource for someone
else, more likely if they're listening to this podcast, then, you know, check out newcoder.io and,
you know, pass it around.
Thanks for the plug.
Yeah.
You bet.
No problem.
That's really cool.
You also have some open source projects that you're working on connected to your work at
Spotify, right?
Right.
Yes.
Do you want to talk a little bit about those?
Yeah.
I'd love to.
So conveniently, actually, this week right now is our hack week.
About twice a year, Spotify holds hack weeks to just kind of hack on what you want, not
necessarily like Spotify, but it could be Spotify related.
And a year ago, I actually hacked together a prototype as a Flask app that was, it's like
a playground for APIs.
If you go to developer.spotify.com slash web dash API, there's a console linked there.
And you can actually play with our APIs via the console to kind of figure out what goes
on, what kind of responses you'll get, what kind of queries that we accept, that kind of
stuff.
I mean, it was pretty awesome because like it came out of a hack week.
Everyone sort of like understood why it was important because I hated answering sort of the
same questions over and over again.
How do I use your API?
So I built this.
And I guess like a lot of people loved it that we just sort of put it out there and it's been
really successful.
And from that, I've, I'm open sourcing the technology behind that.
And the first thing that I open source, which was just a couple weeks ago, is a RAML parser.
And the actual library name is called RAMLifications.
Good name.
Yeah.
I love punny names.
But RAML is like, it stands for REST API markup language.
And it's like YAML.
And it's basically a way for you to kind of define how an API is.
Like we have a Spotify API defined in RAML.
And you can see the title is like web API and like the base URL, the version, like the endpoints,
if it accepts like OAuth or, or something else, that kind of stuff.
So it's a really like great, like source, like end all be all source for a web API.
And so the RAMLifications, like it parses that into like Python, like objects.
And then this week I'm taking that and writing like a static documentation generator.
Just making like HTML files that you can like, like host anywhere that creates documentation off of RAML.
So if you have your API, your REST API defined in RAML, and like you've written like all the docs in there kind of thing,
you can just, you know, run it through this new project that hopefully will be open source soon.
And you'll have some nice HTML files.
And then from there, this is like the in-between step, I'll actually like open source the console itself.
So that, so folks can make their own sort of web site for how to interact with, with their own API.
Yeah, that's really neat.
I think those are a cool set of projects that all kind of work together.
A lot of times you'll end up with these, you know, just basically static documentation around, around people's APIs.
And then, you know, if it doesn't quite work, like the way you're interpreting what they have written, or, you know, if, if it changes and the API documentation comes, becomes out of date, it's super frustrating.
Right.
And you end up writing these little, little apps to just like call the API and spit it out to go, okay, this is what I'm actually getting.
What does it look like?
And, and your, your web API console is just like, let's skip that.
And you can just check it right here.
Right, exactly.
And some people are just more visual or more interactive rather than reading through documentation.
So, yeah.
Yeah.
It's never really like inspiring to read through documentation.
I think it kind of goes back to that persistence thing.
Like, am I willing to power through this so I can have a cool app that uses Spotify or, or am I going to stop because the documentation is, is too much.
Right.
But luckily you're solving that problem.
Have you noticed any change in like the adoption of the API or how long has it been out?
It's not.
I think it's been out at least six months or so.
Okay.
So maybe that it could possibly have some sort of effect you could see.
Right.
I'm going to be honest that I don't pay attention to our usage, web API usage.
But I do know that like the site that the console itself gets maybe like low tens of thousands of views a month.
So it is being used.
And yeah, it's definitely an internal favorite too.
Yeah.
I'm sure.
I'm like, oh, I want to test our own API.
Let me go have a look.
I forgot what this does.
Right.
I'm sure this happens.
Or hey, you're new here.
Go here first.
Go check this out.
Right.
Yeah.
Nice.
So it sounds like these projects are really closely tied to what you're doing at Spotify.
And they're all in Python.
What's the story with Python at Spotify?
Can you talk about that?
Sure.
It's actually kind of a sad story.
So my team and what I do, I'm back an engineer with five other developers.
And we do like strategic integrations.
We're based in San Francisco.
So like a lot of the integration projects is with other local San Francisco like companies.
For instance, the recent Spotify and Uber integration where you can like listen to music during your ride through the car speakers.
Like that was like us.
That was our team that did that.
That's pretty awesome.
Yeah.
So it was really awesome.
Really fun.
And so we do stuff like that.
And in some cases stuff is written in Python, but more often than not it's now being like written in Java.
The reason is we kind of like we kind of had this like corporate like mandate maybe about a year ago that we're kind of writing new services that have end user like facing like capabilities or like whatever.
They have to be like written in Java.
And it's because that I know a lot of people will say, well, wait, Spotify is like IO bound, not CPU bound.
Why the move?
And it's true that we are IO bound.
And however, there's a lot of issues when trying to run like, I don't know, like 23 like processes of the same service on one machine trying to connect to the same Postgres database and memcache and stuff like that.
So there's a lot of orchestration that gets complicated when you have multiple like Python processes running on one server.
So believe me, I've tried, I've had many arguments.
I've like sat down with our senior architect and really try to like go for Python and maybe PyPy or something like that.
But in the end, I kind of like lost the argument.
And so a lot of our end user facing stuff like the web API is written in Java.
However, there's a lot of other stuff written in Python.
For instance, let's see, all of our analytics stuff is in Python.
We have Hadoop and we can run stuff with Java, but a lot of the actual jobs are written in Python.
And then we have, let's see, like our DNS sort of service discovery systems written in Python.
However, I think that's starting to move to our payment system in Python.
Content management where like the labels that actually give us the music, that they'll dump a lot of metadata and songs itself to us, like FTP or something like that.
And we process all of that in Python because it's like not really end user or speed.
Yeah, you're not concerned about shaving that 5% performance off or whatever, right?
Right, exactly.
So there is a lot of Python within Spotify.
It's just like not what...
It's not at the center.
Yeah, yeah, exactly.
Yeah, okay.
Well, that sounds really interesting.
You were saying like some of the thoughts about like running a bunch of processes on this machine and on the treble.
You know, maybe you guys could try some tricks with Docker.
This could be a possibility.
We actually...
Have you tried that?
We're actually using Docker.
We're migrating towards Docker.
We have open source Helios, which is our Docker manager or something like that.
And that will also...
That supposedly, in a lot of Pythonistas' eyes, will allow us to be okay with like running our services in Python.
But it's still in the very early stages of like what Docker and Helios can do.
Okay, that's really excellent.
That's at github.com/Spotify slash Helios.
I'll put that in the show notes as well.
Very nice.
Yeah.
And then have you guys thought about Jython?
Like if you're so into Java?
Yeah.
I actually don't know what our senior architect feels about that.
I don't...
Like I've actually never played with like within Jython.
But it's definitely something to go the direction to look into.
Sure.
I know some of the other major companies around there are using it.
But I probably shouldn't talk about it since I'm not sure if I'm supposed to.
If I'm allowed to.
But yeah, there's definitely some large like high-end web companies out there doing cool stuff with Jython.
For a while, I thought it was dead.
It seemed like it hadn't been updated in a long time.
It was like supported like Python 2.5 or something.
And finally, I think it now supports 2.7, but it still doesn't support 3 as far as I know.
Mm-hmm.
Right.
A couple of years or maybe like a year and a half ago, we had one of the core developers of Jython come speak up, high ladies.
And he was like, we just released 2.7 and now we can start 3.
So there is energy and people behind it.
It's just like not enough people.
I'm sure it's a massive project.
And if it doesn't have a lot of support, it's really hard to keep up.
Definitely.
But yeah, I'm glad to see it going because I know it enables some people to do cool stuff, which is all good.
Mm-hmm.
Right.
So another thing that you like to do is speak in at conferences and user groups and meetups and stuff, right?
Right.
Yeah.
And I saw you have a page with a whole bunch of sessions, like, I don't know, just a quick scroll count.
It's like 15 or something, but quite a few at rogueland.com slash talks.
Mm-hmm.
Are there some of your favorites up there that you want to, like, point out to people, maybe have videos or something?
Right.
As an aside note, I literally just, like, over the weekend redid my site.
And I only redid it for, like, the words part, like, the blog part.
So I apologize if, like, people are going to, like, rogueland.com slash talks and be like, ew, this looks ugly.
Like, whatever.
Like, I'll get there.
Let's say it looks minimalist, huh?
Yeah.
Yeah, definitely.
But yeah.
So, like, actually, one of my favorite talks to give is how to spy with Python.
And it's basically, like, working with Scapee, the project Scapee, to basically sniff, like, wireless traffic.
It's a Python wrapper around TCP dump.
And it's really fun to show people what you can do because that's basically what the NSA is doing.
And, like, it's a tongue-in-cheek way to, like, show people, like, what's going on in, like, an international global level of, like, privacy issues.
But Scapee is a lot of fun to play with.
And it's one of my favorite talks to give.
Yeah, that sounds really cool.
Yeah.
I recommend people check it out.
And some of these are on YouTube and other places, Vimeo, whatever, right?
Right, yeah.
I try to link to everything.
I should probably update some of this stuff, too.
Well, if the page is in for a refresh, maybe, huh?
Yeah, right.
Cool.
I'll put some of those in the show notes as well, and I'll link to that, of course.
I think that just about covers all the stuff that I wanted to talk to you about.
And I think it's a whole bunch of interesting paths.
Like you said, it's a little scattered, but they're all super interesting.
And so if people are out there with, like, meetups or user groups, can they, you know,
do you recommend they go to New Coder and try some of your tutorials,
maybe make those, like, workshops or sessions or something there?
Yes, definitely.
I have a couple of them.
If you go to New Coder, I think it's just slash workshops,
that there's, like, PDF versions of everything.
They do need to be updated since my last site refresh.
But everything's also on GitHub.
And please feel free to, like, take them, adapt them however you want,
and teach off them.
A lot of PyLadies leaders actually take a couple of tutorials to lead their own workshops.
So by all means.
You know, I've done some stuff with Hour of Code and so on,
and it seems really daunting to lead those types of groups
and put something together for people to really appreciate.
But if you can grab a resource like that, or, you know, in the case of Hour of Code,
some of the little tutorials and stuff they have online,
it makes it so much easier to get involved and help out in the community.
Right, definitely.
There's one more thing for people to, let's say it this way,
there's one fewer excuse for people to use.
Right, yeah.
All right.
Anything else you want to talk about while you're here?
Let people know about?
Well, I'll be at EuroPython.
So if anyone else is going to EuroPython, come to say hi.
I'm giving a couple talks there.
That'll be excellent.
What are the talks?
One is one that I actually just gave this weekend.
It's about how my team is doing metrics and how we're, like, it's metrics-driven development,
how we're powering sort of the data that we are newly collecting behind, like,
the sort of decisions that we're making.
And the talk is about kind of taking what we learned and, like,
you don't need to necessarily measure everything, but, like,
what do you need to measure and how do you decide that?
And then the other talk that I'll be giving is basically kind of sort of like a status update
slash what we still need to do about, like, diversity in Python.
We've come a long way, but there's still a long way to go to really sort of create a welcoming environment for everyone.
And since Python community is a leader, we should, in that sort of thing,
we should definitely continue to be a leader in being very diverse and welcoming.
Yeah, I totally agree.
And it seems like that's still a really positive thing going on there.
It's just not done.
Right, right, yeah.
All right, so one of the questions I like to ask my guests before we wrap up a show is,
what's your favorite PyPI package or thing out there that you'd like to tell everyone,
hey, check this out, it's really cool?
Ramifications, of course.
Right, yeah.
But besides something else that I've written,
one of my favorite packages that kind of was released a few weeks ago was adders, A-T-T-R-S.
And it's basically a package that allows you to, like, not have to write a bunch of boilerplate code.
Like what? Give us an example.
So actually, I use it in ramifications.
Adders allows you to kind of, like, make a nice class and, like, set some attributes of, like,
this should be in the init method or should be in the repr method.
And allows you to do, like, some, like, comparisons, like a complete set of comparisons.
It just, it makes, like, writing code even easier, even more simpler.
Yeah.
Yeah, that's cool.
Very cool.
Like default values and things like that.
Right.
Yeah.
Okay.
Exactly.
Very nice.
Yeah, I'll put that in the show notes.
And they've got some good documentation as well.
Yes, definitely.
And, yeah, ramifications definitely uses it.
And, like, so much more code would have been written without it.
Really nice.
All right, final question before you go.
What editor are you using these days?
I use Sublime.
Sublime.
Oh, yeah.
Yeah.
I like Sublime as well.
I do, too.
My coworker's trying to get me to use, like, PyCharm or IntelliJ.
But, I mean, every time I try, I just get sad.
So, I just move back to Sublime.
Yeah, that's really interesting.
I use Sublime for a lot of things.
I'm a big fan of PyCharm myself as well.
But I certainly, you know, a close second is Sublime for many things.
It's definitely nice.
Right.
All right, Lynn.
Thank you for being on the show.
It's been super interesting to touch on all these topics.
Yes, thanks for having me.
It's been a lot of fun.
Yeah.
Great.
And we'll put links to, like, your website and your Twitter and everything in the show notes
so people can just go to the website and find you that way.
That's fantastic.
Thank you so much.
Thanks.
Bye.
This has been another episode of Talk Python to Me.
Today's guest was Lynn Root.
And this episode has been sponsored by Codeship and Hired.
Thanks, guys, for supporting the show.
Check out Codeship at Codeship.com and thank them on Twitter via at Codeship.
Don't forget the discount code for listeners.
It's easy.
Talk Python.
All caps.
No spaces.
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 a salary and equity
presented right up front.
You'll also get a special listener signing bonus of $4,000.
There are just two more days to get the Talk Python to Me t-shirt.
Quick, go to bit.ly slash python shirt and reserve yours before the Kickstarter closes on Thursday.
You can find the links from the show at Talk Python To Me.com slash episodes slash show slash 15.
And before you go, 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 on the website.
This is your host, Michael Kennedy.
Thanks for listening.
Smix, take us out of here.
I'm first to follow.