Most people who set out to learn to code stall in the middle: too many tutorials, no projects, no routine. This plan puts a goal first, then fundamentals, then small builds, then one project you finish and show.
It is language-neutral. In week one you pick a path (web, data, apps or automation) and a single beginner course, and the rest follows from that. Weekly practice sessions repeat so the habit is already in your task list.
Copy it into Tatask and the stages are dated from today. Expect months, not weeks, and adjust the pace to the time you really have.
What's in this plan
See every step
Choose your path(day 0)
Write down why you want to learn to code
A clear reason (a career change, a project, automating work) decides what to learn first and helps when motivation dips.
List 3 things you would like to build
Keep them small: a personal site, a budget script, a simple game.
Pick one path to start with
Common starting points: web (HTML, CSS, JavaScript), data and automation (Python), or mobile apps. Choose one and stay with it for the first three months.
Choose one beginner course and bookmark it
Pick a single well-reviewed course or book, ideally free to start. Switching between several is the usual way people stall.
Decide how many hours a week you can commit
Be honest. Four steady hours beat ten that you drop after a fortnight.
Run a one-line "hello world" program. If it prints, your setup works.
Create a free GitHub account
GitHub stores your code and doubles as a record of your progress.
Create a folder for your practice code
Complete a coding practice session(day 7)(repeats weekly)
Repeats on Tuesday, Thursday and Saturday. Aim for 60 to 90 minutes of typing code, not just watching. Change the days to suit you.
Learn the fundamentals(day 14)
Core ideas(day 14)
Complete the lessons on variables and data types
Complete the lessons on conditions and loops
Complete the lessons on functions
Complete the lessons on lists and dictionaries or objects
Practise what you learned(day 45)
Complete 10 small exercises on a practice site
Exercise sites such as Exercism or freeCodeCamp give instant feedback. Retype solutions rather than copying them.
Write a program from a blank file without a tutorial
Try a number-guessing game or a tip calculator. Getting stuck here is the point.
Read your error messages and note 3 common ones
Reading errors calmly is half of programming. Keep a short list of what each one meant.
Learn the basics of Git and make your first commit
Learn to get unstuck(day 60)
Write a short checklist for when you are stuck
For example: reread the error, print values, shrink the problem, search, then ask.
Ask one question on a beginner forum
Include what you tried, the exact error and a small code sample.
Ask an AI assistant to explain one concept you find hard
Use it to explain, not to write your code for you.
Prompt to copy
I am a beginner learning <language>. Explain <concept> in plain words with one short example, then give me a small exercise to try myself. Do not give me the answer until I ask.
Build small projects(day 75)
Choose 3 small projects from your earlier list
Each should be doable in one to two weeks.
Build project one and save it to GitHub
Build project two and add a README explaining what it does
Build project three, then add a feature you invented
Adding something nobody told you to add is where learning sticks.
Review your three projects and note what you would improve
Find a code review buddy or community
A local meetup, an online study group or a friend who codes. Fresh eyes catch habits you cannot see.
Build one portfolio project(day 120)
Choose one project that solves a real problem for someone
Your own needs count. A tool you use yourself is easier to finish.
Write a one-page plan with a minimum version
Define the smallest version that works. Add extras only after that is done.
Break the plan into tasks of two hours or less
Build the minimum version
Test it with 2 other people and note their feedback
Fix the 3 most important problems found
Write a README with screenshots and setup steps
Publish the project online or share the repository
Keep going(day 165)
Choose your next skill from the gaps you noticed
For example databases, testing, or a framework for your path.
Read through someone else's project code for one hour
Update your GitHub profile with your best 3 projects
Review your progress and set goals for the next 3 months
A review with a fresh view can help.
Prompt to copy
Here is what I have learned and built so far: <summary>. My goal is <goal>. Suggest three realistic next steps for the next three months. Do not invent course names, prices or job market figures.