Learn Programming from Zero: A 90-Day Plan for Beginners

Before you start

You do not need a special computer, a maths genius brain or expensive courses. You need a laptop, an internet connection and a daily habit. The most common reason beginners quit is not difficulty; it is inconsistency and tutorial hopping. This plan gives you a clear sequence so you always know what to do next.

Time needed: 1.5–2 hours a day, six days a week. If you have less time, stretch the plan to 120 days. Consistency beats intensity.

Choose your first language (day 1)

Pick one and commit for at least 90 days.

• Python: easiest to read, great for beginners, data and automation (Python guide)
• Java: widely used for placements, backend and Android (Java guide)
• JavaScript: the language of the web (essentials)
• C or C++: good for understanding how computers work, common in college curricula

If unsure, start with Python. The ideas transfer to every other language.

Days 1–30: the fundamentals

Learn these in roughly this order, and write code for every concept, not only watch:

1. Setting up: install the language and a code editor (VS Code is a good free choice)
2. Printing output, variables and data types (numbers, text, true/false)
3. Reading input from the user and basic maths
4. Conditions (if, else) and comparison operators
5. Loops (for, while) and the idea of repetition
6. Functions: write your own, pass values, return results
7. Lists or arrays, and strings in depth
8. Dictionaries or maps, and sets
9. Reading and writing files; handling errors

Daily practice: 2–3 tiny problems. Examples: check if a number is even, print a multiplication table, count vowels in a word, find the largest in a list, reverse a string.

Days 31–60: thinking like a programmer

• Break every problem into steps on paper before you code
• Learn to debug: read error messages, use print statements, then a debugger
• Solve 40–60 easy problems on a site such as HackerRank, Codeforces practice or LeetCode's easy list
• Learn the idea of complexity: why one solution is faster than another
• Basic data structures: stacks, queues, linked lists (the DSA study plan continues from here)
• Learn Git so your work is saved and visible (guide)

Days 61–90: build something real

Choose a project that is small enough to finish and useful enough to care about:

• A command-line expense tracker that saves data to a file
• A quiz game with scores
• A to-do list app (console first, web later)
• A web scraper or API app that shows live data, such as weather or exchange rates

Finish it, add a README explaining what it does and how to run it, and push it to GitHub. Then improve it for another week. This single finished project teaches more than ten unfinished tutorials. For ideas on what recruiters like, see portfolio projects that get interviews.

How to study well

• Type the code yourself. Copy-pasting teaches nothing.
• Struggle before looking for answers. Try for 20 minutes, then read hints, then solutions. Afterwards, write it again from memory.
• Keep a notebook of mistakes and patterns you discovered.
• Explain concepts out loud to a friend or an imaginary student.
• Use one main resource at a time: a single course or book plus the official documentation.

Good free resources: CS50, freeCodeCamp, the official Python tutorial, Java's official tutorials, MDN Web Docs and the Odin Project.

Common mistakes

• Changing languages every two weeks
• Watching ten hours of video without writing code
• Skipping fundamentals to learn frameworks
• Comparing yourself with people who started years earlier
• Never finishing a project

After 90 days

You will not be job-ready yet, and that is normal. Continue with the software developer roadmap for freshers, focus on data structures, databases and projects, and look at internships as an early step.