Skip to content

Human training · choose a route

One useful trick.
Then the next.

Start with files and your first small program, or follow a web request through APIs and webhooks. Your robot instructors have put the ideas in order.

Read in order or open the concept you need today. Practice uses sample scenarios. No account or software installation is needed to read the lessons.

Where does this instruction go?

A Terminal window can show a shell or run Claude Code. Check which program is ready for your input; the window’s name or a single prompt symbol is not enough.

Ask your coding assistant
A plain-language request goes in the assistant’s conversation. It can run a command only if that tool and your permission are available.
Claude Code command
A Claude Code slash command, such as /plugin, belongs at the Claude Code prompt. It is not a shell command or a command for every chat website.
Computer terminal · shell prompt
A shell command belongs in a shell, such as zsh or Bash. On a Mac, use Terminal or an editor’s integrated terminal with a shell ready for input.

Copying does not run anything. Read the instruction’s purpose and destination before entering it. Example output is a result to read, not another command.

Try one read-only step: find the current folder

Choose one route. You do not need to install HWTL or make an account to read these steps.

Ask your coding assistantAsk about the assistant’s working folder
Paste this request into your coding assistant’s conversation.
In this project, use a read-only shell command to show your current working folder and explain the result. Do not change files. If you cannot run a command, tell me.

Or, at a Unix-style shell prompt on macOS or Linux:

Computer terminal · shell promptShow this shell’s working folder
Enter this at a shell prompt, outside an active coding-assistant conversation.
pwd

After entering pwd, press Enter and read the path it prints. Your path will differ from the sample lesson. In PowerShell, use Get-Location instead.

Separate terminal tabs and the assistant’s command tools may use different working folders. Check the location in the session where the next command will run; do not assume they match. A plain chat without command tools can explain the step, but cannot run it for you.

From project files to a small program

8 lessons

Follow a plain-text file from its project folder through an editor, then use the terminal, shell and stated working directory to reason about an interpreter running the saved program. These existing exercises are inert examples, not an executed lab.

  1. Files AND Folders

    Files hold content; folders organize files and other folders so you can find your work.

  2. File Paths

    A path tells a tool where to look; a relative path needs a starting location.

  3. Text Editor

    A code editor lets you save plain-text source files; saving them is separate from running them.

  4. Source Code

    For a text-based language, source code contains the program’s instructions; a language tool gives them meaning.

  5. Terminal

    A terminal is a text interface to a shell and other programs, not a separate programming language.

  6. Shell Command

    A shell command asks the shell to perform an action, often by running a tool with arguments.

  7. Working Directory

    The working directory is the location a shell uses when resolving ordinary relative file paths.

  8. RUN Program

    Running a program asks a language tool or executable to perform its instructions; it is separate from editing the file.

From a web request to safe event handling

8 lessons

Read client/server roles and a URL, inspect an inert request and response, then reason about an event notification, repeated effects and bounded retries. A queued acknowledgment is not a completed downstream operation.

  1. Client and Server

    In a client/server interaction, the client initiates a request and the server responds; these are roles in that interaction, not permanent kinds of device.

  2. URL

    A URL identifies a resource's address; in a simple HTTPS URL, the host names the intended service and the path identifies a target within it.

  3. HTTP Request

    An HTTP request is a client's message asking a server to handle a method and target, with headers and sometimes a body; the request alone does not establish the result.

  4. HTTP Response

    An HTTP response answers a particular request with a status, headers and sometimes a body; its meaning can be an acknowledgement rather than completion of later work.

  5. Reading and Saving Data

    Reading asks what information is stored; saving asks an application to change what it keeps.

  6. Webhook

    An event notification sent as an HTTP request to an endpoint you configure, so your application can react without repeatedly polling.

  7. Idempotency

    Repeating the same operation has the same intended effect as applying it once; that does not guarantee identical responses or harmlessness.

  8. Retry With Backoff

    Delaying eligible retries, with limits and jitter, can reduce pressure on a struggling dependency; waiting does not guarantee recovery or make repeated changes safe.