Where to Go Next, All of It Still Free
Okay so here's the thing. This is the last lesson, and I want to spend it telling you where to point yourself once you walk out of here, because "take a class" and "actually keep learning" are two different problems. I've watched people finish a class like this, feel great for a week, and then never open a code editor again. Not because they didn't like it. Because nobody told them what the next small step was.
So let's fix that.
You don't need to buy anything
I'll say this one more time because it matters: you do not need to pay for beginner coding software. The editor you're already using, whatever free one we set up in lesson one, is genuinely enough. People try to sell you "learn to code" platforms with subscriptions and certificates and a little mascot character, and some of it's fine, but none of it's necessary. Everything good is free. Python itself is free. The documentation is free. There are entire free courses from real universities sitting online right now. If somebody's asking you for money before you've written 500 lines of code, that's on them, not on you.
Where to actually go
Here's what I'd do, in order, starting this week:
1. Keep using the same small tools that annoyed you into learning this. Seriously. Don't go looking for a big fancy project. Look at your own life the way I looked at my photo folders. What's boring, repetitive, and slightly infuriating? That's your next script. Mine was renaming files. Camille's was tracking our grocery spending. Yours might be sorting your kid's soccer schedule or renaming vacation photos or something I haven't thought of. Small, annoying, yours. That's the whole formula.
2. Free practice sites, typed by hand, not copy-pasted. There are sites out there with hundreds of little practice problems, free accounts, no credit card. Do a few a week. And I'm going to say this one more time because I've said it all class and I mean it: type the problems yourself. Don't paste in a solution you found. Your fingers learn something your eyes skip right over. It feels slower. It's not, not really, because the stuff sticks.
3. Read other people's code, even when it's confusing. There's a ton of free, real code sitting in public repositories online, written by actual people solving actual problems. Half of it will look like nonsense to you right now and that's fine. Poke at it anyway. You're not trying to understand all of it. You're trying to get comfortable with the feeling of not understanding something yet.
4. Come back to stuff that broke you. This is the part people skip. If a topic in this class made you want to throw your laptop into Utah Lake, that's exactly the thing to revisit in a month. Not because you have to master it. Because it'll make more sense the second time, almost every time, once your brain's had a chance to sit with it.
A word about getting stuck (and Ctrl-C again)
You're going to get stuck out there without me circling the room. That's normal. It's actually the job. I told you guys about the night my while loop ran forever because I forgot to update my counter variable, and I just sat there watching my laptop fan spin up like it was trying to take off. That laptop was not fast to begin with, it was already showing its age, and hearing that fan scream while nothing happened on the screen is a specific kind of dread. What got me out of it wasn't some brilliant insight. It was Ctrl-C. Stop the thing, take a breath, go look at what you actually wrote versus what you meant to write.
That's going to keep happening to you for the rest of your coding life, by the way, whether you do this for fun or turn it into something more. The stuck feeling doesn't go away. You just get faster at recognizing it and calmer about hitting stop.
One last opinion, since it's the last lesson
You do not need to be good at math to keep doing this. I know that's the reputation coding has, and I know some of you walked in here worried about it. It's mostly stubbornness and reading error messages slowly and carefully instead of panicking. That's it. That's most of the job. Anybody willing to sit with a broken thing a little longer than feels comfortable can do this.
Before next time
There isn't a next time, officially, but pick one annoying thing in your actual life this week and write four lines of code toward it. Doesn't have to work. Just has to be a start.
It's been a genuinely good group to teach. Go break something on purpose and then go fix it. That's the whole hobby.