Python Basics

Explore & Discover

Before writing a single line of Python, spend a few days just exploring what Python actually does in the real world. NASA uses it to process Mars rover data. Spotify uses it to recommend songs. Utah-based companies like Pluralsight use it for their learning platforms. Go to python.org and read the "Success Stories" page. Watch "Python in 100 Seconds" on YouTube (free, under two minutes). Then open Python.org's interactive shell in your browser — type a few math expressions and see what happens. You're not learning syntax yet, just getting curious about what's possible. You're ready for the next step when you can name three real-world things Python is used for and explain why that's interesting to you.

Learn the Basics

Head to Python.org and install Python 3 (free), then grab VS Code (also free) as your editor. Work through the first three chapters of "Automate the Boring Stuff with Python" by Al Sweigart — the whole book is free at automatetheboringstuff.com. Focus on variables, strings, numbers, if/else statements, and loops. Write at least ten small programs: a temperature converter, a name greeter, a simple calculator. Don't copy-paste — type everything out by hand so your fingers learn the patterns. Run each program and fix whatever breaks. You're ready for the next step when you can write a program from scratch that uses variables, an if/else block, and a for or while loop.

Build Your First Project

Build a text-based quiz game in Python. It should ask the player five questions, keep track of their score, and print their result at the end. Make the questions about something you actually care about — Utah geography, your favorite game, a sport, whatever. You'll need: a list to store questions, a loop to go through them, if/else to check answers, and a variable to track the score. Use the Python docs at docs.python.org (free) if you get stuck on syntax. No graphics yet — just text in the terminal. This one project uses almost every basic concept you've learned. You're ready for the next step when your quiz runs without errors and correctly tracks and reports the score.

Experiment & Iterate

Now make your quiz game better — three times. First, add a timer so players only have 10 seconds per question. Second, add a high score that saves to a text file so it persists between plays. Third, randomize the question order each time. Each of these additions will break something — that's the point. Read the error messages carefully. Python's error messages are actually pretty helpful if you slow down and read them word by word. Use Stack Overflow and the Python docs to debug. Keep a short "bug log" — one sentence per bug describing what it was and how you fixed it. You're ready for the next step when all three improvements work and you can explain what each one does.

Advanced Techniques

Level up with functions, dictionaries, and basic file handling. Functions let you write code once and reuse it. Dictionaries let you store structured data — like a question paired with its answer and point value. Read chapters 8 and 9 of "Automate the Boring Stuff" and try the exercises (all free). Then refactor your quiz game: replace your question list with a dictionary, put your game logic into functions, and add a feature that loads questions from an external text file so you can swap question sets without touching the code. This is how real software is built — separating data from logic. You're ready for the next step when your quiz uses at least three functions and loads questions from a separate file.

Final Project Showcase

Build a final Python project that's different from the quiz — your choice. Ideas: a weather lookup tool using a free API, a word frequency counter for a book, a simple address book that saves contacts to a file, or a mini text adventure game. Whatever you pick, it needs to use functions, at least one data structure (list or dictionary), and read or write a file. Write a short README explaining what your program does and how to run it. Share your code on GitHub (free account) — even one public repo is a huge deal at your age. You're ready for the next step when your project is complete, runs without errors, and is posted publicly on GitHub.