Getting RoseCode ready…
Guide
What the app is for, what each page does, and what actually counts as progress. Ten minutes here saves a lot of wandering.
Start here
RoseCode is built around finishing, not collecting. One lesson you can explain beats five you skimmed. Every page below exists to support that one habit.
The shape of every lesson
Four actions, always in this order. Skipping straight to Test is the most common mistake, and the reason ideas do not stick.
You meet an idea as a big statement, an analogy, plain English, then precise engineer wording. Reading is the cheap part; the teach-back at the end is where you find out whether it stuck.
You predict what happens before you are told, then walk a real path through browser, server, and database. A wrong prediction is the useful kind of wrong — it shows you exactly which step you had backwards.
Practice labs run deterministic checks. Hints are available and cost nothing except a sooner review. Breaking something on purpose teaches as much as fixing it.
You explain the idea from memory, connect it to a real project, answer it as an interview question, and meet it again on a schedule until it holds.
Inside one lesson
Every lesson uses the same fifteen sections in the same order, so you always know where you are and what is coming. Jump between them from the rail beside the lesson.
The big idea
One sentence worth carrying out of the lesson.
Picture it
An analogy, plus where the analogy stops being true.
Plain English
The idea with no jargon in the way.
Engineer mode
The same idea in the words a team would actually use.
Why it exists
The problem it solves, and what you gain.
See it
A small code sample. It is shown as text and never runs here.
Predict
Commit to an answer before the explanation appears.
Try it
A lab with a deterministic check and three progressive hints.
Break it safely
A second lab where you cause the failure on purpose.
Trace it
One scenario followed step by step across boundaries.
Where it appears
Places you will genuinely run into this.
Common confusion
The two things people mix up, and the distinction.
Say it like an engineer
A model answer for standups and interviews.
Teach it back
Write the explanation from memory. Checked against authored key points.
Review card
The idea is scheduled to return before you forget it.
Every page, and when to open it
One suggested next step plus a short daily plan.
Open this first. If you only have ten minutes, do what it says.
Open Today →All 12 stages and 251 topics, labelled honestly.
When you want the whole picture, or to see what is written and what is still planned.
Open Learning path →The 10 complete lessons, each with the same fifteen sections.
For the main work. Nothing is locked — order is a suggestion.
Open Lessons →20 challenges with checks that either pass or do not.
When you want proof rather than a feeling that you understood.
Open Practice labs →19 recall cards on a schedule that reacts to your confidence.
Daily, briefly. Answer from memory before revealing anything.
Open Review →103 terms and 18 comparisons for words that sound alike.
The moment a word stops you. Also drill it directly to close the gaps.
Open Glossary →36 questions with thirty-second and two-minute formats.
Once an idea is solid. Saying it out loud finds the soft spots.
Open Interview practice →Links to public event sites, plus your own planning and recap notes.
When you want people, not more screens. An event counts once you record what happened.
Open Community →A real codebase to investigate, plus 11 capstone briefs.
When lessons start feeling abstract and you want a real system to point at.
Open Projects →20 outside courses and references you track by hand.
To keep one or two outside guides moving. Opening a link never marks progress for you.
Open Resources →A brief about where you are, assembled locally for you to review and share.
When you want to ask an AI for help without pasting your whole history.
Open Tutor bridge →The evidence behind every claim the app makes about you.
When you want to check the app is not flattering you.
Open Progress →Appearance, accessibility, backup and restore, account, and reset.
Set the theme once. Come back to export a backup.
Open Settings →No participation trophies
This is evidence
This is not
This is why a lesson can stay unfinished after you have read all of it — and why Progress shows the evidence rather than a number it made up.
Suggested rhythm
Adjust the amounts to your pace in Settings. The order matters more than the hours.
Most days · 15 min
Clear the due review cards first while your memory is cold. Then move one lesson forward by a section or two. Stop while it still feels easy.
Twice a week · 45 min
Take one lesson all the way through both labs and the teach-back. A finished lesson is the unit that actually moves you.
Weekly · 30 min
One interview question spoken aloud, and one trace through a real project. This is where knowing turns into being able to explain.
Move faster
The command palette searches every lesson, lab, glossary term, and interview question at once.
On a phone, use the search field at the top of the Lessons and Glossary pages instead.
Where your work lives
Everything saves locally as you go. No account, no server, works offline. It belongs to this browser profile, so clearing site data removes it.
Sign in and the same progress follows you. The badge in the corner always tells you which of the two you are currently getting.
Account settings →Export a JSON backup any time, and restore it later after a review step. There is also a readable Markdown summary of what you have learned.
Download a backup →Common questions
No. Everything works signed out and your work saves in this browser. An account only adds one thing: the same progress on your other devices. You can add one later without losing anything.
Reading every section is not the bar. A lesson completes once you pass both of its labs and your teach-back matches enough of the authored key points. The Review card section shows exactly which of the two is still outstanding.
No. Take the hint. The only consequence is that the idea comes back for review sooner, which is what you want anyway.
Partly, and it says so on purpose. 10 lessons are fully written; the rest of the 251 topics are visible so you can see the whole road instead of a marketing summary. Planned means not written yet, not hidden behind a paywall.
Local progress lives in this browser profile only. Settings has a JSON export — download one now and after any big session. Signing in also keeps a synced copy.
It is not there to hand you answers, and on most installs it is switched off entirely. Tutor bridge instead builds a short brief about where you are, shows you exactly what it contains, and lets you take it to whichever assistant you already use.
Jargon is the most common reason people quit. Any term underlined in a lesson opens its meaning without losing your place, and the glossary drill turns the whole vocabulary into something you can practise.
RoseCode