{module 1}
How Leet School works
Orientation15 min read
What you will be able to do
- Describe what you do in one lesson, one week and one project.
- Say what makes a lesson complete, and what finishing the Free Track gives you.
- Plan a week of study that fits the hours you really have.
Why it matters
Abiba runs Volta Grill, a grill restaurant in Tamale, Ghana. She wanted to learn to build her own menu page, so she followed a series of free videos. She watched for three weekends. The videos made sense while they played. When she opened an empty file on Monday, she could not write the first line.
Watching is not the same as doing. There are no videos and no live classes. You read, then you answer, build, and explain what you did in your own words. If you know how the parts fit together before you start, you will not waste your first week guessing.
The idea
The school has three loops. A small one for each lesson, a larger one for each week, and one for each project.
The lesson loop
Every lesson has the same four steps.
- Read. A lesson is text, and from module 1 on it also has code. It takes about 20 minutes to read. From module 1 on, read it with your editor open, and type the examples yourself.
- Answer. Three multiple choice questions about what you just read. They are marked at once. If you get one wrong, you see why, and you can try again. A correct first attempt earns more points than a later one.
- Do. Two to four tasks on your own computer. Each task ends with the words "You are done when", so you can check your own work. You tick each task when it is done.
- Write. A short learning log. Five prompts ask what you learned, what was hard, how you got past it, what changed in what you believe, and what you look forward to. One more prompt is about the lesson itself. A few seconds after you save, you get a short reply that says what worked in your writing and two things to improve next time.
A lesson is complete when you have read it to the end, answered the three questions and saved your log.
The weekly loop
Lessons are grouped into modules. A module's five lessons, weekly check and weekly article are about six hours of work. Its project adds 2 to 8 hours, as its brief says. A "week" here is an amount of work, not a date. At five hours a week, a module takes you two to three calendar weeks, and that is fine.
A module has five lessons. Then it has three more things.
- The weekly check. Three to five questions that you answer by typing. They ask you to explain, compare, find a fault or make a decision. You get a score and written feedback on each answer straight away.
- The weekly article. One longer piece of writing about the week. You publish it twice, once on LinkedIn and once on your blog, and hand in the text and both links.
- The project. Real work for an invented client. The next section explains it.
Every seven days, counted from the day you started the course, you also get a weekly report. It says what went well, which topics to study again (with links to the exact lessons), and one goal for the coming week. It appears on your dashboard and arrives by email.
The project loop
Every module ends with a project. A project is written as a brief from a business: who they are, what they need, what limits they have and when they need it.
- You build it.
- You tick a checklist of what must be right.
- You hand in three things: a link to your work on GitHub, a link to the live page, and a short report written for the client.
- The platform runs automated checks. Is the work public? Does it have a README, which is the page that explains a project? Was it built in real steps? Does the live link load?
- You get written feedback on what is solid, what is missing and what to improve first.
- If you want, you can ask another learner on your course to review it.
A project is complete when the automated checks pass and your checklist is done. You can improve it and hand it in again as often as you like.
Feedback written by AI
The replies to your logs and the feedback on your checks, articles and projects are written by AI. The school can switch this feedback off for the Free Track. If it is off, the platform says so. Your work is still saved and still counts, the three questions are still marked, and the project checks still run, because code does all of those.
Points and streaks
You earn points for the things that make you better: finishing lessons, correct answers, tasks, logs, weekly checks, articles, projects and reviews of other learners' work. A streak counts the days in a row on which you did some learning. Each course has a leaderboard, and you can leave it in your settings. Points are there to show progress. They never decide anything else.
What the Free Track is
The Free Track is free. It is this orientation and five modules: 30 lessons and 6 small projects. You need a browser, a free editor called Visual Studio Code, and GitHub's website. There is no terminal and nothing else to install.
There is no certificate. You have finished the Free Track when every lesson is complete, every weekly check is attempted and every project is complete. What you have then is real and you keep it:
- six small projects online in your own GitHub account, which anyone can open
- your learning logs and articles, a record of what you learned and how
- a clear view of whether this work suits you, based on facts and not on guessing
Plan for about eleven or twelve hours a module, about 60 hours in all: three months at five hours a week. There are no deadlines, so you can go faster or slower.
Worked example
Here is Abiba's plan for one module. She can study five hours a week, and the project brief says 5 hours.
| When | Time | What she does |
|---|---|---|
| Week 1, Monday | 1 hour | Lesson 1: read, answer, do the tasks, write the log |
| Week 1, Wednesday | 1 hour | Lesson 2 |
| Week 1, Friday | 1 hour | Lesson 3 |
| Week 1, Saturday | 2 hours | Lessons 4 and 5 |
| Week 2, Monday | 30 minutes | The weekly check |
| Week 2, Wednesday | 1 hour | The weekly article |
| Week 2, Saturday | 3.5 hours | The project, first part |
| Week 3, Saturday | 1.5 hours | The rest of the project |
That is eleven and a half hours, five of them for the project.
Three things make this plan work. Each weekday has one lesson and nothing else, so a bad day costs one hour, not the week. The project gets long sittings, because building needs unbroken time. And she never plans more than her five hours in one week.
Common mistakes
Reading without typing. The examples look clear on the page. Then the task asks for the same thing and nothing comes. From module 1 on, type every example. Change one word and look at the result again.
Skipping the log on a hard day. The log matters most on the day that went badly. "I did not understand the box model and I still do not" is a good log. It tells your weekly report what to send you back to.
Saving the project for later. A project started weeks later is rushed, and half the module is forgotten. Start it soon after lesson five.
Chasing points. Guessing at questions to move up a leaderboard teaches nothing, and the weekly check will show it. Use points as a mirror, not as a goal.
Think it through
Rafael works shifts in a hotel in Lisbon. Some weeks he has eight free hours and some weeks he has two. How should he plan?
Understand. The problem is not "find eight hours". It is "keep moving when the hours change every week".
Break down. A module has parts of different sizes: five lessons of about an hour, a check of about half an hour, an article of about an hour, and a project of two to eight hours.
Plan. In a short week, do lessons only, because each one fits in an hour. Keep the project for a long week, because it needs a longer sitting.
Build. Rafael writes next week's plan on Sunday evening, when he knows his shifts: which lesson on which day, and where the long sitting goes.
Test. After two weeks he checks. In the short week he planned two lessons and finished one.
Reflect. He planned for his best day, not his normal day. Next time he plans one lesson in a short week and treats a second as extra.
At work
A professional plans the week before it starts. Clients do not pay for hours. They pay for things that are finished by the day you said. The habit behind that is small: once a week, write down what you will finish, look at the time you really have, and cut the list until it fits.
A developer who works for clients might write this on a Monday morning:
This week: finish the booking form (2 days), fix the email bug (half a day), send the status report on Friday. Not this week: the new colour scheme.
The last line is the important one. Saying what you will not do is how you keep the promise about what you will do. Your weekly plan for this course is practice for exactly this.
Your tasks
Task 1: Find your hours
Open a calendar or take a sheet of paper. Mark every hour next week that is already taken by work, family, travel and sleep. Count the hours that are left and that you could protect.
You are done when you have one number: the hours you can study next week.
Task 2: Write your plan for one module
Make a table like Abiba's. Put one lesson on each of five days. Put the weekly check, the article and the project in your longest free periods, with the hours the project brief gives. If the total is more than your number from task 1, let the plan run into later weeks.
You are done when every part of one module has a day and a time, and no week in the plan has more hours than your number from task 1.
Task 3: Decide what to do on a bad day
Write one sentence that starts "If I miss a day, I will". Make it something small and exact, such as moving that lesson to Saturday morning.
You are done when the sentence is written at the top of your plan.
Recap
- A lesson is read, answer, do, write. It is complete when you have read it, answered the questions and saved your log.
- A module is five lessons, a weekly check, a weekly article and a project: about six hours, plus the hours in the project's brief.
- A project is a client brief. It is complete when the automated checks pass and your checklist is done.
- The Free Track has no certificate. You finish with six projects online, your logs and articles, and facts about whether this work suits you.
- Plan the week before it starts, and plan for a normal day.
Go deeper
- The Learning Scientists: retrieval practice explains why answering questions teaches more than reading again.
- The Learning Scientists: spaced practice explains why one hour a day beats five hours on Sunday.
- MDN: Research and learning gives advice on how to study web development on your own.