Weekly Timetable Template (Example: Weeks 3-4 -
Data Structures & Loops)
This is a sample structure. You can adapt the specific days to your school
schedule, but try to keep the sequence the same.
Tim
Day Focus Activity Details & Steps
e
Watch the next 2-3
videos in your course
(e.g., 45-
Watch
on for loops). Code 60
Monday LEARN Course
along with the min
Videos
instructor. Pause the s
video and type every
line of code they do.
Complete
exercises only on
yesterday's
45
PRACTIC Targeted topic (e.g., for loops).
Tuesday min
E Exercises Use W3Schools or
s
freeCodeCamp. Do at
least 5-10 different
exercises.
Look at your code from
Tuesday. Why did your
PRACTIC Debuggin errors happen? Fix 45
Wednesd
E/ g& them. Then, try to min
ay
BUILD Review combine concepts s
(e.g., use a for loop with
a list from last week).
Thursday BUILD Project Work on your 60+
Tim
Day Focus Activity Details & Steps
e
weekly Micro-Project
(e.g., the Quiz Game).
Don't try to finish it.
min
Work Just focus on one small
s
part (e.g., today I will
write the code to ask
the questions).
Finish the core
functionality of your
Project project. Get it to work! 60+
Friday BUILD Completio If it breaks, use Google min
n to debug. This is the s
most important
learning step.
Add your finished
project to
GitHub. Write a simple
45
REVIEW GitHub & README explaining
Saturday min
& PLAN Review what it does. Then,
s
quickly preview the
next week's topic in
your course.
Rest your brain. You
Sunday REST - will learn better if you -
take a break.
How to Apply This to Any Week:
1. LEARN Days (1-2 days): Consume new information. Your goal is to
understand the concept.
o Step 1: Watch the course videos.
o Step 2: Code along with every example.
o Step 3: Take handwritten notes in your own words.
2. PRACTICE Days (1-2 days): Reinforce the new concept in isolation.
o Step 1: Go to a practice site (W3Schools).
o Step 2: Complete exercises focused only on that new concept (e.g.,
just for loops).
o Step 3: If you get stuck, search for the error message or concept name +
"example".
3. BUILD Days (2-3 days): Apply the new concept + old concepts to a real
project.
o Step 1: Look at the project idea for the week.
o Step 2: Break the project into tiny steps. (e.g., "Step 1: Print a question.
Step 2: Get an answer. Step 3: Check if it's correct.").
o Step 3: Code one step at a time. Test after each step.
o Step 4: Debug when it inevitably breaks. This is where 90% of learning
happens.
4. REVIEW Day (1 day): Consolidate your learning and prepare for the next
week.
o Step 1: Push your code to GitHub. This is your proof of work.
o Step 2: Skim your notes and the next week's course content.
This timetable ensures you are not just a passive learner but an active
coder. The constant cycle of learning, practicing, and building is the
fastest way to achieve mastery.