Inside the Machine · Explain what happens when an application starts. Find out what you can already explain in English, then make your explanation clearer.
Start with your own English. No preparation and no correction yet.
First attempt · diagnostic
Speak for 60–90 seconds about an application you know. Your listener cannot see your screen.
Keep this first attempt. With your agreement, use your own voice recorder, or ask your teacher to note two exact sentences. This page does not record or upload audio. Do not read ahead before speaking.
Read the code, investigate one outside source, then explain what the evidence supports.
"dev:web": "pnpm --filter @lexis/web dev""dev": "next dev --port 3001"The root command selects the web package and runs its dev script. That script starts the Next.js development on 3001. Once it is ready, a browser can send a to it.
Predict: does this source prove the server is already running? Which evidence would you need?
Constructed teaching example, executed with Node.js. This short program is not the Lexis web server.
console.log("Application started");
console.log("Result:", 2 + 3);Application started Result: 5
The program writes two lines and exits. Unlike a development server, it has no work left keeping it running.
Read one source below, or watch the opening of the video. Find an actor, an action and a result. Tell your partner what you found; quote only the short phrase you need.
Node.js contributors · Read the original ↗
“pass the name of the file you want to execute”
Find: what two things does the usual command contain? Explain “execute” using a more everyday verb.
Lesson paraphrase: use the node command followed by the file name. “Execute” means “run” here. Explain which part names the runtime and which names the file.
Stretch: a script is saved on disk. Is it already a process? Justify your answer.
MDN contributors · Read the summary ↗
“The term web server can refer to hardware or software, or both of them working together.”
Find: who requests a file, and who sends it back? Retell the exchange with “When …”.
Lesson paraphrase: the browser requests a file; the server handles the request and sends a response. In our startup example, “server” means the software.
Stretch: explain why “the server is a computer” is not always a complete definition.
Short excerpt: MDN Web Docs, CC BY-SA 2.5. Prompts and paraphrases are authored for Lexis.
Node.js Ultimate Beginner’s Guide in 7 Easy Steps ↗ · Fireship · optional fast-speech challenge.
Watch the opening minute. Pause or slow playback and use captions if available. Catch one phrase about what Node.js does; compare it with the official reading. You do not need to understand every word.
If playback or captions are unavailable, use either reading above. A phrase you hear is evidence to discuss, not an automatically marked listening answer.
Choose the statement supported by each artefact. Explain which words or numbers helped you.
1. What does the web package’s dev script request?
2. What does the small Node program write after its first line?
3. What can you conclude from the package scripts alone?
A small language toolkit, after your first attempt.
| Job | Useful English |
|---|---|
| Start the sequence | First, I run the command. |
| Describe system behaviour | The command starts the server. The server waits for requests. |
| Connect an event and a reaction | When the browser sends a request, the server responds. |
| Locate something precisely | The server listens on port 3001. The process uses data in memory. |
| Say what you cannot confirm | I can see the output, but I cannot tell how much memory it uses. |
Say each phrase, then put it in a sentence. Listen buttons use your device’s optional speech synthesis.
Tap a term for its lesson meaning, UK IPA, related language and pronunciation links. For any other word, select it and open Word desk in the header, or type it there.
· · · · · · ·
Describe the difference between and without translating. Use one example from a device you own.
Choose one studio mode (4 min), then sequence the startup (4 min) and repair the language (4 min). Try other studio modes after class.
Spend four minutes in one mode, then use the words aloud. Return for other modes after class. These rounds are separate from lesson XP and are not a placement test.
Written recall is saved only in this browser. Use Clear saved recall on a shared device.
Cover the meanings. Recall each term, then explain it to a partner.
Order this successful local web-server scenario. The browser request is made only after the server is ready. This is a simplified teaching scenario, not a captured startup log.
Complete the explanation with one word per gap. Use the base verb in brackets where provided.
The command (start) the server. The server listens port 3001. The browser (send) a request. The process uses data memory.
Your teammate needs an explanation, not a list of technical words.
System walkthrough
Explain the journey from running pnpm dev:web to seeing a page. Use the source snippets as evidence; do not read a model answer.
Challenge ladder: Support — keep the scripts visible and use First / Then / When. Core — explain from five keywords. Stretch — explain without using “thing” or “it”, and distinguish what the script tells you from what a runtime log proves.
Useful clarification: “Do you mean the file or the running process?” · “Could you repeat the last step?” · “First I would check whether the server is ready.”
Working alone? Record your explanation with your own recorder, answer the two questions aloud, then listen again. Save it beside the warm-up if you want a comparison.
Use evidence from what you actually said.
| Look for | Evidence to note |
|---|---|
| Clear sequence | Can the listener retell the steps in order? Copy one sequence phrase. |
| Actors and actions | Does each sentence say what runs, sends, waits or displays? |
| Precise vocabulary | Are saved files and running processes distinguished? |
| Interaction | Did you answer a follow-up or ask for clarification? |
For each row, note independently / with a prompt / not yet on paper or in your own notes. Choose one sentence from your recording, improve it, and say it again.
Transfer check: compare “The server listen in port 3001” with your own wording. Repair the verb and preposition before opening Teacher notes.
Take the language back to a system you use.
Finish aloud: “Now I can explain…” and “I still need help with…”
Between lessons · 5–10 minutes: open a trusted project’s README or package scripts. Find its documented startup command. Write four sentences: what you run, what starts, what output you expect, and how you check readiness. Do not run unfamiliar commands just for this task, and remove secrets or personal paths before sharing anything.
Read the official Node.js guide to running scripts. Bring one useful phrase and one question. In Lesson 2, you will read process/system output. Keep today’s baseline for the Unit 1 walkthrough.
Authentic script excerpts: lexis/package.json and lexis/apps/web/package.json. Additional authentic sources: Node.js documentation, MDN Web Docs and Fireship’s linked YouTube guide (source links and tasks in Input). Readings checked 5 October 2026; video availability and captions depend on YouTube. Short quotations are attributed; all tasks and support paraphrases are authored for Lexis. Runtime reference: Node.js CLI: --eval. Course basis: Lexis Computing syllabus, Unit 1, and source corpus §9.
The arithmetic command is a constructed, executed teaching example; the teammate and successful web-startup sequence are constructed scenarios. Neither is presented as a production incident or verbatim conversation. The lesson is usable offline; external reading and device speech voices may require a connection.