Programming fundamentals · Beginner · 12 min
Choose your first programming language
By Padding · Updated 18 Nov 2026
Any computer or phone · November 2026
You will turn what you want to build and the limits you work within into one chosen language and a dated four-week plan built from our tutorials.
On this page
Most people who ask "which language should I learn first?" are hoping for a single winner. There isn't one, and asking for one tends to stall you for weeks while you read arguments online. What you can do is make a choice that fits you: what you want to build, the machine you have, the data you can afford and any course you are already enrolled on.
This guide works like a short worksheet. You write your goal down, list your limits, shortlist two or three languages from the goal lists below, cross out the ones your limits rule out, and commit to one. You finish with a plan for the next four weeks, built from tutorials on this site, and a date on which you will review it.
One thing to know before you start: the first language is the hard one. Variables, decisions, loops, functions, reading error messages and breaking a problem into steps are the same ideas in almost every language. When you learn a second language you are mostly learning new spelling for things you already understand, so it usually takes a fraction of the time. Picking a "wrong" first language costs you far less than not starting.
Step 1 · Write down what you want to build
Open your notebook or a new notes file and give it the title "My first language". Underneath, write one sentence that starts "In three months I want to have built..." and finish it with a real thing, not a job title.
Some examples:
- "...a website for my mum's catering business that shows the menu and takes enquiries."
- "...a script that combines our shop's weekly sales spreadsheets into one report."
- "...an Android app that tracks my savings goal."
- "...a small 2D game my younger brother can play."
- "...a program that answers questions about my course notes."
If you have several ideas, write them all, then circle the one you would be most annoyed not to finish. Motivation carries beginners further than any technical advantage a language has, so the thing you care about wins.
If you genuinely have no project in mind and want to learn programming in general, write "general: I want to understand how programs work". That is a valid answer, and Step 3 has a list for it.
Check it worked
Your note has one circled sentence that names something a person could use or look at, such as a site, a report, an app or a game. If your sentence is "become a developer", rewrite it as a thing you would build.
Step 2 · List your constraints
Under your goal, write a heading "Limits" and answer each of these questions honestly in a few words:
- Computer. What do you have? Write the RAM and free disk space if you know them. On Windows, RAM is under Settings, System, About and free space under Settings, System, Storage. On a Mac, RAM is under Apple menu, About This Mac and free space under System Settings, General, Storage. "Old laptop, 4 GB RAM" or "no computer this month, phone only" are both useful answers.
- Operating system. Windows, macOS, Linux, ChromeOS or Android.
- Data. Do you have unlimited broadband, or prepaid mobile data that you top up? Roughly how much can you spend on downloads this month?
- Time. How many hours a week can you really give this? Three focused hours are better than a promised fifteen.
- Course or job. Is a school, bootcamp, university module or employer already asking for a specific language? Write its name and the date it starts.
- People. Does a friend, colleague or study group already use a language and offer to help?
On prepaid data, plan downloads before you choose. Some languages need a few tens of megabytes to get started, while others need gigabytes of tools. Where you can, download installers once on a free or cheaper connection (a library, office or campus Wi-Fi), keep the installer file, and copy it to other machines with a USB stick instead of downloading again.
Check it worked
Your "Limits" list has an answer for all six questions, even if the answer is "none". You should be able to read it back and say which of the questions actually restrict you.
Step 3 · Shortlist two or three languages for your goal
Find your goal below and copy its languages into your note under a heading "Shortlist". Each entry says why it fits and links to the Hello World page for that language, where you can see what writing it feels like. Pick at most three. Every language and editor named on this page is free to download and use, so cost should not decide your choice.
Websites and web apps
- JavaScript. The only language every web browser runs, so any interactive page uses it. With Node.js it also runs servers, so one language covers both sides. Hello World in JavaScript.
- HTML and CSS first, alongside JavaScript. These are not programming languages but you cannot build a page without them. Learn them in the same weeks as JavaScript. Build a button in HTML and CSS shows the shape of the work.
- PHP or Python for the server side. PHP is long established on the web and most shared hosting plans support it. Python powers frameworks such as Django. Hello World in PHP, Hello World in Python.
Data analysis and reports
- Python. Reads spreadsheets and CSV files, cleans data and draws charts with free libraries such as pandas. Hello World in Python.
- SQL. The language for asking questions of databases. Almost every data job uses it, and it pairs with whichever other language you pick. Hello World in SQL.
- R. Built for statistics, and common in research, public health and universities. Hello World in R.
Mobile apps
- Kotlin. The main language for Android apps, and the one Google's Android documentation and courses teach. Hello World in Kotlin.
- Dart with Flutter. One codebase for Android, iOS and the web. Hello World in Dart, then install Flutter.
- JavaScript with React Native. Useful if you also want websites, since the language is shared. Create your first Expo app.
- Swift. For iPhone and other Apple devices. It needs a Mac, because Xcode only runs on macOS. Hello World in Swift.
Automating everyday tasks
- Python. Renames files, fills spreadsheets, sends emails and talks to web services with short, readable scripts. Hello World in Python.
- PowerShell. Already on Windows, and strong for managing Windows machines and Microsoft 365. Hello World in PowerShell.
- Bash. Already on Linux and macOS, and the glue of servers and build scripts. Hello World in Bash.
Games
- C#. Used for scripting in widely used game engines, including Godot. Hello World in C#.
- Lua. A small language embedded in many games and game tools for scripting. Hello World in Lua.
- Python. Good for learning game logic with simple text or 2D games before moving to an engine. Build a number guessing game in Python.
Backend services and AI apps
- Python. The common language of machine learning libraries and of most AI model SDKs and examples. Hello World in Python.
- JavaScript or TypeScript on Node.js. Popular for APIs, and you can share code with a web front end. Hello World in JavaScript.
- Go or Java. Common in larger companies for long-running services. Hello World in Go, Hello World in Java.
General: understanding how programs work
- Python, because its short, readable syntax lets you focus on ideas rather than punctuation, or JavaScript, because you can see results in a browser you already have. Read what happens when you run a program whichever you choose.
Check it worked
Your "Shortlist" heading has two or three language names, each with a reason in your own words copied or adapted from the lists above. If you have more than three, cut the ones whose Hello World page you liked least.
Step 4 · Cross out what your constraints rule out
Now read your "Limits" list against the shortlist and strike through any language that a limit blocks. Work through these rules in order:
- A course or employer names a language. It wins. Cross out the others for now. Learning a different language in parallel with a course that uses another one splits your attention at the worst time.
- Phone only. You can still learn. On Android, Termux gives you a Linux terminal where Python and Node.js install through its package manager, so Python and JavaScript stay on the list. Cross out Kotlin with Android Studio, Swift and engine-based game development until you have a computer. Termux does not exist on iPhone, and an iPhone alone is a poor setup for this plan: borrow time on a computer at a library, school, office or cyber cafe for your practice sessions, and use the phone for reading tutorials in between.
- Old or low-memory laptop. Android Studio is a heavy download (the Windows installer alone is listed at 1.5 GB) and pulls in more during setup, and an Android emulator needs plenty of RAM. On a machine with 4 GB of RAM, prefer Python, JavaScript, SQL, Lua or Bash, which run well with a light editor such as VS Code (under 200 MB to download).
- Swift for iPhone apps without a Mac. If your goal is an iPhone or other Apple app, cross Swift out: building those needs Xcode, which only runs on macOS. Swift itself also runs on Linux and Windows, so it can stay if your goal is general learning.
- Tight prepaid data. Favour the languages with small downloads (Python, Node.js, SQLite for SQL, Lua). If you still want mobile, plan the large downloads for a free Wi-Fi session and write that date in your note.
- A helper. If someone near you offers regular help in a language that is still on your list, give it extra weight. A person who can look at your error message in five minutes saves hours.
Check it worked
At least one language on your shortlist has a line through it, or you have written next to each surviving one which limit you checked it against. If everything was crossed out, go back to Step 3 and add Python or JavaScript, which survive every limit above except a course that names another language. The exception is a reader with only an iPhone: you need borrowed computer time first, as rule 2 says.
Step 5 · Commit to one language
If one language is left, that is your choice. If two or three are left, use these tie-breakers, in order, and stop at the first one that decides:
- Which one appears under the most goal headings in Step 3 (Python and JavaScript each appear under several)? Pick it, because it keeps more goals open if yours changes.
- Which Hello World page did you understand most of on a first read? Pick it.
- Still tied? Pick Python if your goal is data, automation, AI or "general", and JavaScript if your goal involves anything a person sees in a browser.
Write your choice at the top of the note in capitals, with today's date, for example "PYTHON, chosen 19 November 2026". Then write one more line: "I will not switch before" followed by the date four weeks from today.
That second line matters. Every language gets frustrating around the second week, when the first easy wins are behind you and errors start piling up. That frustration is learning, not a sign that the language is wrong for you, and switching resets you to the beginning of the same difficult patch in a new language.
Check it worked
The top of your note shows one language name, today's date and a "no switching before" date exactly four weeks away.
Step 6 · Write a four-week plan from our tutorials
Under your choice, write four headings, "Week 1" to "Week 4", each with its start date. Under each, list two or three tutorials and the hours you will spend. Fit the hours to the time you wrote in Step 2.
If you chose Python, you can copy this plan, which follows the learn to program from zero series and builds a budget tracker you can use:
- Week 1: Hello World in Python, use the terminal as a programmer, start a budget tracker with variables and print.
- Week 2: record what you spend from the keyboard, warn when spending goes over budget, keep asking for expenses with a while loop.
- Week 3: store expenses in a list and show a summary, organise the budget tracker into functions, save expenses to a CSV file and load them back.
- Week 4: handle bad input and finish the budget tracker, make your first Git commits, then your own project from Step 1.
If you chose JavaScript:
- Week 1: Hello World in JavaScript, use the terminal as a programmer, build a button in HTML and CSS.
- Week 2: declare variables with let and const, work with arrays: map, filter and reduce.
- Week 3: use JavaScript modules with import and export, build a to-do list command-line app in Node.
- Week 4: write tests with the Node test runner, make your first Git commits, then your own project from Step 1.
For any other language, Week 1 is its Hello World page plus use the terminal as a programmer. For Weeks 2 and 3, work through the programming fundamentals tutorials on this site, translating the examples, or follow the Python plan alongside: the ideas carry over. Week 4 is always version control and a first step on your own project.
Write down the downloads each week needs, too. Installing the language and an editor happens in Week 1, so if you are on prepaid data, that is the week to find free Wi-Fi.
Check it worked
Your note has four dated weeks, each with at least two linked or named tutorials and a number of hours. Week 4 ends with a task from your own goal sentence in Step 1.
Step 7 · Set your review date and what you will judge
On the "no switching before" date, you will review your choice. Write three questions in your note now so you answer them honestly then:
- Did I finish at least three of the planned tutorials?
- Can I write a short program, such as a loop over a list with an if inside, without copying it?
- Is the language still a good match for the goal I wrote in Step 1, or did the goal change?
If the answers are yes, yes and yes, keep going with the same language for another month and start your project in earnest. If the goal changed (you started with data and found you love building pages), switching is reasonable, and you will notice how much faster your second language goes because the ideas are already in your head. If you finished fewer than three tutorials, the problem is usually time, not the language: cut your plan down before you change anything else.
Put the review date in your phone's calendar with a reminder, and tell one person what you chose. Saying it out loud makes it more likely you will still be at it in four weeks.
Check it worked
Your calendar shows a reminder on the review date, and your note ends with the three review questions.
Next steps
Start Week 1 today with the Hello World page for your language: Hello World in Python or Hello World in JavaScript, or the page you linked in your shortlist.
Before or alongside it, read what happens when you run a program to see how the text you type becomes something a computer does, and write pseudocode before you code to practise breaking your Step 1 goal into small steps in plain language.
Part of these paths
Related tutorials
- Hello World in Python: the interpreter, input and your first scriptYou will print Hello World in the Python 3.15 interpreter, save and run it as a script, greet a person by name from the keyboard and from the command line, and know what Python does with your file when it runs.
- Hello World in JavaScript: run it in the browser and in Node.jsYou will run JavaScript in a browser console and in a web page, install Node.js 26 LTS, write and run hello.js, greet a name passed on the command line, and turn the folder into an npm project with a start script.
- What happens when you run a program: source code, compilers and interpretersYou will build and run the same small program in C, Java and Python, look at the files each route leaves on disk, and be able to explain source code, compiler, interpreter, runtime and executable in your own words.
Need this done for you?
Padding does this work for growing companies, from the first diagnosis to a system that keeps working.
Get new tutorials