Corey Schaefer has been building his YouTube channel of tutorials for many years.
He recently has made the big shift from taking this hobby project and making it his full-time job.
You'll hear about how Corey made that transition, what it takes to go pro,
and even a little bit about the similarities between my work with Talk Python and his projects.
This is Talk Python to Me, episode 169, recorded June 29, 2018.
Welcome to Talk Python to Me, a weekly podcast on Python, the language, the libraries, the ecosystem, and the personalities.
This is your host, Michael Kennedy. Follow me on Twitter where I'm @mkennedy.
Keep up with the show and listen to past episodes at talkpython.fm,
and follow the show on Twitter via at Talk Python.
Corey, welcome to Talk Python.
Hey, thanks for having me.
Yeah, it's really great to have you here, another Python creator, putting out content for the whole world, huh?
Yeah, actually, I've been doing that now for about only a few months, so I'm kind of new to it, but it's been fun so far.
It's going to be an exciting ride for you, I know. You've been doing it for quite a while, and it's picking up speed.
That's awesome, and we're totally going to dig into those sorts of things,
but before we get to them, of course, let's hear your story. How did you get into programming in Python?
So I got into programming probably a little bit later than most people that you talk to.
I really started out, I went to Marshall University for computer science,
and really that was one of my first exposures to computer science and programming in general.
And I kind of just went and just chose a major.
My dad was a computer programmer, so I chose that.
But for the first few years there, I wasn't too passionate about it right off the bat.
And it wasn't until kind of towards the end of my college career, I got an internship down at Kennedy Space Center in Florida.
And a lot of people down there were super passionate about their jobs and loved what they did, and that kind of rubbed off on me.
So whenever I went back from my last semester of college, I was really into it,
and that's when I started doing most of my self-study and doing my own applications and things like that.
That sounds so exciting.
Like Kennedy Space Center, that is really cool.
First few years I was born, like a few miles from that place, and I lived there.
And it just seems like such a special place in both the tech science world and sort of in history in general.
What was it like to work there?
It was great, yeah.
It was an amazing place.
Even if you weren't doing programming, it was just an amazing place in general
because there's so much that you can see and do there because you can just go out on the beach and watch a space shuttle launch.
So I got to see a few launches, which was one of the coolest things I've ever seen in my life.
And, yeah, and even just driving through the Space Center, seeing all the history, you can go to the old launch pads,
and they're kind of – some of them are grown over with weeds and stuff now,
but it's kind of neat to see where all this history was built.
So, yeah, it was an awesome place to work.
One of the things that kind of motivated me whenever I worked down there was, you know,
I'd always put it on a pedestal in terms of people that can work there, which is true.
I mean, you definitely have some of the smartest people walking around there, but at the same time,
there's also so many average people there too who have just got there from studying over the years.
And that kind of rubbed off on me that, you know, there's no reason I can't be here too
if I start going and putting some effort into this stuff.
Yeah, that's a really awesome lesson.
I think that's a great lesson that, you know, a lot of people learn at different stages in life that, like,
wait a minute, this seems so high level and so impossible, but I see a bunch of sort of normal people that just worked really hard.
I could do that, right?
That's a great takeaway, I think.
Yeah, awesome.
So what kind of programming did you do there?
Whenever I was there, I was doing mostly some, I think I was doing C++, but I wasn't very good with C++ at the time.
It was a lot of, and also I got, it was just an internship, so also I was getting, they used Linux systems,
and that's one of the first times I'd use Linux.
So I spent a lot of the time just kind of learning my way and navigating around and writing some command line applications for them to parse.
I think we were parsing some XML files and things like that, but yeah, nothing too complicated.
That's cool, but basically that experience.
Learned a lot when I was there, though.
Yeah, that's awesome.
So that experience sort of inspired you to like, hey, this programming thing is actually pretty awesome.
I'm getting into it more.
Yeah, yeah, exactly.
So yeah, whenever I got back from there, I had one semester left in college, and then after I graduated college,
that's whenever I got my first programming job.
Probably spent a couple years doing some stuff that wasn't necessarily things that, you know, knowledge that lasts too long.
Like, for example, for a couple years, I was doing Adobe Flex programming.
I don't think Adobe Flex is even around anymore.
That was basically to build Adobe Flash applications.
There was a time where that was like, you could get some seriously good consulting jobs, like at the early stages of interactive web.
What is that, like 96, 97, 98 type frame?
Gosh, that was not that long ago.
I caught it on the very tail end of when JavaScript kind of replaced it.
So it was probably around 2010, yeah.
Okay, cool.
Yeah, so only about eight years ago.
And then, so after that, I got my first job where I really felt like I was learning some technologies that were going to be around for a while.
So I got a full-time job as a front-end developer doing JavaScript programming, doing GIS web applications and mapping applications.
And that was at West Virginia University in Morgantown, West Virginia.
And from there, that's when I also got exposed to Python.
We were building some back-end scripts using Python.
And so that's whenever I wrote my first Python scripts.
And so that was probably only about five years ago that I started doing that.
And, yeah, I kind of fell in love with it.
That's, I started, you know, compared to JavaScript, I was looking at Python.
And I was like, man, this is a language that I can use to write scripts that move files around in my file system.
Or I can write desktop applications or command line applications.
And back in, there's just so much.
It's such a broad language and so much that there is to tackle with it.
Yeah, that's one of the great things.
It's so broad, right?
Yeah, exactly.
Yeah, for sure.
Awesome.
And so you have what I would consider a slightly unusual job that you're doing day to day.
So why don't you tell people about the big move that you've recently made and what you're up to now?
So, yeah, about whenever I started learning Python about four or five years ago, that's whenever I started making YouTube videos.
And it kind of sounds counterintuitive to say that I was making videos on Python while I was learning Python.
But really, that's originally why I started making the videos was just to kind of solidify what I was learning and put that out for other people.
I would just keep notes of any time I was learning something.
If it wasn't exactly clear to me, then I would go back after I learned it and say, OK, well, why wasn't I understanding this when I went through it first?
And is there a way that it could have been explained to me that would have made me understand it faster?
So that's how I started making my first videos.
And, yeah, so I've been doing those videos for about four years now.
And I got a full time job working with Python out at the University of Colorado Boulder for about the past three years.
And I was making videos pretty much the whole time on the weekends.
And for the first couple of years, it wasn't it was basically just a passion project.
It was stuff that I was doing and not making any money with it at all.
I think after the first two years, I was looking at my earnings.
I was making like less than a dollar a day after two years.
So it definitely wasn't a money making scheme at the time.
But, yeah.
And then two years after that, it just kind of grows exponentially and got to the point where I started thinking, man, maybe I can do this full time.
And a couple of months ago, I was able to do that.
So, yeah.
Now my day to day is now that I'm doing it full time, it really opens up a lot of time to work on larger courses.
And because before it was hard working on the weekends to do a large course because it's really hard just to keep the continuity from weekend to weekend.
And be able to know where you picked up or picked off and stuff like that.
So, yeah.
Being able to do it every day and be able to keep my mind where I left off last time and it really helps doing those larger courses now.
That is awesome.
Yeah.
So, yeah.
The day to day basically is as far as work hours goes, it's pretty much broken up into either creating videos that I already feel comfortable teaching.
So, that's videos that I'm ready to record right now and a lot of research for videos that I want to record but that I need to brush up on the topics first.
And now for the past couple of months, I've also been spending a little time just learning how to do this as a business now.
So, that's kind of the more boring stuff in terms of learning, picking out different health insurance and retirement plans and if I want to make a different account for taxes and boring stuff like that.
Man, I was just juggling taxes earlier.
I can very much relate.
First of all, congratulations.
That's an awesome move.
Yeah.
Thank you.
Yeah.
It's been great so far.
I'm sure you're really, really happy about it.
I think this transition that you're talking about here is really tricky for people with computer science degrees or this sort of developer training because nobody teaches you about marketing, accounting, about business structures, about like all this stuff.
You're like, wait a minute.
How do I have a retirement account again when I don't have a company that gives me the 401k, right?
Like, oh, yeah.
A self-employed person, Ira.
That's apparently a thing I need to learn about.
So, you know, sort of what's that experience been like?
That's probably been the hardest thing, yeah, in terms of just learning how to get the information out there.
I've actually gotten – I'd say that a lot of that has been kind of lucky in terms of like I'll put out content that I think is good.
And if it's good enough, a lot of it's been kind of free marketing from other people.
So, you know, the Python weekly email list was big when it got on there a couple of times, and I really saw a lot of people come in from that.
People posting posts on Reddit, and, you know, one of those going popular will bring in a couple thousand people here and there.
And, yeah, so just stuff like that has really helped with marketing in terms of people just sharing the content online.
As far as self-marketing, it's – yeah, that's been hard because I'm not a very good designer in terms of, you know, designing images for my courses and things like that.
So that's been a lot of self-study just going through other online courses and learning how to create all that and put it out there on social media, making a Facebook and a Twitter and all that stuff to push that out to people who are interested.
Yeah, and I feel like coming from the tech space that marketing feels a little dirty, almost shady, right?
You're like, I don't really want to do marketing.
Yuck.
But at some point, like, if you were going to do these types of things that you and I are doing, you more or less have to go, like, okay, well, there is a positive side to – I'm trying to help people.
I'm trying to spread the word about this stuff, but I have to go through these steps or nobody will come, right?
It's not like the field of dreams.
That would be lovely.
But it really is, right?
Yeah, that's been one of the hardest things is, you know, some people are so good at selling themselves and, you know, saying, you know, if you take this course, it's the best course out there.
Trust me, and stuff like that.
And it's been hard for me to kind of push stuff like that.
Yeah, and I find, honestly, like a lot of times it's not, which is really rough, right?
So you feel like, well, if I do the same thing, I'm going to be grouped in the same category.
So it's a hard balance to strike.
So I want to run an analogy by you with your NASA background and what you've just gone through.
So people ask me sometimes, like, how do you get into these places, right?
Like, I'm doing full-time my podcast and the courses, and you're kind of doing a parallel path in YouTube.
And the story is very much the same.
Like, I started the podcast, and I would record from 9 p.m. to 10 p.m.
And then do the editing until 1 a.m.
And then wake up and go back to work or do it on the weekends.
You know, just squeeze it in whenever you can.
And at some point, it gets good enough that you can actually put more of your time into just that, right?
And so I think a good analogy for people who are thinking about these types of things is when a rocket takes off, you know, they talk about max Q, right?
You familiar with max Q?
I don't think so.
What is that exactly?
So max Q is the concept where when the rocket is taking off, it's accelerating faster and faster.
And it's going through, like, the low atmosphere at high enough speeds that it's the maximum aerodynamic force on the rocket.
Oh, okay, yeah.
And as it's trying to break free, it gets harder and harder.
It has to actually slow down.
Like, they throttle down the engines for, like, a few seconds after, like, one minute.
And then it kind of breaks through that, and it, like, takes off again.
And so going through these processes is very much, I like this max Q.
Like, the more successful that you get and you still have your job, the more work you've got to, like, double down.
And it just gets harder and harder and harder until you get to the point where you can, like, break through that.
And you're like, okay, now I can focus on the one thing.
And the pressure, at least, of, like, trying to juggle everything lets up.
Yeah, yeah.
I think that's a great analogy.
Yeah, that's, I'd say the hardest part of this whole transition was probably the last six months of work where I saw the goal line of almost being there in terms of being able to do it full time.
And it felt like I needed, you know, a few more good courses to put out there.
But, yeah, it was just a lot of work there combined with the work that I was doing full time.
And it's, yeah, that's definitely the most stressful part is that last little bit before you actually do break through and go full time.
Yeah, and probably, I don't know about you, but that last couple months when you sort of decided, but you're not quite ready, the motivation to keep doing your regular job well is hard to keep there, yeah?
Yeah, you're just thinking about, you're just thinking about, okay, as soon as I get this in place, I'm going to be doing this other thing.
And, you know, you're kind of out the door.
It's really hard.
So I do want to dig into some of your lessons and series and stuff, and we'll spend a lot of time on that.
But I guess kind of while we're still on the subject here, maybe talk about, like, lessons that you learned in going through that process of going out on your own as a person working in, you know, sort of trying to teach people in the software development field and in open source and stuff.
What went right?
What went wrong?
Like, what advice do you have for people?
Well, one piece of advice I would have is that it has to be something that you actually are really passionate about and something that you enjoy.
Because, like I was saying before, I've had a lot of people contact me just about, you know, kind of as the money.
They say, hey, can I do this and make a lot of money doing this?
I would love to.
And you definitely can after some time.
And I'm sure it's different for every person.
But for me especially, if I was just doing it to make a living and just doing it to make money,
I would have definitely given up in the first two years just because, like I was saying, I was making less than a dollar a day after two years.
So if it was all about the money, then I would have, yeah, definitely given up way before it was actually started bringing in anything.
So the first thing I would say is that it just has to be something that you actually enjoy doing and something that you probably would be doing in your free time anyway.
And I really liked doing the videos and I liked the feedback that I was getting.
So it was more about that than making money in the first place.
So that would be my first piece of advice is just that, yeah, it has to be something that you're basically going to be doing anyways.
So whether that's an open source project or a blog or, you know, making videos, anything like that.
Yeah, I guess if you really want to make money, maybe just move to New York or London and just get a stock trading job automating it with Python or something, right?
Yeah, yeah.
If you're not going to love it anyway.
Yeah.
Other than that, if it's about if people are looking into getting into teaching specifically, one thing that I've kind of learned over the years that and it's kind of evolved, too, in terms of how good you are at it.
But one of the best things you can do when you're actually teaching courses is and it's a skill that is kind of hard to come by.
But you have to kind of be able to put yourself in the position of mentally of somebody who's seeing something for the first time.
And that can be harder than people think.
Because, you know, if you have all this experience and all this knowledge, it can be hard to actually, you know, remember what it's like to see this for the first time.
And it's easy to skip over a lot of stuff and and not anticipate what kind of questions people ask or where people get tripped up.
So if people are specifically looking into teaching, that's one thing that I would recommend, too, is just try to get better at putting yourself back in that position of of learning something for the first time.
I think that is super undervalued.
And you talked about how it was kind of counterintuitive that, hey, as I'm learning Python, I'm actually creating the videos.
And I don't know about you, but one of the feelings I had was like, I really don't know enough to, like, put myself out there as an expert.
But I know I can talk about these things.
So why don't I just do that and, like, you know, see how it goes.
Right.
But I think this starting earlier in that process actually lets you connect with your students a little bit more.
You're like, yeah, just last week, I couldn't get this thing to install.
And here's what I actually had to do to make it work rather than, of course, you just, you know, do these other these few commands and it works.
Right.
So you're just you know, you're you're sort of the pain is more recent.
And so you can help people.
You can sort of have a little better empathy, I think.
Yeah.
And I think that's great advice, too, is not to be worried about putting yourself out there.
It's hard.
That's a hard stepping stone to get over.
I definitely had that also.
I definitely was making videos worried that I would get questions about things that I knew nothing about.
And and but yeah, after you put out the first videos, everybody's real appreciative that you just are showing them anything that was a hurdle for you.
Yeah, absolutely.
This portion of Talk Python to Me was brought to you by Datadog.
Get insights into your Python applications and infrastructures with Datadog's fully integrated platform.
Debug and optimize your code by tracing requests across web servers, databases and services in your environment.
Then correlate and pivot between distributed request traces, metrics and logs to troubleshoot issues without switching tools or context.
Get started today with a 14 day trial and Datadog will send you a free T-shirt.
Visit talkpython.fm/Datadog for more details.
Let's talk about some of your video series that you have going on.
Like you said, you have four years of videos and I didn't count, but it's many pages of little thumbnails.
So it's quite the set of series and stuff that you put out there.
And of course, we'll link to your YouTube channel.
But let's talk about some of the series that you put together that you liked and we'll dig into them a bit.
Okay, great.
Yeah, sounds good.
What's the first one you want to talk about?
The most popular series on the channel right now is probably my object oriented series.
I think that's my most popular video.
I'm not sure how many views that has right now, but it's above all the other ones.
I think that people enjoy the object oriented series because it's kind of taught a little bit different than some of the other courses that are online in terms of.
So, for example, we show a lot of real world applications for what you're learning in that course.
And by real world applications, it's not something that I put together that's a real world example.
It's really actual code like in the standard library.
We'll open that up and see like, okay, if we're doing like static and class methods, like so class methods can be used as alternative constructors.
And so we'll open up the daytime library and see, okay, well, and for people who don't know what an alternative constructor is, basically it's multiple ways of creating an object or instantiating an object.
So, you know, date times can be created by the default way as just saying, okay, I want a date that is the year, month, day.
But you can also do, usually they start with like a from keyword.
So from timestamp or something like that.
So there's multiple ways to create a daytime object.
And those are all class methods.
So we open up the standard library, look through there and say, okay, well, here is a class method and here's how date time is using it.
And this is, and it's doing basically exactly what we just learned in the course.
And that kind of gives people confidence that, you know, there's millions of people using this code and the daytime module.
So they know it's going to be something that is, that applies to the real world, what they're learning at the time.
Yeah, that's cool.
Certainly digging into the standard library code is a neat way of doing it.
You know that it's been optimized for performance.
It's been, like you said, used by countless numbers of people.
It's pretty interesting.
I think certainly class methods and static methods are, they're interesting in that they're almost the same, but not exactly the same.
And so it's like, well, why would I use a static method over a class method?
Do you have any thoughts on this?
So a static method, yeah, static methods can be a little confusing because static methods don't take self or the instance or the class as an argument.
They're basically, they're basically just regular functions.
And so people don't really, so they have nothing really to do with like the instance or the class.
It's really just, it could be a separate function almost.
And people don't really know when to use static methods.
But it's, it's really a function that, yeah, it doesn't operate on the instance or the class, but it does have a relation to the class.
So like the example that I use in the, in the series is we're building like an employee object.
And I'll say, okay, well, you might have like an is workday method, like to check, to pass in a date and see if that is a workday or, you know, something like that.
So checking if something is a workday, it doesn't actually work on the employee instance or the class itself.
It could be a separate function altogether.
But it's kind of related to that, to that object in a way that it might be some functionality that you want to pass on whenever somebody input, imports your class that you created.
So that's kind of what a static method is in the sense of why you might include that in an object or in a class.
And yeah, the class methods are basically it's, you're working instead of passing in the instance, like a regular method, you're working on the class itself.
So, and like I said, you can use that to set class attributes if you want, or a lot of people use them for alternative instructors where you can take in different arguments and then return that class with an instance of a newly created class.
That's right.
Almost like a factory method.
Like if you're going to allocate an instance of that class in the class method, you need to know that it's not.
If you derive from it, then you want to create the derived thing, not the other thing.
But the fact that the class, the CLS thing is passed in, you could just sort of, you know, call that and get to the constructor.
Yeah, exactly.
Yeah.
Pretty interesting.
Yeah.
Okay.
So what else do you cover in the object oriented series?
So we also do inheritance.
So inheritance is another one where we kind of go through the lesson, but then we also open up the standard library and see how it's done.
So I never knew how to pronounce.
I never have actually heard this spoken out loud, but the work zoo library, the one that.
It ships with a dependency of flask.
Uh-huh.
So yeah, we, we, we look in there and we take a look at their HTTP exceptions.
And that's a great example of inheritance used well there because they have their base HTTP exception, which gives you all of this functionality.
And then each higher level exception, like a 404 not found or a 500 internal error, they all inherit from that base HTTP exception.
So they get all of that code for reuse.
And then basically they just change like the status code in the method or in the message.
So it's a, it's kind of a neat way of seeing how a real world library is actually using this efficiently.
That's a really great example.
And I think that's one of the places where inheritance makes tons of sense in Python.
I'm, I'm a big fan of classes and inheritance, but I do feel like they can be a little bit overused in Python because sometimes it's just used for like grouping common behaviors.
And we could just as well do that in a module with some module level functions or variables, just as, you know, much say like a class with a bunch of static methods, right?
They're kind of almost equivalent.
It's just different ways, ways of thinking, but around exceptions, like it really makes a big difference, right?
Because in your accept various type, you use the inheritance to drive your error handling basically.
Yeah, exactly.
Yeah.
So I really like that.
That's awesome.
Another one that I think is probably really popular in, in your set of videos is Python for beginners.
Like we all want to, you know, maybe write the most advanced, like deep look inside of this aspect of saying like an ORM or something.
But the truth is most people are just getting into Python.
Like it's a growing field.
So most people are coming into it.
They're not looking for like that super internal deep dive thing.
Right.
So this beginner series is probably pretty popular.
Yeah.
The beginner series.
I think that's my second most popular series on the channel behind the object oriented.
And it's kind of funny because it took me a long time to put a beginner series together because originally I was only going to do videos where I didn't think that there was, you know, I thought that other tutorials were kind of lacking in and things like that.
And there's so many good Python beginner series is out there that I wasn't really going to tackle that.
And not only on YouTube, but just kind of everywhere.
There's some great resources for learning Python.
But I think a lot of people will, you know, just kind of get used to a specific instructor.
And they, you know, even if you recommend a class elsewhere, they'll say, OK, well, you know, I'd really like, though, if you would teach it.
And so so I put one together and gave in after a couple of years.
And but, yeah, it's a popular course.
So we go over, you know, just basic installation and how to set the Python path on Mac and Windows and Linux and things.
That's where a lot of people get tripped up.
And also so we touch on basically the data, all the basic stuff, data types, loops and conditionals.
But once we get up to functions, we kind of try to tie all that back together.
And again, we pull up.
We basically write a function that that will check how many days are in a month given a year in a month.
And that's basically a function that's already written in the standard library.
I think that's in the calendar or calendar module.
Maybe I can't remember exactly.
But, yeah, we go through that and kind of learn or use everything that we learn to build up that function.
And then when it's all said and done, we can open up the standard library there and see, OK, well, we just basically wrote a function that that a lot of people use on a regular basis.
So so in that beginner series, I think it's really awesome that you actually start with import anti-gravity because that's both fun and instructive.
Like, wait a minute.
Why did importing a thing actually cause an action?
Isn't that more of a declaration and not a behavior?
Yeah, that's one of the more popular videos on there is where we go over imports and kind of show what the sys.path is and and how to append to that path.
Or you can set the Python path in an environment variable.
And also, yeah, the import anti-gravity is one part in that series where we say, OK, well, we're importing this module and it does something cool.
It opens up our web browser.
Let me interrupt you just for a second, Corey.
Maybe not everyone has has actually typed import anti-gravity into their Python ripple.
So if you're listening and you could do that, stop for a second and type import anti-gravity inside the Python ripple.
If not, tell people what happened.
Yeah, basically, it's kind of an Easter egg in Python in the sense that it's not super useful, but it opens up your web browser and just kind of sends you to one of the XKCD comics that is kind of talking about a little comic about Python on there.
That's that's kind of funny.
So, yeah, it's super, super easy.
It's just import one line and then it opens up your browser and goes to that comic.
I think it's really instructful, though, because it's instructful because when you talk about things like the pattern for, you know, if Dunder name equal equal may under main then invoke this behavior like that stuff doesn't really register with people coming from something like C++ or C#.
You're like, wait a minute.
What is this weird construct at the end?
But this sort of going through this experience is like, oh, I see actually how functions and classes get defined and how things get imported and brought into my namespace and all these sorts.
It's like really it helps to break the paradigm that is incongruent with Python.
People come for this other languages.
Yeah, exactly.
Yeah.
And it makes it super easy to like even if you're wondering how that imported code works, then I mean, you always have the opportunity in Python to just look underneath the hood.
So if you want to, you know, see, OK, well, what is this module doing that?
I just, you know, it's opening my browser and opening this comic book.
But how is it doing that?
So then you can go into the standard library and just look at the anti-gravity file.
And it's basically two lines.
It just kind of imports the web browser and then, you know, uses web browser dot open on that comic.
And that kind of makes people feel like once they know how to look at that other people's code, they can say, OK, well, now, you know, now I've learned something here.
So now if I want to open up a web browser to my own web page, then this is how you do it.
So you can always dig deeper and look under the hood and see what's going on.
I think that's another really interesting thing with Python as well.
Yeah, that's a really cool way to kick things off.
What else do you talk about in that series?
After the so after we go through all the data types and conditionals and and for loops and everything like that, and then the importing and taking a look a little bit at the standard library in terms of, you know, how to how to do basic things with the standard library, like work a little bit with dates and the random module and the math module.
After we do all that, it's kind of open ended after that.
So I end the series at a nine part series after we learn how to import.
And from there, I basically tell people, just like we were talking about before, how Python is such a broad language.
And after you learn those fundamentals, you can pretty much take it anywhere that you want.
So, you know, if like I didn't want to continue the series and, you know, teach them about file objects next, like it was the next, you know, obvious thing that people should learn.
Really, after that, they can you know, if they want to learn how to work with file objects and they can do that or if they want to learn to work with a database and they can do that.
So after that first nine videos, then it's kind of broken up to I kind of logically ordered the videos in a sense of what I think would be good to learn next.
But I tell them that from that point on, they can basically skip around and and learn whatever specific subject they want to learn about.
Yeah, that's one of the challenges of teaching Python is so many people use it for different things, right?
Like some people may be learning it for data science.
And so they want to learn all about, you know, that side of things.
Maybe you're learning for web.
So you got to learn about frameworks and databases.
Maybe you're learning it for DevOps.
And if you're in one class of people, you do not want to be learning about DevOps when you're trying to do data science.
Like it's just like, you know, there's it's one of the real things that's making Python grow so fast is people coming from all these different disciplines.
But it's really interesting to see different ways of working with Python.
You know, you've got like the data scientists working with Jupyter Notebooks in this sort of exploratory fashion.
I've got the web developers building like really structured architectured things with unit tests and code coverage.
And it's kind of cool to have them all coexist.
Yeah, exactly.
That's also one of the challenge.
Yeah.
Like you were saying, one of the challenges with teaching Python, too, is, you know, whenever you say that, you know, Python, a lot of people kind of expect that you kind of know every aspect of Python.
But, yeah, there's just so much so much to cover that.
Yeah.
If somebody.
So, for example, my previous full time job, I was basically doing a lot of web service back end work.
So, that's kind of why I started with the Flask course as my first course that I put together whenever I first went full time.
But, yeah, and things like data science and machine learning are things that I want to cover in the future.
But those are things that, you know, I'm going to have to, you know, buff up on myself because there's just so much there.
And, yeah, so much to learn with it.
For sure.
I think that's an interesting segue to the next series that you put together.
Because both with the podcast and with the courses that I'm doing, at some point it hits a limit of, like, I have totally tons of experience doing this.
And I can just do this off the top of my head where it gets into the point of, like, you know, I've never actually dug into that aspect of what I'm trying to teach people or try to interview people about.
And it becomes quite the research project, right?
So, that was sort of the story with your Flask one, right?
Yeah, the Flask series was the first one that I put together after I went full time.
And I kind of made a mistake whenever I first did that because whenever I first quit, I kind of saw this huge chunk of free time.
And I was like, okay, well, now I can start working on large series.
But probably in hindsight, what I should have done is put together a lot of one-off videos that I could slowly release while I was working on that large series.
Because, you know, a lot of people had found out that I went full time.
But then it took me about a month of, you know, doing some research and putting together a blog that I thought, you know, had a lot of features that people would be looking for, like uploading profile pictures and an entire authentication system and setting password reset or email resets and stuff like that.
And so, yeah, it took me about a month to, you know, research that and record it and edit it.
And it came out to be about eight hours worth of content.
And, yeah, so, yeah, that was one series that it's pretty popular.
It kind of takes a Flask application and you can kind of see how an application like that will evolve over time.
So, we start out just by, you know, using the default Flask that you can get from the documentation, the hello world, and just in a single file.
And then build that up to where, okay, well, if something gets a little more complicated, then it's, we can't really hold it in this single file anymore.
So, now we have to break it up into packages.
So, then we start using packages to simplify imports and things like that.
Oh, and to give credit where credit is due, where I learned a lot of that stuff with the imports and circular dependencies and things like that was from a lot of talks by Miguel Greenberg.
He does, I think he's been on the podcast before.
He does a great job with Flask applications.
And he has a mega Flask tutorial that he put together that's, you know, more advanced than even the series I did on it.
So, yeah, he does a great job with those.
Yeah, Miguel's series was really cool.
And I love the way that he sort of revamped it recently.
So, yeah, I think your Flask series is quite interesting.
And it's probably worth talking just a little bit about, like, how much time and energy does it take to put together one of these things?
So, you said it took for eight hours of published content.
It took you a month of full-time work.
That sounds about right to me.
But I'm not sure everybody who comes along understands how much effort goes into creating these short, relatively short little bits that come out the other side.
And it really depends on what you're teaching, too.
I mean, it's kind of similar to, like, as an analogy, I'd probably say it's kind of similar to, like, writing music or something like that.
You'll hear interviews with certain people who say that, you know, it took them forever to just write this one song.
And then a lot of people say that they just kind of sat down and it just started, you know, coming out and was everything kind of poured out in one session.
And it's kind of like that with this.
Like, sometimes it takes me longer to put some videos I can put together, you know, an hour.
And it just I can record it all on one take and get there in no time.
And then sometimes it just takes a while to get all these pieces together and make sure that I'm teaching it in a way to where I'm not, you know, repeating the same topics too much.
And that they're that we're kind of touching on all the topics that people would want to learn about in terms of polished, finished application and things like that.
So it kind of one of the things that took me the longest was just it's been so long since I've touched front end development that I wanted the, you know, I wanted the finished application to look nice so that people could have a nice application once they were done.
So a lot of that time went into, you know, relearning some JavaScript and CSS.
And that's not even stuff that we really touch on in the video.
It's just a code snippet that I hand out and say, well, you can use this for the CSS.
But even that took a while to put together just to make it look presentable.
So, yeah, a lot of work, a lot of hidden work goes in that a lot of people don't see there.
This portion of Talk Python to Me has been brought to you by Rollbar.
One of the frustrating things about being a developer is dealing with errors.
Relying on users to report errors, digging through log files, trying to debug issues, or getting millions of alerts just flooding your inbox and ruining your day.
With Rollbar's full stack error monitoring, you get the context, insight, and control you need to find and fix bugs faster.
Adding Rollbar to your Python app is as easy as pip install Rollbar.
You can start tracking production errors and deployments in eight minutes or less.
Are you considering self-hosting tools for security or compliance reasons?
Then you should really check out Rollbar's compliant SaaS option.
Get advanced security features and meet compliance without the hassle of self-hosting, including HIPAA, ISO 27001, Privacy Shield, and more.
They'd love to give you a demo.
Give Rollbar a try today.
Go to talkpython.fm/Rollbar and check them out.
Yeah, I agree.
I think when you talk about the people who just – or the times in which you just sit down and stuff just flows out, you couldn't do that from scratch, though.
That happens because you're kind of swimming in these ideas and in these spaces where this is like all around you.
And then eventually it crystallizes in your mind.
You sit down and it comes out.
But if you just took a random person off the street, right, they probably wouldn't have that happen because they haven't been thinking about it for a month before they decided to work on it, right?
Yeah, that's exactly right.
Yeah, you definitely have to know the subject well before you sit down and do that.
But yeah, that's – I'm sure you probably have the same thing with teaching courses.
But I've got folders and folders of just thousands of ideas where I have kind of started writing videos and then stopped and then will start again.
And then kind of whenever I'm actually ready to record it, I piece all those together into one finished course that finally comes out.
But yeah, just even piecing those small pieces together and setting down over time and writing those, it takes a long time if you were to actually add it up altogether.
Yeah, for sure.
I have a Google Doc that I think has 63 full course ideas in it, 63 different courses.
And I'll go back and I'll pull stuff out of there.
But people are suggesting interesting new courses to me faster than I can – that list is growing.
It's not shrinking even though I'm doing it all the time.
I guess one final thing to round that out.
Like I just saw a comment on Reddit saying about my 100 days of code course saying, oh, the course is only 17 hours of like polished edited video, right?
Like how can this be for 100 days?
I'm just like, you have no idea, man.
You have no idea.
You know, it also comes with like 80 hours of exercises.
So there's your 100.
But it took me, Bob Belderbos, and Julian Squira.
It took us three and a half months each.
Like that's a full year almost of one – if you did it as one person of just to come up with like that content.
There's like some serious, serious commitments you got to make here.
Yeah, I'm sure that, you know, the hours that are actually edited down when it's all said and done too.
Like I'm sure you have the same experience.
But like whenever I said that there was about eight hours of Flask finished content, that was edited down probably – I think those unedited videos before cutting out all the dead spots was about 22 hours of content.
So I actually only end up using about a third of everything that was actually recorded.
So yeah, it takes a while even to cut those down.
Yeah, it's quite the thing.
All right.
So let's touch on the last two because they're both really interesting.
One is decorators.
I feel like decorators are quite mysterious to most people, many people in Python anyway.
Now that's only one video, but it's kind of funny.
I get a lot of comments in the comment section of that video that they say it's kind of like YouTube inception because it's – because in the decorators video, I basically say, okay, well, we're going to do decorators in this video.
But if you haven't learned about closures yet, then you might want to go watch my closures video.
And then in the closures video, I say, well, okay, we're going to learn about closures here.
But if you haven't watched my first class functions video, then you might want to go watch that first.
So people kind of get down this rabbit hole.
But yeah, after – so yeah, first we kind of teach people about first class functions and what that means.
And basically that means that you can just pass a function around like any other variable.
So if you can set a variable equal to a function or you can either execute the function and set it to the return value or you cannot execute the function and just set it equal to that function ready to be executed.
And then when it comes to closures, you kind of use that same concept where you can return.
So within a function, you can return an inner function waiting to be executed.
And that inner function will kind of remember the context in which the first function was run.
And then decorators builds on that to where you actually pass in a function and add functionality dynamically.
So yeah, I mean I can totally understand why it's a confusing subject.
It took me a long time to wrap my head around it too.
So yeah, it's confusing just in terms of how much is going on and you kind of got to piece these things together.
And even after I've taught that video, you still run – and I'm sure this is like this with everybody.
But if you're reading someone else's code and you run into a complicated decorator, then you kind of got to sit down and be like, okay, let me map all this out here and see exactly what's going on.
It's definitely not super intuitive, but it's very useful once you have that down.
Yeah, it's definitely useful once you learn it.
But yeah, it's a bit of a mind-blown sort of thing.
The last series or video that you talked about is something I've been thinking a lot about lately as well is how to volunteer your skills as a software engineer.
And I feel like software engineers are almost modern-day magicians.
So much of the world is technical or interacts with technology and devices.
And we're the people who can kind of wave the magic keyboard and then something comes into existence that solves one of these problems or something along those lines.
We have the skill to do that, right?
And so how – if you see problems where you're like, well, these people just knew a little programming.
This would just not be – this could totally change things.
What do you talk about in this one?
So yeah, that video, it's – that's a video that I did several years ago.
And it's a video that I really like a lot, but it's not very popular.
And I think the reason it's not very popular is just because I think when I released that video, I only had like a few hundred subscribers.
And it's not very often that people go back years to see what videos I was making back then.
So that's one that now that I have a larger audience, I think I'd like to remake that one.
But yeah, in that video, I basically talk about when people think about volunteering, they – especially as software developers, you might not think that you can actually volunteer using your skill set.
You might think that you have to do something else.
But yeah, there's tons of things that people who have a tech background can do.
So one of the first things I mentioned is at senior sitters or assisted living homes, you can go in – and this isn't exactly software related, but you can go in and just show people how to set up emails or connect to Wi-Fi.
Because it's kind of a misconception that older people don't really care about technology or don't want to use technology.
But in my experience, I did that for a few years ago.
And you go in and they definitely want to stay connected and they want to get pictures of their grandkids and set up their email so that they can keep in touch with family or learn how to subscribe to their favorite online news source or anything like that.
That's one way for – as far as tech people.
As far as it's – as far as being more software related, I also talk about how you can build websites for free for certain organizations that might not be able to actually afford to hire somebody.
So you can do websites for maybe a pet shelter or a local farmer's market or something like that.
That's a cool idea.
And one of the things so many people who are getting into Python need before they can actually reasonably go get jobs is some experience and something they can point at and go, that thing?
I built that thing and here's what it does and here's how this company is using it.
Here's a way if you've got some free time that you could do one of those projects and it still benefits you very directly in that like when you apply for the job, say, for Django or whatever, you go, yeah, I use Django.
Look, this thing I did over here and maybe they maybe learned it from your channel or something.
Who knows?
That's definitely a great way to have some things added to your portfolio.
I get that question all the time, people asking me, what is a real-world project that I can do that a computer or that a corporation or an employer might be interested in?
And usually, yeah, usually I tell them that like one of my top recommendations is to build a website because when you build a website from scratch, you get so much, you get your hands involved in so many different areas.
So, for example, you do the back end, which is probably going to be in Python if you're listening to this podcast, but you can also do back end websites and Node.js and PHP and things like that.
But you also get exposed to the front end doing JavaScript, HTML, CSS.
If you host the website yourself, you get...
Maybe Linux and Docker, yeah.
Yeah, yeah, yeah.
So if you're hosting the website yourself, you're going to get exposed to Linux and setting up, you know, system security and how domain hosting works and everything.
So, yeah, doing a website is a great way for people to build up a portfolio because you get exposed to so much.
And not only that, but it also helps you realize what you like the most.
So if you, you know, if you liked doing...
And that's kind of what happened to me is once I started doing back end web work with Python, I realized, hey, I think I want to do this instead of front end work now.
So it's, you might not know it until you try it.
And it's the same thing with, you know, maybe somebody will do, put their website up on a Linux system and they really like doing the system administration type of stuff.
And then they go and do that full time.
So not only is it a great way to get a portfolio built up, but it's also a great way to kind of identify where your strong points are and what you enjoy the most.
That's great advice.
One of these sorts of examples that people did in a volunteer sense that I thought was pretty cool is something called Humanitarian Toolbox.
It's at htbox.org.
Now this, I think, I think the project is mostly a .NET project.
So Python people might not really care to contribute, but maybe it'll inspire you.
It's like a thing that the Red Cross and other organizations like them can use for like hurricanes and earthquakes and stuff like that to help connect people and victims and sort of after stuff strikes.
It's pretty cool.
Yeah.
They're kind of similar to that.
There's a, if you go to GitHub, I think it's under, it used to be under GitHub showcases, but now I think it's under GitHub collections.
And I've never actually contributed to any of these projects, but I saw it in my research for that video.
And it's kind of the same.
It has, there's one section that's called Made in Africa.
And it's a lot of, you know, open source software that people are using over there to stay connected so they can do, you know, yeah, emergency response or SMS type of systems where they can message people back and forth.
And setting up that infrastructure is, yeah, would be a great thing to work on.
So it sounds kind of similar to what you're talking about with the Red Cross.
That's awesome.
I put the Made in Africa link in the show notes for people.
Cool.
Awesome.
All right.
So that rounds out the video series that we are going to, the ones we're going to cover, at least for the show.
But you have a whole bunch and people can come check them out on your YouTube channel, right?
Yeah.
Yeah, definitely.
All right.
So in the last bit of time that we got, I think I want to talk a little bit about some of the mechanics of just being successful on YouTube.
So you touched on a few things like how to, you have to enjoy it, right?
You can't just go in there for money.
You talked about how it took a long time before you saw any success.
And I think one of the things that is, as human beings, especially people who are human beings who are excited about a thing you're about to embark upon, it's really hard to understand the non-linearity of these types of things, right?
Like you worked on your channel for a long time before it started to see growth.
I worked on the podcast for a long time before it was anything that would reasonably put my daughters through college.
But then it does, right?
But you've almost got to have this irrational belief that if I just, I'm not there yet.
I know it's been six months, but I'm just like, yeah, we're going to be way more than $10 next month, I promise.
Right?
So it's an interesting thing.
So you do have to enjoy it and basically have to do it anyway.
It's like, I would do this anyway.
Hopefully people enjoy it, right?
Yeah, exactly.
Yeah.
So what other advice do you have?
Yeah, I'd say that's the biggest piece of advice.
As far as YouTube and teaching in general, so first of all, yeah, like we were saying, you have to have patience.
But you also have to have some consistency.
But you also don't want to be tied down by that consistency.
So like, for example, you know, if you get on and look up YouTube advice on how to be a successful YouTuber, for example, one of the top things you always see is to be consistent.
So like, you know, a lot of people like to put out like a weekly show, like, okay, every Wednesday I'm going to release a video.
And I think that's great advice.
And definitely I wouldn't say not to do that.
But also don't be afraid to break away from advice like that as well, because I try to be consistent in terms of releasing, you know, a week or every other week.
But I'm not tied to that so much to where I sacrifice the content.
So if you have like a deadline coming up and it's like, okay, well, I told people I would put this out, but the content's really not that good.
Then I would sacrifice the deadlines to make the content better because the content's really the most important thing.
You want to put out something that you're proud of that you think is going to actually teach people and not just some, you know, quick video that no one's really going to care about just to meet a self-imposed deadline.
So, yeah, I'd say for blogs and for, you know, YouTube or any kind of teaching or any kind of content creation, content should be the first and foremost thing that you think about whenever you put stuff out.
Yeah, that's really interesting.
I think it's good advice.
You and Dan Bader had an open session at PyCon covering some of these ideas, and I was hoping I could make it, but I was at my booth doing my booth thing.
So I couldn't go, but you said you learned some interesting stuff there.
What was that like?
Yeah, so that was an awesome experience for me because, you know, this was my first year at PyCon.
And, you know, usually when I do these videos, I'm just behind the computer.
I'm not like, you know, interacting with creators all the time, other creators.
And so that was a really cool session in terms of just bouncing ideas off of each other.
And it was interesting, too, because it's the first time that I've actually been included in something like that.
Because, you know, whenever I was learning Python, I was like Al Swigert was there.
He's the one who wrote Automate the Boring Stuff.
And Trey Hunter has given a bunch of PyCon talks.
So it was just kind of interesting being in that group.
And, you know, some people asking questions like, oh, well, what do you think about this?
And, you know, it's just kind of interesting in terms of being kind of included in that for now.
But, yeah, we bounce some ideas off each other in terms of, you know, a lot of people are saying that they were basically saying that they use email lists a lot.
So that's one thing that I'm kind of lacking on is setting up a good emailing list, because that's something that you can kind of take anywhere when you know anywhere that you go.
So if, you know, YouTube was to fall through and I have to move to a different platform, then that email list is still something that stays with you.
And you can always, you know, email out all of your followers and say, hey, I'm, you know, not doing this anymore.
I'm going here.
So you kind of have an audience that can follow you around.
So, yeah, bouncing ideas like that off of each other was a great way to to learn different techniques and different streaming services and how other people are doing things.
So, yeah, I thought it was extremely useful.
That's really cool.
I definitely want to double down on that.
Like, I think the sort of the email list side of things and that kind of stuff is very much the iceberg of success for a lot of these things.
And, you know, the stuff that you don't actually see, the people are like, that person is crazy successful about it.
But you don't actually see how it is.
There probably is some sort of email list involved.
Like I have, you know, some for the podcast and some for the training.
And it's the relative value.
I would say, like, I would trade 20,000 Twitter followers for 2,000 email people who actually want to be there.
Like it's at least that that much of a difference.
Yeah, because that's people who have gone out of their way to actually, you know, taking the time to subscribe.
It's so much easier to just get on Twitter and hit follow.
But, yeah, there's so many of those people who won't get the message that you're trying to send through.
So, yeah, having a core audience of people who, you know, really listen to the things that you send out is definitely, definitely useful to have.
Yeah, I just want to say thanks to everybody who subscribed to my list or subscribed to the podcast.
And I know you feel the same way about your YouTube subscribers, right?
Yeah, that's definitely the only reason that we can do it full time for sure.
Yeah, for sure.
So, YouTube can be a tough place to sort of put yourself out there.
Where, you know, it's like 99% of the people are really friendly and super supportive.
And then other people, you know, they'll think that you owe them some sort of consulting thing because you talked about something they're having a problem with.
Or they can just be like outright mean.
Like, have you had any of those experiences?
I know that I have and other people who are doing similar stuff have.
Yeah, so like you said, it's probably a little over more than 99% who are completely positive.
And then you're going to have that, you know, that less than 1% who definitely kind of give you a hard time.
And yeah, I've run into that.
It's one thing that you kind of have to – I actually thought it was going to be worse before I started doing it.
So it was – because, you know, I look at, you know, news channels on YouTube and stuff like that.
If you look in the comment section of channels like that, it's just a complete, you know, dumpster fire.
It's terrible.
But in this community, it's been fantastic.
You know, a lot of people are supportive, you know, and other creators even support other creators.
So it's not like we look at each other as, you know, competitors.
I've had – you know, I've recommended other people's YouTube channels whenever I don't really haven't covered a subject yet.
And they've done the same.
I've seen, you know, people who have YouTube channels who link to my videos.
And yeah, so it's for the most part very supportive.
But yeah, that's just like anything on social media these days.
You kind of have to have slightly thick of a skin to ignore that 1% because those are definitely the ones that kind of stick with you and sting for a while.
But –
Exactly.
You could have 100 great comments and then one super mean one.
And somehow that is the takeaway that you take from those messages.
But I find that I've gotten to the point where, you know, I have definitely not thick skin in general as a person.
But over the last few years, I definitely have built it up and it's fine.
But I just wanted to kind of touch on that a little bit for anyone else who's out there thinking about it.
Just let it roll off.
It's not the – you're helping most of the people.
There's a few people that get upset and whatever.
Yeah, exactly.
And that's – these days I don't even take it personally.
I think those people would be upset at no matter what the content is.
I think some people are just looking for an outlet and they kind of forget that there's another person on the other side of the computer.
And so they kind of use it as their own, you know, little punching bag to get on there and say whatever they want to say.
So – but yeah, it used to bother me more than it did.
But after doing it for a while, you just got to, yeah, let it roll off.
Yeah, I'll give you one real quick example just so people kind of get a sense.
You know, I have two MongoDB courses.
One of them is eight hours.
And we talked about how much work that is.
One of them is two and a half hours and it's not like a copy of the other course.
It's totally different.
And I did that from scratch.
And it took me almost a month of just work to make that free course that I gave away, you know.
And one of the first comments was, why won't you just give us the full course?
This is crap.
I'm just like, are you kidding?
I spent a full month of my life making zero income to make this for people like you.
You don't have to love it.
But please, you know, come on.
Don't like go out and publicly berate it.
Right?
But that kind of stuff, you know, hundreds of people loved it.
Thousands of people loved it.
But that one person still kind of bugs me.
So you just got to get like to the point where like, yeah, that does bug me.
Yes.
Stuff like that.
There's, you know, there's a lot of stuff out there that's, yeah, just not really offered as constructive criticism.
I mean, I get a lot of constructive criticism and I kind of like that.
I like whenever people are nice and they say, hey, you know, I, you know, why don't you, I couldn't really watch this.
You know, on some of my older videos, they were like, you know, this looks great, but I wish you would have made the text larger because I can't see.
So now stuff like that really helps because I can make better stuff.
But yeah, there's a lot out there that's not even really meant to be constructive.
I think the other day I had, let's see, one of them that kind of stuck with me is one of the earlier videos I did.
Somebody was like, man, this guy's Southern accent is so bad.
Why would anybody watch this, you know, watch this all the way through?
And so I was kind of thinking about that, like, man, maybe everybody's going to think that.
But no, it's 99.9% positive.
So, yeah.
Yeah, yeah, yeah.
Absolutely.
All right.
So I guess, you know, I don't have enough experience with this side of things, but, you know, maybe people out there might be interested.
So share as much or as little about this as you want to tell me, like, I don't want to answer this.
But you talked about in the first couple of years, you only made like $100 a month or something like that.
And then it became enough that it could be your job.
Like, what level of subscribers and views and, like, how frequently do you have to put stuff out where it's like, okay, I could reasonably call this my job if I did that?
So what's the bar for people to aim for if they wanted to do something like that, I guess is what I'm asking.
That is a tough question to answer because it's so – it's very – it's different for every person.
So, like, for me personally, I was able to – I think I quit my job as soon as I reached 100,000 subscribers.
But sometimes people will have more subscribers with less views, and sometimes they'll have more views with less subscribers.
So it's kind of hard to – kind of hard to say exactly, you know, the number of subscribers there.
But one thing I will say is as I was going through the process, let's see, I think I was – I probably was able to quit whenever I was getting about 600,000 views per month.
And that's – and YouTube has all those analytics for people.
YouTube's great with analytics in terms of, you know, telling you your demographic and when people stop watching your videos and how many people are watching your videos and where they're being found from, whether they're being found in search results or external URLs.
So, yeah, that's about the time I could quit my job.
And I'm actually trying to move over to different sources of income as well.
So I'd say right now – and I just made a video about this the other day.
But I think right now I'm making about 95 percent of my income from YouTube advertisements.
So when people go to watch a video, YouTube plays an ad before the video, and then the creator gets a chunk of that money.
But really I would like to build up the fan funding section to where it makes up the majority of my income.
You know, sites like Patreon.
I know that you have a Patreon for Talk Python.
Yeah.
And that's – I've never experimented with Kickstarter.
I know you've done some Kickstarter things that – so basically for people who don't know the difference between Patreon and Kickstarter is that Kickstarter is really meant to fund like one single project.
And you have, you know, a goal that you're trying to reach.
And Patreon is more monthly contributions to an ongoing project.
So, you know, for people who are making consistent content like Talk Python, people can just support that on a monthly basis.
So I would really like to build up the fan funding section of the income more so that I wouldn't have to rely as much on YouTube.
Because like I was saying before, in terms of having an email list where people can follow you to any platform, that's kind of the same concept with fan funding.
Like if I was to go from, you know, YouTube to something like Twitch and start doing more live streams through something like Twitch, then I wouldn't have to worry that I was losing that YouTube income if I had the majority coming from fan funding.
So then you can just be – you know, those are the only people that you, you know, are really looking out for are the people who are actually paying for your content and worrying less about advertisers and sponsors and stuff like that.
Yeah, that's really interesting.
I think it's a good path for where you are and where you're going.
And it seems like a great way to connect with people.
I don't push my Patreon stuff that much because if somebody supports the podcast by donating $1 a week, that's about $50.
Or if they could buy one class a year, that's also about $50.
And if they buy the class, then they get something extra.
Whereas the Patreon, they kind of – I don't really have any perks there.
So I don't push that super hard.
But the multiple angles of staying in touch, the multiple ways that you can interact with people and help them and they can give back definitely is worth pursuing.
Yeah, exactly.
All right.
Well, Corey, this has been super interesting.
And I think we're just about out of time here.
So let me ask you the final two questions.
So if you're going to write some Python code, what editor do you use?
Although we could go to your YouTube channel and discover this probably.
But go ahead and tell me that.
That's probably the most common question that I get in my comment section is what editor I'm using in the videos.
So I'm using – I have a few videos where I set up different development environments.
But the one that I'm actually using the most is Sublime Text.
So – and that's – I didn't choose Sublime Text for any reason other than the fact that it is very minimalist and it doesn't have any bells and whistles getting in the way.
And that makes it good for recording videos because then people can just focus on the actual code instead of seeing all these extra options off to the side.
I think that PyCharm might have something like that in a presentation mode.
But I – you know, Sublime Text is working for me so well right now that I haven't taken the time to check out other IDEs that might be useful.
But I've heard great things about PyCharm too, though.
Yeah, very nice.
Yeah, definitely Sublime Text is great.
And then notable PyPI package.
Yeah, I think the package I probably use most often is SQLAlchemy or SQLAlchemy.
And that's basically just because, you know, it's hard to touch any application these days that doesn't have some kind of database in the back end.
Even if that's, you know, a desktop application, you might be using SQLite on the file system or a web application you'll be doing, you know, maybe a Postgres in the background.
And, yeah, SQLAlchemy is great because it gives you this, you know, something that you can interact with and even switch databases around.
You know, you can use SQLite for development and then go to Postgres for production.
And all of that code just stays the same that you've written for SQLAlchemy.
So that's definitely the one I think I use most often.
Yeah, that's a really nice one.
And the ability to just change the connection string for production to development and maybe even have a totally different database, like you said, is really great.
Yeah.
So I've been recently been playing with Alembic.
Have you been playing with that?
Alembic.
Is that, I don't think I have used that.
It comes from Mike Bayer as well, and it integrates with SQLAlchemy to do migrations.
So as your class schema changes, you can just say apply these changes to upgrade my database in production or in staging as those changes roll in.
It's really nice.
Okay.
Yeah, that's right.
I have actually used that on one project.
And, yeah, that is a nice addition to SQLAlchemy as well.
Yeah, I like those together.
All right.
So final call to action.
I know lots of people out there are like, I would love to do something kind of like this.
But what would you say to them?
Basically, I would just say to, you know, just to get started.
If you want to do something like that, just start keeping notes about what you want to present to people, what you want to start creating.
And then you can just slowly roll it out.
You know, a lot of people feel like they have to have this big production setup before they even do their very first, you know, attempt at something like this.
But really, you can just, if you're doing a blog, you can just get on and write up your blog in a text editor and put it out to a site like GitHub Pages or something like that.
Or if you're making videos, as long as you have, you know, you can buy a cheap microphone for about $20.
The first videos I did, I didn't even have a microphone.
So it was just, you know, recorded off my computer.
And people don't mind that stuff as much as you think they would.
So, yeah, just getting started and getting your foot in the door with stuff like that is the best way to go.
Yeah, that's awesome.
I started the podcast with a $55 microphone and $5 worth of software.
So, yeah, yeah.
Yeah.
So it's not as complicated as what a lot of people make it out to be.
It's just getting that first step, taking that first step and just doing it.
I have one other thing to throw out there for people to sort of follow on with that is we live in a world where there are no longer gatekeepers.
Right.
Like, who did you ask permission to start your YouTube channel from?
Oh, yeah, exactly.
Yeah, yeah.
There's nobody.
Nobody, right?
Nobody that you have to check with.
Yeah.
Same here.
And so many of the people who are doing stuff like us, they just decided, I'm just going to do this.
And a lot of people sort of see, you know, I kind of think it's sort of under an undertone in their thinking, not super obvious.
But they feel like I've got to get to some stage where people will accept me and where people are going to kind of like, I'm good enough that some channel or some platform will accept me to do my work.
Not really.
You just got to go out there and get started.
And, you know, there's no gatekeepers.
It's up to you.
Go and do it.
Yeah, I think that's great advice.
Yeah.
All right, Corey, thanks for being on the show.
This is really awesome.
And super congratulations on going full time on this.
That's amazing.
Yeah, thanks a lot.
I really appreciate you having me on.
I have listened to your podcast since probably the first episode and I never thought I would actually be on it.
So it's really cool to be on here.
That's really awesome.
Well, I'm happy to have you.
This is cool stuff you're doing.
So happy to share it.
Take care.
All right.
Take care.
Thanks a lot.
This has been another episode of Talk Python to Me.
Our guest this week was Corey Schaefer.
And this episode has been brought to you by Datadog and Rollbar.
Datadog gives you visibility into the whole system running your code.
Visit talkpython.fm/datadog and see what you've been missing.
Don't even throw in a free t-shirt for doing the tutorial.
Rollbar takes the pain out of errors.
They give you the context and insight you need to quickly locate and fix errors that might have gone unnoticed until your users complain, of course.
As Talk Python to Me listeners, track a ridiculous number of errors for free at rollbar.com slash talkpythontome.
Want to level up your Python?
If you're just getting started, try my Python jumpstart by building 10 apps or our brand new 100 days of code in Python.
And if you're interested in more than one course, be sure to check out the 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, Google Play feed at /play, and 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.
Thank you.