What Python is, and what it is actually used for

Before you install anything, it is worth ten minutes to understand what you are about to learn and — just as importantly — what it will not do for you. A lot of people spend six months on a language that was never going to get them where they wanted to go.

What Python actually is

Python is a programming language: a set of rules for writing instructions that a computer can carry out. You write plain text in a file, and a program called the interpreter reads that file line by line and does what it says.

That "line by line" part matters. Some languages, like Java or C++, must be compiled first — translated in one go into a file the machine can run. Python skips that step. You save the file, you run it, you see the result. When you get something wrong, you find out in seconds rather than after a build.

This is the single biggest reason Python is a good first language. The loop between "I wonder what this does" and "oh, that is what it does" is very short, and that loop is how you actually learn.

The trade-off is speed. Python is slower than compiled languages — often ten to a hundred times slower for raw number-crunching. For almost everything you will build, this does not matter: your program spends its time waiting for a network request or a database, not calculating. When it does matter, people write the slow part in C and call it from Python, which is exactly how the popular data libraries work.

What people really build with it

Python is genuinely used, at scale, for these:

Web backends. The server behind a website or an app — the part that handles logins, stores data and returns results. Instagram runs on Python. Spotify uses it. Django and FastAPI are the main tools, and Django is the subject of a later course here.

Automation and scripting. Renaming four thousand files, pulling a report from one system and pushing it into another, checking whether a site is up every five minutes. This is the least glamorous use and quite possibly the most valuable one early in a career. It is also the fastest way to make yourself useful at a first job.

Data analysis. Reading messy spreadsheets and CSV files, cleaning them, producing numbers somebody can act on. Pandas is the standard tool.

Machine learning and AI. Essentially the whole field runs on Python. PyTorch, TensorFlow and scikit-learn are all Python libraries.

Testing and infrastructure. Test suites, deployment scripts, and the tooling that keeps production systems running.

What it is not for

Being straight with you saves you time later:

• Mobile apps. You will not write a serious Android or iOS app in Python. Android is Kotlin or Java; iOS is Swift. If a native mobile app is your goal, the Kotlin course on this site is the honest starting point.
• Front-end web. The code that runs inside the browser is JavaScript. Not Python. If you want to build interfaces, you need JavaScript eventually — the Web UI and JavaScript courses cover it.
• Games with demanding graphics. Possible, rarely sensible.
• Anything where microseconds count. High-frequency trading, operating systems, device firmware.

Notice that "web development" appears on both lists. That is not a contradiction: Python does the server, JavaScript does the browser. Most full-stack developers use both every day.

Why start here

If your goal is mobile, you could reasonably start with Kotlin instead. For almost everything else, Python first is the right call, for three reasons.

The syntax stays out of your way. Compare printing a line of text in Java:

public class Main {
    public static void main(String[] args) {
        System.out.println("Hello");
    }
}

against the same thing in Python:

print("Hello")

Every word in the Java version means something real, and you will learn what each one is for if you take the Java course. But when you are learning your first language, those words are noise — you are trying to understand loops and conditions, not class declarations and access modifiers. Python lets you learn one idea at a time.

Second, what you learn transfers. Loops, conditions, functions, data structures, and the habit of breaking a problem into steps — these are the same in every language. Once you genuinely know them in Python, picking up Java or JavaScript is a matter of weeks, not months.

Third, it keeps doors open. Web backend, automation, data and AI are all reachable from here.

Version 3, not version 2

You will find old tutorials written for Python 2. Ignore them. Python 2 reached end of life in 2020 and is gone. Everything in this course uses Python 3.12 or newer.

The quickest way to spot a Python 2 tutorial: it writes print "Hello" without brackets. If you see that, close the tab.

Where this course takes you

By the last module you will have built a working command-line expense tracker that stores data in a file, handles bad input without crashing, has tests, and lives in a Git repository you can show someone. Not a toy — a small, complete, honest program.

Along the way you will get the things tutorials usually skip: how to read an error message, how to debug when you are stuck, how to set up a project properly, and how to tell when your code has become a mess.

Practice

No code for this one. Two things instead:

1. Write down, in one sentence, what you want to be able to build. Be specific: "a website that tracks my expenses" beats "become a developer". Keep it somewhere you will see it. Around week three, when a bug is not making sense, that sentence is what gets you back to the keyboard.

2. Decide when you are going to work on this. Not how many hours a week — which hours. Forty-five minutes at a fixed time beats a heroic six-hour Sunday that happens twice and then stops. Consistency is doing the work here, not intensity.

Next: getting Python onto your machine.