Learn by building

Read code, run it, then map the system

Choose the amount of structure you need: a complete course, a quick local experiment, or a source-linked X-ray of a real codebase. Each route keeps the next action visible.

Clear starting routes
3
Execution and storage
Local
Code X-ray evidence
Exact lines

A guided coding journey

Move from an idea to a system you can explain

Each step has a real action and a visible outcome. You can begin anywhere and return through My Learning when work has been saved.

  1. 01

    Learn the method

    Read a focused lesson, inspect worked examples, then run deterministic tests.

    Start the JavaScript course
  2. 02

    Try and trace

    Change a small program, run it locally, and connect output to changing state.

    Open the scratchpad
  3. 03

    Read the whole system

    Upload real source and move between files, symbols, imports, calls, and lines.

    Build a local X-ray

Representative workspace preview

See what the program does, one state at a time

This static trace demonstrates the visual feedback pattern used across coding. It is an example, not a claim about uploaded code; the real X-ray always uses the learner’s exact files and line locations.

function sum(values) {
  let total = 0;
  for (const value of values) total += value;
  return total;
}

sum([2, 4, 6]);

Execution trace

Text equivalent of the example execution trace
StepIndexValueTotalWhat changed
Startn/an/a0Create the accumulator
Read022Add the first value
Loop146State changes visibly
Loop2612The condition ends next
Return3n/a12Send the result back

Step 3 · Bring a real codebase

Build your private code X-ray

Choose one source file or a .zip repository. Novus Learn parses it in this browser into a real file tree, symbol index, source view, and relationship map. Nothing is rewritten or graded, and every observation stays linked to its line.

Drop a source file or a .zip codebase

Source files (.ts, .js, .py, .go, .rs, .java, …) or a .zip of a codebase · up to 40 MB

How this stays private

  • Files are read and parsed in your browser; their contents are never sent to a server.
  • The generated project is stored only in this browser (IndexedDB) until you delete it.
  • Malformed, binary, empty, or oversized files are rejected with a clear message.
  • Every claim keeps its source location: a line range for text, a page for PDFs, a timestamp for transcripts.

Consent version 2026-08-21.1

Cookie preferences