Build something real · a full syllabus · one-on-one tutor
Learn it properly.Whatever “it” is.
Learn C by writing a shell, or Rust by building a key-value store. Every course comes with a full syllabus, and the tutor teaches all of it inside the thing you're building, one concept at a time.
- Cost
- Free credits to start
- Setup
- Nothing to install
- Catalog
- 1 courses, 116 lessons
Before lesson one: what do you want to end up with? Anything you'd actually use.
Set up pixel-dodger: a game loop, two sprites and an empty scores.py. Same Python syllabus as everyone else — 41 lessons — taught in here.
Getting started
What the first ten minutes look like.
Three screens, in this order, and then you're in lesson one.
- 01
Find the subject
Search the catalog and read the whole syllabus before you make an account. You get every module and every lesson in the order they come, so nothing behind the sign-in wall is a surprise.
No account needed
- 02
Say what you want to build
The thing you want to end up with. A shell, a game, a scraper for the site you keep checking by hand. It's the only setup question you get.
A short conversation
- 03
Start lesson one
The workspace opens with the starter files for that idea, and the tutor teaches lesson one inside them. Same syllabus as everyone else, taught through what you're making.
Same session
You finish the course with the thing you built.
The workspace above is where the apply step from the lesson at the top of this page happens: same project, same files, opened in the browser with the editor and terminal already running. Dictionaries got taught there because the build in the demo needed them — pick a different one up there and this changes with it, which is the point.
That is the whole method. The syllabus decides what you have to learn, your project decides what each lesson looks like, and you keep the project.
Most of the catalog
A project and a workspace, generated from the idea you described. Editor, terminal and your files, already set up when lesson one opens, and the syllabus taught by building the thing.
Nothing to install
When there's no code
Some subjects here have none, and those courses drop the workspace. You say why you're taking the course, and the same full syllabus gets taught against the problems you came with.
No setup at all
The obvious question
Why not just ask ChatGPT?
For a one-off question, go and do that. The difference shows up over weeks, when you need to finish something and still be able to do it yourself afterwards.
| A general chatbot | codeset | |
|---|---|---|
| Structure | Whatever you think to ask | A full syllabus, in order |
| What it sees | Text you paste in | The work you actually did |
| Progress means | The conversation continued | You worked through the syllabus |
| When you're stuck | It hands you the answer | It finds the gap, then teaches it |
| Tomorrow | Starts over, remembers nothing | Knows exactly where you left off |
| What you end up with | A transcript you'll never reread | The thing you built, and the syllabus behind it |
- Structure
A general chatbot
Whatever you think to ask
codeset
A full syllabus, in order
- What it sees
A general chatbot
Text you paste in
codeset
The work you actually did
- Progress means
A general chatbot
The conversation continued
codeset
You worked through the syllabus
- When you're stuck
A general chatbot
It hands you the answer
codeset
It finds the gap, then teaches it
- Tomorrow
A general chatbot
Starts over, remembers nothing
codeset
Knows exactly where you left off
- What you end up with
A general chatbot
A transcript you'll never reread
codeset
The thing you built, and the syllabus behind it
What we mean by course
Three things have to be true.
Otherwise it's a chatbot with a syllabus stapled to it, and you already have one of those.
The whole syllabus gets covered
What you want out of the course doesn't get to decide what you skip. Every skill in it is placed somewhere, taught through your own work where it fits and bridged with a short exercise where it doesn't.
It looks at the work itself
The tutor reads the files you wrote and the output you got, not your account of them. It responds to what is there, including the mistake you haven't spotted yet.
Reading it isn't finishing it
Every concept goes lesson, then apply it in your project, then a short test you take without the tutor. That last part is what the stars come from, so progress means you could do it unaided rather than that you scrolled past it.
- A window and a loop
- Things that move
- Scores that stick around2/5
- Looping over a list
- Sorting
- DictionariesTeaching
- Saving the high scoreLocked
- Reading a file backLocked
The same course as the lesson above, in the rail the studio keeps beside it. Every lesson with stars was taught inside the project and then tested with the tutor switched off, and the stars are that test's result — so the rail records what you can do unaided rather than what you opened.
Courses
Find yours, then read the whole syllabus.
Every module and every lesson is readable in order, with no account. If a syllabus looks thin, don't take our word for anything else on this page.
Not in the catalog
Then have the tutor write it.
Describe the subject and you get a syllabus back, module by module, to read before you commit to any of it. It costs credits from the same free balance every account starts with, and what comes out is a course like the rest.
The things you'd ask before signing up.
- What does it cost?
- Nothing to start. Every account gets free credits, worth about five lessons or one course you generate yourself, with no card and no trial clock. Past that, plans start at $14 a month, and the pricing page shows what a credit buys before you spend one.
- Is this only for programmers?
- No. Plenty of the catalog has no code in it at all, and those courses work the same way: a full syllabus taught one-on-one, aimed at what you said you wanted from it.
- What if my subject isn't in the catalog?
- Describe it and the tutor writes the syllabus, module by module, before you commit to any of it. Generating a course costs credits from the same free balance every account starts with, and what comes out is a course like the others: readable in full, and yours to start or discard.
- Will it just hand me the answer?
- It's built not to. When you get stuck it looks for the thing you've misunderstood and teaches that instead of pasting in a fix. It isn't flawless at this, but it's what the whole tutor is tuned around.
- Do I have to install anything?
- No. Courses with code run in a workspace in your browser, with the editor, terminal and files already set up when the first lesson opens. Courses without code need no setup at all.
- How much time does it take?
- One lesson at a time, and it holds your place exactly. Come back a week later and the tutor picks up mid-thought instead of asking you to explain your project again.
- What's still rough?
- It's early. Some courses go deeper than others, the tutor gets things wrong now and then, and the coding workspace still needs a laptop, though lessons and the tutor work on a phone. You'd be an early user, with everything that means.
Early access
Judge it by the syllabus.
codeset is early, and the honest version of this pitch is the thing itself: a tutor that reads the files you wrote, and a full syllabus taught inside what you're building. Find your subject, read its syllabus end to end without an account, and if it holds up you'll have started building in ten minutes.