How do you go from poking around at Python code to actually solving real problems the right way?
Well, there are many paths. The longest one probably is to get a four-year computer science
degree. Maybe faster, but pricey still, is a solid in-person developer bootcamp.
But have you considered reaching out to the community to find a mentor?
Many Python meetups have project nights where folks who could help will be attending.
And if you're up for giving back, maybe you could become a mentor at one of these events.
That's what this episode is about. We'll hear from two former guests of Talk Python,
Rusty Gregory and Doug Farrell. They teamed up and are back to share their mentorship story.
This is Talk Python to Me, episode 254, recorded February 14th, 2020.
Welcome to Talk Python to Me, a weekly podcast on Python, the language, the libraries, the ecosystem,
and the personalities. This is your host, Michael Kennedy. Follow me on Twitter where I'm at,
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 sponsored by Brilliant.org and Linode. Please
check out what they're offering during their segments. It really helps support the show.
Rusty and Doug, welcome back to Talk Python to Me.
Thanks, Michael. Glad to be here.
Good to be back.
Yeah, it's great to have you back. So, Rusty, you were on episode 194 previously about learning
and teaching Python in a vacuum. And back then, we talked about how you were in not super populated
part, a small town in Vermont, and you were working at elementary school, right?
Correct. Yep.
Yeah, yeah. Helping teach kids programming concepts and other things. And then, Doug,
we had you on back like 12 episodes before then.
I was teaching kindergarten directly and then basically just kind of made sure everybody else
could do whatever they needed to do with computers, whether it was teachers or students, and basically
just kind of all-around resource for people. We had another person that worked with the equipment.
I was the people person, the bridge between that kind of the technology and all the students
and teachers. And I also taught web design at a community college.
That's super cool. And Doug, you were on episode 182, Picture Python at Shutterfly, where you
talked about how you guys are using Python over at Shutterfly, which is a photo sharing, photo
book site, right?
Yes, correct. We use it quite a bit and doing more of that.
Super. You guys got a lot of API stuff going on there, I'm guessing.
Oh, yeah. A lot of rest calls and RabbitMQ stuff. And we're actually getting into AWS. So
that's an interesting twist for us.
Oh, yeah. That's going to be exciting. And I know you because you were on the show before,
but also I've read some of your articles on RealPython and you're writing a book. You're
doing a lot of things. You're keeping yourself busy for sure, right?
Thank you. I've been enjoying writing the articles for RealPython and that actually led to a book
proposal and actual book that I'm writing for Manning Publishing, which is fun and a little
nerve wracking. Yeah, that's for sure. What's the book title?
The Well-Grounded Python Developer. The proposal is, and I'm going to try to fulfill it, is that
there's a lot of beginner books and there's a lot of expert books and cookbooks, but not much stuff
that helps a beginning developer transition more towards an expert. So that's kind of what I'm
trying to do is convey how to help somebody who's got a basic tool set move into thinking about bigger
projects, the big picture stuff and think like a developer.
You know, that's a really big step, I think.
Yeah.
It's easy to go around and say, I want to learn language X. So I want to learn what a loop is,
what a variable is, how do I call a function? But then you go to actually create a program and you're
like, it's like deer in the headlights or, you know, writer's block or something. It's just like,
I don't really know how to put the pieces together. Right. And the advanced stuff is too hard.
Yeah. It's like knowing how to use a hammer, but he doesn't know how to build anything.
Yeah, exactly. Yeah. So I think that sounds like a cool project that you're working on. Great.
Yeah. It'll be fun.
Yeah. So at the beginning, Rusty, I think maybe it would be fun. You talked about a little bit
before we hit record about sort of the progress that you've made. So maybe give people a sense of
the challenges. You know, that was a really popular episode that you did with me way back when,
and I guess that's probably a year and a half ago. So it's, it's been a while, but so you've
made a lot of progress and I guess to sum it up, like one of your main challenges was you're in this
position where you need to have a fair amount of expertise in the software that you're working with.
And yet being in a small town, it's really hard to go to meetups or to find folks to collaborate
with. And if you're the only one at the place you work, well, that's also doesn't help, right?
Yeah. That was, I was actually learning with a colleague of mine who was kind of interested
in getting into Python a little bit. And so we were both learning at the same time and then he
promptly got another job with a different school district. So then I was, by myself again.
And, it was, you know, it's a lot more fun when you can bounce ideas off people and everything.
So I was getting started to get a little bit frustrated. I was starting to want to be able
to do more than I, than I could.
You know, what I think is interesting is everyone gets stuck when they're doing programming
or they're working on software projects. You know, I remember not long ago, some library
I was trying to use, I'm like, why does it not do the thing it's supposed to do? You know,
and I've been programming for like 20 years. Right. But still I'm, I'm sitting here pulling
my hair out because it seems like it says it's going to do X and it's not doing it for whatever
reason. Right. And the thing that I think somebody somewhere knows how to make it do that.
Exactly. But here's what I think is interesting is I think, you know, everyone gets stuck,
but they don't always get stuck in the same place. Right. I might get to a part and I'm
stuck here, but you've already figured that out, but you're stuck on something else. Right.
But if we could just talk to each other and go, Hey, I tried this and I'm, I'm stuck. Like,
you know, I did that. And it was, yeah, I remember that was hard, but now here, you can just like
help each other over these little hurdles much easier if you can interact with somebody.
Right. Stack overflows there, you know, when you have the time to, you know, craft a half
an hour question about, you know, two lines of code to make sure you don't get ridiculed or,
or whatever's going to happen if you don't, you know, freeze your question in the correct way and
show that you've, you know, tried all these other things. And, and yeah, so there, yes. Being able
to just ask somebody that, you know, is, is awesome.
These public spaces that you can go like stack overflow or Reddit or whatever, they can be kind
of rough, but let me tell you, I learned a program when it required a book when there was like
hardly even in the internet. And when you got stuck, it was like, you know what, let's go get
in the car and drive for 20 minutes and hope that there was a book at Barnes and Nobles or one of
these other weird places that kept all these trees and buildings in square form. And you would go there
and you would go through it. Like, so I guess the reason I put it out is like, it's kind of a love,
hate relationship. Like I can type an error into stack, into Google and likely a stack overflow thing
helps me nine out of 10 times. I don't have to ask the question. Right. But it can be rough to get out
there and ask questions like, didn't you read the manual or that's a stupid way to do it or whatever.
You're like, well, how about you just say a better way to do it would be this, because I only asked this
way because this is the best I got. Right. I'm trying to learn, like, take it easy on me.
Yeah. Lots of times in the early days, you don't have the vocabulary to explain what it is, or you don't
understand this concept that you want to go. Like for me, it was databases. Like I didn't even know how to get
started or how to, how to do things like that. So I had to like think through all of that. You can't
do that in a, in a forum really. Right. Right. It's too general. So yeah. So I guess long story short,
long question short, give us a quick update on what you've done. You've taken a couple of courses.
Obviously you found a great mentorship story, which we're going to dig into, but just give us the recap.
Yeah, it was great. So when we talked last time, I was doing a few things, processing, you know,
pictures and, and writing a few little apps that interacted with Google sheets. And then
I took a Java course, a Python course at an access course at the community college that I teach at,
because I was able to do them, you know, pretty much for free. And I only took access because the
SQL course kept getting canceled. So I figured that was the best I could do. And it worked out. I
understand, you know, I wasn't happy, but I did it. Yeah. And then, I got a call from Doug
afterwards, which we'll talk about after we talked last time, but, and after Doug and I connected,
I was able to build a flask app that was like asynchronous play for this board game that I was
interested in. It was basically just, it held your cards, you know, in between, but I built a
dashboard for users, put a database on it, notification emails when it was your turn.
I was really just kind of, I was spending like 25 hours a week on it at the time. Cause I was using
this thing called walk a time that talks to Adam and I think it works for a PyCharm as well.
Cool. So walk a times like time tracking, if you want to know how you're spending your time.
Yep. When you open up your editor, it keeps track what language you're using at the time.
Oh, interesting.
Yeah. And it was, it's really great with Adam. I couldn't get it to work very well with Python,
uh, with a PyCharm, but, I'm sure there's a way to make that happen. Yeah. So, I mean,
that was just really exciting to go from, I was a web guy before, but, to be able to make
an app that did all these things was just blew me away. And I had a blast that I, you know,
try and stop me from coding on the weekend, getting up at seven in the morning and working on it. It was a
good time.
It's such a cool experience when you're like, just, you wake up, you're like, I gotta, I gotta get back
to it. I really was. I'm not done. I still have these ideas. It's wonderful.
Yeah. It was, it was a lot of fun. It even made me want to put up with the question of like, can I
download this in the app store? You know, that's the first question I would show it to people. I'd be
so excited. Like, Oh, can I, no, it's, it's not an iOS app. It's, it's actually a web app and
it's in Python and nobody really cares. But anyway, I was pretty excited.
You just got to show them how to put like a little icon, like save a shortcut to the desktop.
Yeah. Their eyes just glaze over after you say no.
I hear you.
I started to, rebuild one of my first apps as well. Since then, try and do, you know,
build on what I had done before. And what was that experience like with, more experienced eyes?
It was wonderful. I was able to go back in and just make everything so much simpler to read. I
discovered, flask sessions, which just made a world of difference. Once I was able to put things
into a cookie then and persist it over pages was awesome because before I had,
I had to come up with this hack that I was doing it. I went from sending it as a hidden piece in a web
form. So every page had to be a form to figuring out how to do that. And yeah, it was, it was good.
It was really rewarding.
Nice. Well, it sounds like you're making really, really good progress there. And I now know about
walk a time, which is apparently a thing I'm going to have to dig into.
Check that out.
For sure. And Doug, how about you? What have you been up to?
You might not want to know.
I have another article coming out on real Python, which was insane to do with the book. And then,
uh, all of my free time, every spare second, that's not tied to work is involved in the book.
And then just work has been very busy. the fourth quarter for us is insane. So
it's been a very busy time. And then, right.
Yeah. So I've just been very busy with that stuff.
Yeah. This is like the big holiday rush. Everyone's going to get photo books for Christmas
or something like that, right?
Yeah. The fourth quarter is like a huge.
So Black Friday, that's like a, a legitimate thing that makes the business go for you guys,
right? Like gets you back in the black.
Yeah. They put us, they put, they, they try to put like the police tape around the entire system
so that we don't touch it after that. So it doesn't break. But at the same time,
it's constantly like wants new features.
Can't have it both ways, can you?
Yeah. I saw a really cool joke cartoon type of thing. And it just said the first rule
of programming is if it's not broke, don't touch it.
That's really an excellent optimization.
Yeah. I'm not sure if it's really good advice, but I certainly know the feeling and you know,
I know the feeling even more when it's software that I didn't originally write and I'm not especially
fond of or, or think it's like well written. Yeah. Yeah. It's like, if you touch that and break it,
it becomes yours. Like, no, no, it's fine. We don't need to, it's fine over there. It's just,
we're going to let it do its thing. If you want to touch it, you can fix it, but not at all.
Cool. All right. So let's jump into the main topic here, which I think is going to be a lot of fun.
So as I mentioned before, both of you have been on the show, episode 194 and 182. And I don't remember
which direction it went, but I know that one of you guys reached out to the other after you were both
on the show saying, Hey, it sounds like there might be some chance for us to work together or help each
other out. And you all started working together through that, right? Let's give us the story there.
I had listened to the episode that Rusty was on and I really liked, I really enjoyed it. And I thought,
you know, I thought to myself, there's a real opportunity not only to help, help out, but to
have him help me. I am teaching sometimes at this STEM place near me. And of course the writing,
the articles is sort of like teaching. And plus I had taught many years ago and realized how difficult
it is. And I was struggling at the STEM course with STEM place teaching kids. And I thought,
you know, Rusty could really be helpful. And I, I've been in that position as a self-taught programmer.
I learned myself all of the languages that I know. And so I've been subject to trying to figure things
out. And I've been at the hands of divas who didn't really want to help me as much as give me a hard
time. And I thought, you know, I could save Rusty some time and avoid that. I reached out to him
through you to see if he'd be interested in connecting. And, and he was, which was great.
That's really cool. And I'm pleasantly surprised to see that you all have gotten so much and made so
much progress and done so much collaboration. That's, that's great. And so Rusty, I guess it's
also maybe worth mentioning that you got a new position where you're actually doing more programming
and this, this aspect of life is actually even more relevant to you these days, right?
Yeah, it's, it was, it was really good that we had a new, with a change of kind of leadership
and our tech team in the school district that I'm at. And the new guy was not as technical as perhaps
the guy before him. So I got to help out with a lot of different reports that had to be filed and things,
which the average person would probably not find that exciting, but it was great. I got to,
you know, use some Python pandas to clean data and all the things I'd heard about basically listen to
your podcast. And I was like, why would somebody want to use a Jupyter notebook? And then,
you know, I figured out a reason why I might want to do that. Yeah, it was good. So now I'm the data
manager for my district. I left teaching. I still leave in the middle of the day from programming and
go and teach kindergarten. And then I will come back and finish off my day writing a SQL and,
and plugins for a power school and things. But so it's an interesting break.
No, they didn't have anybody to do it when I, when I took the job. So this year, so.
Oh, you're a voluntold. I understand.
Exactly. You can do this, but.
Here's a, you got to help out here. That sounds wonderful. You describe it. It's always like
these reports. A lot of people really wouldn't be that keen to do it or whatever. But I remember
my first programming job, it could have been almost anything they were having me do. I'm just like,
I'm sitting here at this computer. I was C++ at the time. Like I'm writing C++ code. They're paying
me. And I have this book and I get to learn it while they're paying me. Like this is heaven,
right? Like, I mean, it wasn't even that advanced to stuff. Right. But for me, it was like,
I'm in, I can't believe it. Like, how have they not found out I don't belong here? I'm going to
figure out this before they catch out onto it and get me out of here again.
Yeah. Where's security being escorting me out?
Exactly. Right. Exactly.
It's been really good. I've been really enjoying the kind of the blending of, you know, education and
programming at the same time. So I'm still involved in school and I've never had an adult job that
didn't involve school, you know, working at school. So it's been, it's been a great process.
This portion of Talk Python to Me is brought to you by Brilliant.org. Brilliant's mission is to help
people achieve their learning goals. So whether you're a student, a professional brushing up,
or learning cutting edge topics, or someone who just wants to understand the world better,
you should check out Brilliant. Set a goal to improve yourself a little bit every day. Brilliant
makes it easy with interactive explorations and a mobile app that you can use on the go.
If you're naturally curious, want to build your problem solving skills, or need to develop confidence
in your analytical abilities, then get Brilliant Premium to learn something new every day. Brilliant's
thought-provoking math, science, and computer science content helps guide you to mastery by taking
complex concepts and breaking them into bite-sized, understandable chunks. So get started at
talkpython.fm/brilliant, or just click the link in your show notes.
Do you feel that schools, elementary, middle, high school types level of schools are underserved from
like custom software or software that solves their problems?
That is a perfect question. Yes, because we don't have the money that industry has. So all the services
go towards people who can pay for it. And schools have to, we get this generic thing that can be bent to
our will, but have a lack of resources amount of people who can do it. You know, there's a district
down in, in Burlington. It's the big city in Vermont. And you know, there's a data team of six people.
You know, they, they hired a data scientist and stuff. And, and in my school district on the,
on the edge of civilization, we have me and I've been there for eight months, you know?
You're on the outpost way out there.
That's right.
Yeah.
Yeah. That's an interesting point because if I go to any major fortune 500 company or pretty much any
startup, almost any startup or, you know, even middle-sized companies, right? They all have a
software IT group, right? Right.
Maybe it's only five people and they're not super advanced, but there's a team of people who write
software to make that place run. Like the place I was telling you about where I was doing the C++
stuff. That was like six people, you know, and they still had somebody hired to work there as a
developer and build software. So I just feel like there's probably a lot of opportunity to give a
little bit of programming skill to folks at the non-college, non-university level schools to empower
them to do, do more.
I agree. You always say that, you know, Python is maybe your superpower at work and it's very much true
where we're at. You know, there's very few people have the time to slow down and write
code like I do at the moment. A lot of people that have my job around the state, it's been added on.
Oh yeah, you're going to do this data portion as well as whatever. And I'm in the pretty unique
position where I was hired to do that. So it's, it's been, it's been great.
That's cool. And you want to, right? You're not voluntold.
Exactly. I asked.
Nice. And Doug, you had mentioned that you're a self-taught developer. Like I am mostly, I took,
I needed a couple of credits at the university for a minor in computer science and other types
of stuff. But for the most part, I'm pretty much self-taught. So I'm pretty sympathetic about
those sorts of challenges and whatnot, but maybe just give us the quick story of, of that for you.
Cause I'm sure that'll resonate.
I graduated with a BS in physics, which I tell the joke all the time with a BS in physics,
I'm completely qualified to get coffee for the other physicists.
But by the senior year, I did a project where we built a very primitive cat scanner, which was a
computer controlled cat scanner. And I got hooked. I bought a Radio Shack color computer,
taught myself a basic and a little bit of assembler. And that was enough to get my first
job as an engineer after college, doing process control. And I was off and running doing
programming and I worked in Fortran and Pascal and CC++ PHP and then now Python and
JavaScript quite a bit.
Yeah. You've seen a lot of them. That's, that's super cool.
Yeah.
Yeah. So that, that starts when there are books before the internet, before Stack Overflow, right?
Oh, this was, this starts before that, before books, this was like BBSs.
So BBSs, that's like the internet that you go to. That's really slow and it makes sound and only
one person can be on at a time, right?
Yeah. My education was continually slowed down by getting phone calls from friends.
Yes.
I remember that. We actually had two phone lines at my house just so my brothers and I could
all be on either internet dial up or on BBSs at the same time. And it was still a problem,
right?
Yeah.
We'd have like call waiting come in and knock us off and oh my God. All right. So fun,
fun time. So tell me about what you guys have worked on, especially in the beginning, I guess,
Rusty, go ahead and maybe start this conversation now. Like, so Doug reached out to you and you're
like, wait, this guy, just this random guy on the internet. That's really, yeah, that's really
knowledgeable, wants to help me out. Like, what is this? And so where did you start? And like,
what was that like when you got that message?
I'd said earlier that, well, I didn't say on the podcast, but it was great because Doug
wanted to exchange kind of some teaching knowledge with Python knowledge. And I said that I basically
won the lottery and got somebody who knew exactly what I wanted. And Doug lost out because he's
already a good teacher, but I still needed lots of help. So I just started asking questions. I wanted
to go further with Flask and started to build that, you know, database app, the kind of asynchronous
kind of card playing app. And I had no experience with, with databases or not. So he kind of showed
me a, luckily he was writing an article on something very similar and kind of talked me through starting
to use SQLAlchemy. And it just kind of got started. And I asked him questions about database design and
I would, I would craft emails. And then, you know, there's a, we had about one or two day delay just
because we're both busy people and that's how we kind of started. And then I started to ask more and
more questions and it helped a lot that we had a lot of common ground. We're both cyclists. We both
enjoyed Python and teaching. So there was a lot of, you know, banter. And I, I tend to try and ask a lot
of personal questions when I'm working with people as well, just to kind of get to know them better.
So started to build my app and, and I was able to go, you know, and say, Hey, I'm having problems with
this. I didn't have to explain everything from the beginning or, yeah, it was just a really
wonderful experience for me to be able to, just have get stuck and, you know, within a day,
be completely unstuck and probably looking at a different feature.
Yeah. That's really interesting. You know, like those types of assistance or whatever,
when you're new, you can be stuck on something for like five hours and you're like this,
I just don't know. I just tried everything. And somebody who's gone through it a few times,
like, Oh yeah, that's confusing. But when I figured it out, it was X. Right. And then,
so there's a lot of effort and that's potentially for like staying in touch and coordinating, but
sometimes you can just look at something, Oh, that's really easy. And it's, it's just such a
service to you. Right. To just be able to receive that and go, Oh my gosh. Right. I so appreciate it.
Whereas like the person who do it, like, it's okay. Well, I just called it out of my memory. Right. I kind
of know. Right. Yeah. I put everything on GitHub. I was starting to get a big into GitHub,
as much. I'm still afraid that I'm not going to be able to recover what, you know,
two or three versions back. And so I don't have that much faith in it, but it was good to be able
to have everything there. So you've moved on past the, I've made some progress on this project.
Let me zip up the directory and give it like a version.
Doug, you're laughing. Have you seen that as well?
I knew GitHub was great before I knew how to use it. Yeah. So we were able to do that. And then I
could just say, Hey, you know, I've, I've done the update and Doug could pull it down on his end and,
and run it and see what the error was or whatever it might be that way. So that was pretty cool.
I always made sure that before I asked a question, I wasn't going to waste his time that I had
exhausted everything. So it wasn't a flippant. Oh, I'm stuck for five minutes. Go and do this. It was,
you know, I'm really stuck here. So now I'm going to have to ask. Yeah. Yeah. And I, you know,
I have some folks who periodically ask me questions, whatever. And when it's like that, I totally don't
mind. It's fine. Right. The thing is, you know, sometimes you have people are just like, well,
this isn't working. Why? And, you know, it's pretty obvious that like a little bit of take the
error message, put it in Google would come up with a really good answer. you know, it's one of those
types of things. And yeah, so that's really, I think an important part of trying to make something
like this work is if you're going to work with Doug and ask him questions and, you know, basically
take some of his extra time and energy, cause he's got so much when he's not working on his book or his
book articles or all the other stuff he's doing that it's really like, you know, that someone's put a
lot of effort into it because then it's like, okay, well they really tried and they're really stuck and
I can probably help them as opposed to just this person didn't even Google it. Like I really don't want to,
you know, it really was a lot more. Yeah. Sometimes people will shoot me a message and I'll
ask, could you help me with this? I'm really, it's like clearly not like from one of my courses or
from an episode. It's just like random Python question. I'll take the question, put it in Google,
grab the link one and shoot it back and go, how about this? Oh my gosh, that totally fixed it.
That's an incredible skill.
Yeah.
You need to let me Google that for you as a site.
I know. Is it still a, is that still a thing?
Yeah. It was mostly concepts that when I would get to, to ask, you know, that's, I needed to know
how to go about something. And I had to be careful because Doug would actually just write me the
program and send it back. And I would be like, oh my God, how long did this take? And it was like a
complete, you know, Ajax program that updated your database for you. It wasn't exactly what I was doing.
So I would still have to create my own, but it was a working example of here. This is what it might
look like that I could go into it and dissect it. I would have to be like, okay, I'm at work right
now. I'm going to need three hours at home to like, look through all this that he's just sent me. And so
it was pretty good that way.
That's awesome.
For me, that was the key with Russell was that he would always ask me, you know, I could see that he
had looked for stuff and well-researched and intelligent questions, which was great for me because I,
you know, I don't have a lot of time to spend, but the other thing was,
I often didn't give him complete solutions. I would do the left as an exercise for the reader
kind of thing where I would give him a sample that I knew that he could extend and extrapolate
from in order to solve the bigger problems he was facing.
Right. Like here's a really, really simple proof of concept of like some Ajax thing or something,
right?
Yeah. Some of the things were just conceptual Python stuff, like, you know, moving away from
everything as a dictionary. Dictionaries are extraordinarily powerful.
but to get into object oriented stuff, it's kind of a hurdle, but it has a really great
use. And I knew that I wanted to take him, you know, from, from dictionaries to object oriented
and then onto SQLAlchemy, which of course is dependent on objects to get into databases.
Yeah, absolutely. I think SQLAlchemy is really special and ORMs in general. I think they're very special because I remember when I was learning to talk to databases and you had to write SQL embedded in strings, embedded in your programming language. You're like, I just want to like get some data. Why do I have to learn a whole new programming language for this? And then, you know, you got to go and put stuff back in the database and like, how do you get the right types? And then obviously you can't string.
concatenate it. You got to figure out how to use parameters. There's just, there's all those layers of either best practices or just understanding or, you know, lazy loading or whatever. And with SQLAlchemy, you can kind of learn a skill that is also applicable in general Python, this object story. And databases are easy again. It's wonderful.
Yeah. I mean, I've been in, had both feet in the object oriented camp since C++, you know, 20 years ago. And I didn't really want to have to deal with tables of raw data from SQL. I wanted things to come to me in an object form because I want to think in terms of objects.
Yeah. I mean, usually a real common pattern, if you weren't using an ORM would be to do a query and then load up an object with the data that you caught back and then give that back, give that over. Right. It's like, well, why am I doing this?
Like from an object and once coming in and then trying to update the database and make, Oh, this is fun.
Yeah, exactly. Couldn't we let a framework do this? Which, which is really nice. And it creates the tables for you and all that. So I guess I'll throw this out to either of you. I don't know which one wants to take it, but Rusty, you spoke about using Git and source control and how that was a little bit mysterious. Like you knew it would be good for you and you knew you should do it, but it was kind of something you didn't really know. So it was just another layer of something you have to deal with while you're trying to learn all these things. And finally you got there. So that worked out as a super way for collaborating, right?
Yeah, it was fantastic. I was using it really to go from my work computer to my home computer. You know, if I had 10 minutes at work for lunch or 20 minutes, I would go ahead and, you know, it'd work on my program and then sync it, upload it and then get home and then pop it, keep going. So that was pretty cool that I could switch between computers. That was kind of my initial impetus for using it. And then when Doug actually asked to be a contributor one time, so he could do a pull request. Then I had to like do like two hours worth of research when that came back to figure out how to merge and things like that.
I think I did it right because it worked afterwards, but
Oh my gosh, there's a merge conflict.
What are we going to do?
Yeah. So that took some time, but you know, we, I figured that out and I use GitHub for all my, my projects now just to kind of keep it there. But yeah, that was a part of the learning curve as well. It was really cool. I was still the only time I've ever collaborated with someone on GitHub. I've, I'm actually to the point now where I'm, I'm asking questions of a plugin, not plugin, package authors on GitHub as well, which has been pretty cool.
It's a really nice place to be able to go and have a conversation as well. Right. We've had source control for a long time, but the fact that it's got this kind of social component to it is really cool.
Yeah. Yeah.
For me, it was great because, you know, Rusty and I had used a couple of ways to collaborate email, of course, and then we had done some screen captures and then screen capture movies and Skyping. And, some of that, you know, that was useful to me, but sometimes I was like, what is he talking about?
I need to see this thing because I needed the context of, what it was running. And so having access to the whole code base through GitHub was really helpful for me for that context. And you know what the goal was that he was trying to achieve.
Absolutely. I've certainly had people send me videos of like, here's what I'm trying to do this part. I'm stuck on, but when I click this, here's what's happens. And you know, that is actually really better than just a random email trying to describe it.
But it's not necessarily as good as being able to just poke around yourself.
Yeah.
I'll make a video in, you know, in 30 seconds that would take me, you know, 20 minutes to type. So I'm definitely much more and I'm more comfortable in front of the camera and I've been using it in teaching for a long time to, to make videos. So that was probably the most common way I would send issues. I would say.
That was great for me too, because I could think at length and, you know, I sort of could type my way to an answer within code instead of keeping rusty on the phone or trying to send another video back and forth. Cause some of those concepts are kind of abstract, like, you know, OO and things like that are a little abstract to try to talk about.
Yeah, definitely. A good written example is nice there. You know, I've used that screen recording trick for bug reports, you know, for like random software. Like, I know you say this is not a problem, but here I've recorded it.
This button that says do X, it doesn't do X anymore. Can you just help me out here? And that's pretty effective as well, but it's not so much of a mentorship, I have a relationship as well. Now, one of your philosophies, Rusty, is that you're not keen to use code that you don't understand outside of say pip install a thing and just leverage that directly. So how'd that play into this whole interaction?
Like I say, unless it's a package, I'm really not that comfortable. Like if, you know, if somebody were to give me, here's a bunch of code that does exactly what you want. Now I wasn't doing this for a job at the time. These were personal projects that I was trying to learn. And I really feel like if that happens and I try and debug it, I, and I don't understand what's going on. It's going to be really, really tough for me to use that in any kind of a meaningful way. And that's one of the things that Doug helped me understand was actually, I listened to his interview on your show.
And he was saying that he doesn't understand why people don't use an editor that has a debugger in it. And now I wouldn't now, you know, if I was going to write something because it's just that important. And I didn't really understand how important it was being able to look inside the variables would be.
So I just really want to understand it at its base level because I just feel it's going to be so much better going forward. So yeah, there's even some packages I wouldn't use that took over my Flask app in a way like the Flask users package is just this huge invasive thing. And I didn't really understand what I wanted to do. If I was building something that I was just going to build it for a month and then leave it or whatever, I might use it.
But otherwise, I'd rather understand that whole process so I could use it later on or use that knowledge later on.
Yeah, I totally agree. And that Flask example is pretty interesting because I feel the same way.
Right. Like I put together a course on Flask and it doesn't have any of the extensions, right? It doesn't use Flask login or any of that stuff because I just want to talk about the primary thing and every one of those layers.
While it saves you a few lines here, it adds layers of complexity and understanding along the way. If people want to go grab that later, that's fine, right? They can go use that. But sometimes you just want to just like, what is the essence of what I'm doing? Right?
Yeah. What do you think? How's your philosophy around this, Doug?
I do like to use packages, mostly because I work particularly. I just don't have the time to build everything myself. But I spend a lot of time vetting stuff that I want to use.
For instance, we write a lot of REST APIs and I looked around a lot to find a tool that I thought worked for me, which is why I use this thing called connection rather than some of the Flask RESTful stuff.
Because it just fit my style of work. It seems well supported. It has current updates and all that stuff. There are things that I do want to build myself because I have to have that much control. It depends on how much my OCD kicks in.
If I build it myself or use a package.
Yeah, I think there's just so many trade-offs. And it's interesting to talk about because it's like, what's the right action? What's the right choice? You know, for example, like just take like Flask login or authentication or Flask users as an idea.
On one hand, it's great to let that whole thing be someone else's problem. But as soon as it doesn't do what you need and you're like outside of its box, then all of a sudden you're jumping through all these hoops to try to understand how to juggle it plus what you're doing and so on. Right. And so it's just attention. I think people just got to get used to.
When you download a good package like Flask users, it's great that a lot of that works for you with some hidden complexity. It's like a black box. But when you have to open the black box and try to do something with it, that can be a bit of a hassle.
This portion of Talk Python to Me is brought to you by Linode. Whether you're working on a personal project or managing your enterprise's infrastructure, Linode has the pricing, support, and scale that you need to take your project to the next level.
With 11 data centers worldwide, including their newest data center in Sydney, Australia, enterprise-grade hardware, S3-compatible storage, and the next-generation network, Linode delivers the performance that you expect at a price that you don't.
Get started on Linode today with a $20 credit and you get access to native SSD storage, a 40-gigabit network, industry-leading processors, their revamped cloud manager at cloud.linode.com, root access to your server, along with their newest API and a Python CLS.
Python CLI. Just visit talkpython.fm/Linode when creating a new Linode account, and you'll automatically get $20 credit for your next project.
Oh, and one last thing. They're hiring. Go to linode.com slash careers to find out more. Let them know that we sent you.
One of the things I think could be helpful from a mentor-mentee relationship is when you're new in writing code, and I kind of touched on this a little bit earlier, Rusty, when I asked you the question about going back to your other project, is a lot of times beginners, when they're working on something, they're like, if I can just get this to work, that's it.
It's working now, right? But then there's the, oh, this is not very Pythonic, or did you know that Python has this language feature that makes those five lines be one, and it's real simple?
Or even there's a standard library thing, like, why are you sorting this by hand? You know what I mean? Things like that.
So maybe talk a little bit about, kind of helped him make his code more Pythonic, or make it a little more professional, or whatever.
Well, I guess one of the early things that I did, or I tried to do, is when we first started to work together on the Flask app that Rusty put together, I recall it being a single file. It was a single Python file.
And for me, I got, you know, I looked at that, and I said, oh, this is, it's hard for me to keep all of what's happened, this giant file, in my mental model all at once.
The cognitive load on me was just too much.
One of the things I did, and I think in one of the pull requests, was to introduce the idea of modules, and how to break code up into logical modules, where, you know, this kind of stuff should live here, this kind of stuff should live here, because you could think about, that sort of separates the work, or what you're doing, into a domain, a little domain, where that's all it really does.
And you can sort of depend upon that. It makes the amount of stuff you have to keep in your brain a little bit smaller and more manageable.
And then, you know, the idea of how to, creating your own modules, how to import your own modules, rather than just the system modules.
I think for me, that was a big step that we took forward into making the work that Rusty was doing more along the lines of a developer, rather than just a programmer.
Yeah, yeah, I certainly agree with that.
It was great. Blueprints was a big part of that.
Blueprints are interesting.
These are things in Flask.
You know, Flask, through, I don't know if I would put this on the people who were, like, writing the early tutorials for Flask, or just other people who are passionate about Flask and written tutorials.
But whatever the origin is, it feels like Flask a lot of times gets sold as, like, Flask is amazing.
It's so simple, you just need this one file.
Just put your stuff there.
Go.
You know what I mean?
You can do that.
For the really simple example, it's fine.
Yeah.
When your website has 300 views.
For the whole world on a browser, that's fine.
Yeah.
You have 300 views and 10 database classes.
And yeah, it's crazy.
What nobody could get through to me until Doug and I worked together was why you'd want Blueprints.
You know, while we got to a point where, like, you needed to break it up into these different pieces.
And he must have shown me Blueprints two or three times before it finally clicked with me.
Because I'd watched YouTube videos of the Flask site itself, or the docs.
Yeah.
Assumes you already know exactly why you'd want to do them.
And yeah.
So I just didn't understand why I'd want to start to break it up.
I mean, one of the great things about Python is that it's supposed to be written clearly instead of cleverly, I suppose.
You know, overly clever, I should say, rather.
So Blueprints allowed you to kind of break that up, just like you would break up, you know, a function into smaller pieces, which was awesome.
But yeah, it took a long time.
And then even then, it's not super well documented.
So watching somebody, a pro who had done it before was instrumental.
And it really, really opened my eyes to why you'd want to do that.
But it took a lot.
Yeah, yeah.
It's definitely one of those things.
It's hard to sell.
Like, why do I need this?
Because a lot of times when you're getting started, you have three views.
You're like, you're just making it complicated.
Like, why are you putting all this stuff everywhere else?
But when you have 300, all of a sudden, you know, having those categorized, like, here's the stuff about users.
Here's the admin stuff.
Here's the, I don't know, the blog stuff, whatever you're writing, right?
Like, it's massive.
And it's kind of like you said, Doug.
I think one of the things that's really important for people to, as they're getting into programming to learn, is that you can think at different levels of building blocks, right?
You can think, you talked about this with modules as well.
Like, you can think of line by line what's happening.
Or you can think of function by function.
But if you use modules, you can sort of think, okay, that's the thing that I use for working with sending email.
And I go to it and I say, send email, send debug message, send error.
And that's, I don't care what, how that happens.
I just ask it to do those three things.
And so now you're just thinking at the, here's my email building blocks for the rest of my app.
And so there's like these different conceptual layers that you go.
And I think that's kind of being productive is really about identifying the right level and thinking of those Lego pieces, right?
Oh, yeah.
I mean, you know, that whole, why would I want to do this?
You know, you start out simple and you think, oh, this is, you know, I can get something running pretty quickly.
And then it starts to get more and more complex.
And why would I want to do this?
It's like, from my point of view, it's like, well, you know, you're already running into name conflicts with functions because you've got so many of them in one module.
And you're crossing over where you're sending email in 10 different places.
And it's hard to, it's hard to think about, you know, all those things that are going on there.
If you put it in a module or the namespace and even, you know, what a namespace is, is so useful.
And what Rusty said about that, we were over this a few times, part of the benefit for me, besides just enjoying helping him, was for me to find the right way to phrase it.
You know, how do I convey this information that would help him hit?
Because it's not like I gave him perfect examples and he took off of it.
What I was doing was trying to find a way to show him an example or say it in a way where Rusty arrived at that aha moment all by himself.
And suddenly realized, oh, this is why I want to do that.
And then he would pursue it because it's not just because I told him to, it's because he suddenly saw the value of it.
I think half the time he spent just stripping out my imports and everything imported in every single file.
And that's one of the things I learned as well.
Just in case you need it.
I guess it's worth really quickly, just for folks who are out there who are using Flask, but they're like, wait, Flask Blueprints?
Is this like an extra package or something?
Flask Blueprints are awesome and I massively encourage people to use them.
But Doug, maybe give us the quick elevator pitch on what those are.
For me, Blueprints is a way to segregate functionality in the Flask app.
So if you have a lot of URL endpoints, some of those are going to be related together like logins or these are the endpoints that I need to feed a page or provide a view.
And you can have, you know, you have in a basic Flask app, you have one templates folder.
And in that templates folder, you might have JavaScript and CSS and HTML.
But as you get more pages in an app, that starts to pile up and you start coming in with these weird names and stuff like that.
And then across, they don't really logically go together.
So Blueprints is a way to separate the URL endpoints, the API, I guess, into modules which exist in separate files.
And now you have all of these modules that contain that functionality, which they have their own template files, their own static files, you know, all those other things that make up the functionality of that page.
I usually try to break it up by page because that's always complex enough for me.
You have all the functionality of that page in one place, which is super handy because you can think about it in one place to the other.
And nothing else in there, right?
And nothing else.
The other great thing, I haven't done this too much, but the other great thing is you can actually take that module, that Blueprint module, and use it in a separate app just by picking up that, you know, copying that directory or that folder, the project, what do they call it, a package, to another Flask app.
And it would work.
In my project, I had the main part where you actually played your cards or whatever.
And then I just made another Blueprint.
That was the member section.
So then you'd check in, it'd pick up your deck, and then it'd shoot you over to that other module.
And then there was a little point where it said, oh, if you're logged in, go back to here.
Then you'd have to wait.
And then when I wanted to build an admin section, that was a whole other Blueprint.
Boom.
Then I could work on that completely separate.
Yeah.
And so it's beautiful.
So the reason I think it's less obvious in Flask and also, but still important, is Flask normally has you go app.route on all the view methods.
And the place you create that route is in the main thing.
So it's hard to share it to other files, which then have to be pre-imported.
And it creates like this circular nightmare that you run into.
And so it gets challenging.
So people should, if they're not using them, they should definitely check into Blueprints.
I use this idea even more extreme than that, maybe.
So I've got separate modules for my related view methods, like say stuff about admin.
And then there's functions in there that handle the views.
And then I have my templates organized that way as well.
So my template folders has maybe an admin subfolder.
And then the names of the template files are the names of the functions.
So there's like this kind of hierarchy of, I'm here, I know exactly where to go.
There's not 500 templates in one file.
And I also use this idea of view models, which is like classes that exchange and validate the data between the HTML request and the rest of your site.
So like this data comes from the URL, this data comes from the form, this data comes from a header.
Let's validate that and pass it on.
And those also have the same structure, right?
They're view models and then the module name and then the name that's associated.
So I really love this idea of organizing it.
It just, it means like almost no matter how complex your project grows, you just follow.
It's like a little tree traversal and you found what you need on all the different layers.
I love it.
I think that's a really valuable part of Blueprints.
I think one of the things you're alluding to, one of the more difficult parts of using Blueprints as a, not being familiar with it, is that idea of the app, the app instance and how to, how to share that in the other, the other modules in the Blueprints.
Still working on that one.
Yeah.
Cause you, you created in the, in the main Flask app and then how do you access it elsewhere?
That's, that's hard.
I tried and said, I couldn't.
My dog crashed.
It won't let me.
You start breaking up your code like this.
You need to do it before you understand why you reach a point past where you should have done it.
And then you start to understand that maybe I needed to start doing that.
So having somebody there to kind of help you along with that process was, it's pretty key.
Yeah.
To kind of precipitate it and get it started.
That's for sure.
So what are some of the other tools you talked about using GitHub?
You talked about recording, like sharing screen recordings.
What are some of the other communication tooling that you used?
Well, we just talked on the phone.
Yep.
It was harder to set up cause we're both busy folks.
It's harder.
It was harder to get the actual conversations, but it was great.
So I would say every couple of weeks we'd chat on the phone and then we actually set up a video conference once as well, which was good.
That was, that took a lot of doing to make sure we were both at a place.
Cause you know, you can't do that necessarily quickly at work or whatever.
Yeah.
That can be challenging.
It's also fortunate that the Rusty and I are both on the East coast.
So there's no time zone issue for that video conferencing or trying to share a Skype call or something.
Yeah.
I do think that the tooling is around to make this much more possible for distributed folks.
It's not like, well, I've got to find somebody in my town to help, which that may be great.
Right.
It may be great to find someone locally.
Cause then you could just, Hey, every Wednesday, let's get lunch together and I'll bring our laptops or something like that.
But you know, that limits the options of who you can work with pretty dramatically.
If you restrict it to your town versus the world.
Well, one of the other things that I tried to do, which I think is important for me as a mentor is that I try to be responsive to Rusty, that he sends me a question or he's updated his, the Git repository and asked me something about it.
Is that I try to look at it pretty quickly because one, I want to help him.
But two, I don't want to fall behind where he's, he's moved on because he hasn't heard from me.
And, you know, suddenly my assistance is irrelevant.
Right.
You've already gone so far to help him out.
You gotta, gotta keep going.
Doug, how did you work with the, I guess there's probably this tension around, am I just doing the work for him versus teaching him, you know, give him a fish versus teaching him to fish?
Yeah.
Well, I think about that a lot because I teach at a STEM place where, with kids, you know, that range from age from eight to 16 and, they'd be happy to have me give them all the fish I have rather than figure it out themselves.
So I'm onto that trick.
Not that Rusty does that, but, oftentimes I guess one of the, I guess I do two things.
I don't try to solve the entire problem for me and I'll give him a working example, but it's really a prototype that he's going to have to extrapolate from in order to do everything that he intends to do.
And then the other thing I try to do is I really try to listen more than talk because I've found, I'm sure both of you have seen this, over time, over time.
Listening more gives the person a chance to put their thoughts into words in a way that they're trying to explain it to them.
They just keep nodding.
Some, but quite often they come to the solution themselves by the act of expressing it.
Yeah.
You've kind of shaken up their thought patterns and got them to focus from a different perspective, right?
To try to verbalize it and whatnot.
Yeah.
Silence is powerful.
Yeah.
Plus I know that, you know, I can tend to ramble on and on myself.
So I want to give, I want to give him an opportunity to tell me what he's really trying to do.
Well, that was a great story you told me, Doug, but that's not what I was asking.
That's a real possibility.
Yeah.
Well, for me too.
So this sounds like this has been working out really well for you guys.
And certainly I think it's great, Rusty, that you've got this job where it sounds just looking in from the outside.
It sounds to me like you've leveled up a little bit in terms of what you're doing with Python and with code and the impact that you're able to have doing more analysis of what's going on and so on.
And I'm sure this, this hasn't hurt that process at all.
So it sounds like it's going really well.
And I guess maybe the last thing I'd like to explore while we're together is just, you know, how do we help other people make these connections and help each other out and, you know, get, get benefits on both sides.
It's a tough one.
And I think before I actually connected with you to talk about, you know, kind of learning Python by myself, I'd gone to a couple of meetups in Burlington.
And, you know, for me, it's an hour drive down there, an hour drive home and, and stuff.
And I ended up there and everybody there is like working at a startup and, you know, is, is pretty savvy.
And we had this like presentation.
We're doing this with Dockers.
And here's the thing about Kubernetes cluster.
You're like, what is a loop?
It was a lot of people who knew each other, you know, from different projects and stuff, you know, it was kind of a, an old boys club kind of thing or young boys club, I guess.
And I, we had a presentation one night when I was there, there's a bunch of different organizations came out and said what they were doing with code in the area.
And I would actually, I was thinking to myself, well, I'm just going to, next time there's one of these things, I'm going to show up with a slideshow and say, Hey, I want to try and bring, you know, coding to Franklin County as a teacher.
And if I could have a mentor, I think I could get to the point where I could do that kind of thing.
So I was not necessarily that desperate, but I was like, that was like my next big plan because I didn't really have anything else up my sleeve, you know, to try and make connections as far as that goes.
It is tricky.
I do think these meetups are very valuable.
People are pretty humble or they're not really, you know, they, even though I'm sure people are doing stuff that sounds intimidating.
I don't find very many people are condescending, I guess is what I was looking for is like, they're pretty welcoming of newcomers, especially in the Python meetups.
And so I do think coming out to these are, you can really make some good connections at them.
Yep.
This was a general, like, I don't think there is, there is a Python group there, but it never has a meetup.
So it was just kind of a general code.
But it was a, you know, it was a comfortable atmosphere, but I wasn't necessarily going to walk out, you know, with the kind of connections that I was looking for.
I don't know.
I think I just kind of got lucky to get connected with Doug.
So yeah, I don't know that I have any help.
Yeah.
It's funny how life takes these turns, right?
Yeah.
Doug, what do you think about finding mentors?
Well, I think for me is, it's interesting.
You know, I approached, I approached Rusty because there were some things that I wanted to help him with, but there's also some things I wanted to help me with.
And so it's kind of a two way street about the mentoring.
But I think part of it is just asking someone to do so is probably a big thing.
I go to a Python meetup in Hartford, Connecticut, and I've given presentations there and I've met a lot of people.
And some people, you know, have gotten in touch with me afterwards and, you know, enjoyed the presentation or whatever.
But very few of them have asked me for help.
And at the meetup, it was clear to me that they were really looking for help.
And I thought, just ask me, you know, why not?
Yeah.
Just, you know, the worst that could happen if somebody says no.
I don't know how prevalent this is.
And I honestly haven't been to it here in Portland, but at least in Portland, one of the Python meetups here has like a weekly, I'm sorry, not weekly, a monthly project night or something.
Where you just come with whatever project you're working on and you could just talk to other people.
And either they have a project or they're just there to give advice or whatever.
And that seems like a really great thing to set up if it doesn't exist near you.
I suggested that to the guy who runs the Hartford meetup that I've gone to.
You know, they usually have two presentations a night and then he's had hackathon kind of things.
But they're sort of free form.
And I suggested to him that they might do exactly what you suggested is a tutorial night where people, somebody comes and they focus on a thing.
And they work on that thing to try to kind of like a class, I guess.
Yeah.
Like we'll do a hands-on workshop on SQLAlchemy or something like that.
Yeah, exactly.
Yeah.
You know, another thing I'll throw out there, it doesn't work for super, super beginner, but it does work, I think, for even intermediate, like advanced beginner, I guess I would call it, is one of the things that really changed the interaction and trajectory for me was when I started doing presentations at my local meetup.
Yeah.
And at CodeCamps.
Because other people who were really bright and really experienced, like, oh, that was really interesting.
I didn't know that thing, but they knew other stuff that I definitely needed help with, right?
And so I had dove into some small area and wanted to present on it.
And that got me sort of connections, not exactly like a mentorship, but like a peer group that I could then start talking to them about these other things that I needed.
And that actually really made a huge difference.
And I know a lot of these meetups, they're looking for people to present.
And you don't have to be an expert in everything.
If you just know one thing you can spend 15 minutes on, there's a good chance you could talk about it and get connections you would otherwise wouldn't.
Oh, absolutely.
I mean, I got started writing articles to publish because I was doing presentations at works at our various engineering all hands at work.
And people responded well to these presentations about various things in Python.
And I got the idea to turn them into some articles.
And I've been working with Dan Bader at RealPython.
And they've been very popular.
So that's what got me into that.
I think the short form, I think, is probably the key there to getting people up to present.
If you only had 10 minutes or 15 minutes to say something, that's a lot less intimidating than if you were going to give a half hour, 45-minute presentation and then take questions.
If you could, you know, everybody stand up and do like a lightning, you know, here's 10 or 15 minutes.
A lightning talk, yeah.
Yeah, absolutely.
I think that would be huge.
I don't know.
I guess part of it is, look, if you're looking for a mentor, you've got to take a few steps to get out there, right?
Certainly sitting behind your computer at home and not talking to anyone is not going to get anyone to help you because they don't even know that you're out there.
But also, you know, it's also a bit of a give and take, right?
Like you said, you both helped each other with various things and whatnot.
I guess the one other thing to maybe mention is there are people who help with speaking in the Python space.
Like if you apply to PyCon, you can get a mentor that will help you craft your application and craft your presentation.
Basically, whatever it is you're going to present, they'll give you feedback and advice on that.
I guess the danger is that they accept it.
Yeah, then you're committed.
Oh, we've chosen you for the keynote.
Oh, super.
Oh, my God.
This is going to make me sweat.
But yeah, it's still, I think, I do think there's ways out there.
I mean, obviously, there's communities.
You can join like different Slack communities and whatnot.
There's codementor.io.
Never use them.
Not a recommendation or endorsement.
I just know they're out there and you can.
I think it might even be a paid relationship.
But if you're like, I really need somebody to help me with this project.
And if I spent a month or two, maybe, you know, with one-on-one help, it might help.
So, you know, that's another thing that you could do.
I don't know if anyone has experience with that.
Yeah.
I went to, this is a long time ago now, but I went to Toastmasters near me for a while
to help with public speaking, which is not necessarily, it's certainly not code oriented,
but it helped me a lot to improve my public speaking.
I wish a lot of people who I work with would go.
Sure.
Well, I hear you.
And I was going to say that one of the really important things that you can learn that is
not taught in any sort of computer programming background is this public speaking, putting
yourself out there.
Yeah.
It really makes a big difference on a lot of different levels.
And so, whether it's Toastmasters or it's more like organic, hey, I started giving talks
at my local meetup and then at, you know, small local PyCons or whatever, like I highly encourage
it.
It's a rare skill.
And if you have it, it'll put you in a different place.
Oh, I really think it helps your career to be able to do that.
I've been telling my own kids that for a long time, dealing with kids, you know, in public
schools and things like that, that if they can just communicate and get their information
out there and they don't mind putting themselves out there a little bit, that's going to be,
that's going to be like Python.
It's going to be like your superpower at work.
You can actually communicate it because, you know, these kids have their heads in their phones
and, you know, I'm not saying that's horrible, but there's not a lot of my own children are
scared to call people on the phone.
You know, it's.
Yeah.
I know like my daughters are not huge fans of talking on the phone either.
Yeah.
I think they mostly hate the numbering system dial 472 for this system or whatever.
Right.
So I understand it.
Like they don't want to wait there for 20 minutes, but yeah, I do think that this is a
skill that is going to be more special, not less.
It's not like everyone's now a good speaker.
When I was a kid, no one was, but now everyone's so good at public.
Like, no, that's not true.
Right.
It's certainly not.
So I think it's really a great thing as well.
I mean, it's not directly related to being a mentor in a technical space, but I do think
having that, you know, I think it helps you with other places.
Like I talked about like presenting the meetups and whatnot.
Sure.
Yeah.
Which gives you an opportunity to meet other people who you could either ask to be a mentor
or be a mentor to.
Yeah, absolutely.
Yeah.
That's very cool.
All right.
Well, you guys, this is a really interesting story and I appreciate you coming on here to
share it.
Glad to.
Excellent.
Yeah.
And Doug, I do want to ask you really quickly before we move on to the last two questions.
Just really quick.
You talked about your book.
When's it going to be out?
Well, it won't be out probably till 2021 because it's, I've only gotten four chapters written
and I've got 16 total to do.
So I got a while to go, but I'm supposed to be producing one chapter a month for the Manning's
early release program.
So I'll be chugging away.
That's cool.
Well, keep slow and steady.
All right.
That's the way to do it.
That's, it's cool though.
I'm looking forward to it.
It sounds great.
Yeah.
Thank you.
All right.
Now, before you all get out here, the last two questions.
So when you write some Python code, I'll go with you, Doug, first.
What editor do you use?
I primarily use PyCharm, which I really like, but I'm getting up to speed on Visual Studio
code because that's what I recommend in the book because it's freely available and it's
a great tool.
Yeah.
Those are both really good.
Obviously, I'm a huge fan of PyCharm, but basically I use VS Code for anything that's not
a Python project as well.
So yeah, it's definitely a good one.
Rusty, how about you?
I prefer Adam if I'm going to do something that's a one-off or if I'm going to be working
in multiple languages.
Jupyter Notebooks has been really big for me this year as well.
And if it's a big project, I do PyCharm.
But like I say, I'm in a relationship with PyCharm, but willing to try new things.
I've really lost all of my love for it.
My PyCharm stopped telling me when my functions are used or it stops telling me if I need an
import and things like that.
And I can't figure out how to fix it.
So yeah.
Oh, that's not good.
There is a way in the settings that you can go in and tell it to clear its cache.
I've done it all.
Okay.
Well, what a bummer.
Yeah.
All right.
Cool.
Well, yeah.
So Adam, that's cool.
That's like the grandfather of VS Code in a sense, I guess.
That's where Electron came from, right?
I really like it.
It's really, really, really customizable and really fun.
And until I really enjoyed it until Doug convinced me that I needed a debugger and there's no good
debugger built in.
So yeah, I had to switch.
I couldn't let him go down the path of being one of those Vim guys who just loads his code
with a print statement.
Nice.
Nice, nice.
And while we're talking about this, it's not either of your answers, but let me just
throw it out because it's pretty interesting.
So Rusty, you bring up Jupyter Notebooks, which is super common in the data world.
Have either of you all heard about Carnets, C-A-R-N-E-T-S?
No.
So Carnets is an open source, free, local Jupyter Notebook platform for iOS.
Wow.
So yeah, it comes with like NumPy, SciPy, Matplotlib, all that.
And it runs like on the device, not just a browser talking to something.
So it works with no internet and stuff like that.
Anyway, who knows how long it'll be until someone says that's their answer, but it's still a pretty
cool little option to help people about.
That's cool.
Yeah, for sure.
And then notable PyPI packages.
Doug, you want to go first?
Well, I have two kind of.
One is not a PyPI package.
I've been using P-Y-E-N-V to run multiple Python versions, which I find fantastic.
Very handy.
I was just thinking this morning, like I should probably start playing with that more because
it was nice to say this one is a 3.6 one and this one is a 3.8 one.
Yeah.
Right?
And with the book, I've had to update my Python version for the book twice already.
It's probably going to happen two more times.
Yeah, right.
Exactly.
And then the other one that I like, I just discovered this a couple of days ago is this
thing called JustPY, all one word.
It's an object-oriented web framework, but everything is done in Python, including the rich JavaScript
web application, which uses Vue, but is embedded in the Python.
Yeah, this is really interesting over at JustPY.io.
I just learned about it as well.
And it's like, yeah, it's a pretty cool little framework for sure.
Cool.
All right.
Well, that's a good recommendation as well.
I have no idea if you can pay up and install it, but it's definitely cool.
Rusty, how about you?
Package?
I'm going to go with pandas.
I've been cleaning data for 2,000 students for about six months, and it's been amazing.
And I never really knew why I'd want it before, but yeah, it's been a lot of fun to use, actually.
Yeah.
I wish it looked like the rest of Python, but...
It's its own special thing.
Yes.
So that's cool.
And something I just learned about recently is through Brian Okken, who I think learned
about it through another one of our Python Bytes listeners, is detail.
details, but D-T-A-L-E.
I don't know if you guys are familiar with that, but it's a cool framework that lets you
visualize Panda data frame.
So if you click on the link, you can click on, there's like a little interactive demo tutorial
thing you can check out somewhere.
There's a live demo right at the top.
But it's like, think a super reactive Excel hype thing that you just point at your data
frame and it just comes to life and you can even see like example data.
Wow, that's cool.
Yeah, it's super cool.
So anyway, if people are taking your advice and using pandas, they might also want to check
that out.
It's a pretty cool little visualizer.
Excellent.
Yep.
All right.
So final call to action.
People are out there.
Either side of this relationship that they're looking to set up to work together, what do
they do?
Well, just reach out and make themselves public.
Put yourself out there.
And yeah, just got to take the chance and maybe somebody will take you up on it.
On both sides.
I reached out to Rusty to think that I could help him out and he was willing to let me
do so, which was very great of him.
That's awesome.
Yeah, I'm sure he didn't see it that way.
That's awesome.
I could have had no information at all on the national offering to help him.
This crazy guy that has no idea about programming.
Let's talk about the program on the internet.
No, obviously he knew you were on the show and stuff, right?
So very cool.
Great.
I think that's good advice.
And I do think that that is what it takes, right?
No one is going to be willing to help you if you don't get out in the community, make
some connections and take some steps, right?
Like if there is someone showing effort to make progress, you're way more willing to put
in a little effort to help them rather than someone just like, you know, looking to get
someone to figure stuff out for them.
Yeah, absolutely.
Awesome.
All right.
Well, this is really interesting peek inside what you guys have been up to and I'm sure it'll
help some folks along the way.
I hope so too.
Yep.
Thanks for being on the show.
Thank you very much.
Thanks, Michael.
Thanks, Rusty.
Yep.
Bye guys.
you'll automatically get a $20 credit when you create a new account.
Want to level up your Python?
If you're just getting started, try my Python Jumpstart by Building 10 Apps course.
Or if you're looking for something more advanced,
check out our new Async course that digs into all the different types of
async programming you can do in Python.
And of course, if you're interested in more than one of these,
be sure to check out our Everything Bundle.
It's like a subscription that never expires.
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 feed at /itunes,
the Google Play feed at /play,
and the direct RSS feed at /rss on talkpython.fm.
This is your host, Michael Kennedy.
Thanks so much for listening.
I really appreciate it.
Now get out there and write some Python code.
I'll see you next time.