Coding for Shippers — Connected Exercise Path

Begin with evidence and a useful result

Begin with First Repository and Commit in a new harmless folder you own, or inspect an existing practice repository before adding anything. Keep a known working version. If the code is unfamiliar, use Codebase Explainer before you plan a change; it is a read-only orientation exercise.

Before building for a pull request

If you intend to propose a pull request, use First Pull Request’s setup first: establish the approved base and a separate branch, and preserve unrelated work. Build and test on that branch, then return for the finished diff review. A local-only tool needs no host account.

Carry the work into the next step

Use Build a Personal Tool for one repeated task. Define sample inputs and expected results before implementation. Run the normal, malformed and boundary cases, inspect the output, and correct a demonstrated problem. Then use First Pull Request when you have a host account and appropriate contribution access. Keep the branch focused and check the actual proposed diff.

If a technical step is confusing, Work Through a Problem with AI shows how to ask for one concrete next step. Check Your Work and Choose What Comes Next explains claimed versus actual actions; Git and runtime checks remain in the exercises.

Use only the support you need

A local tool and meaningful commit are useful even if hosting is unavailable. A pull request requires a host and contribution permissions; defer that exercise rather than claim you completed it. This path is a small practical introduction, not the full programming course.

Open the exercises

• Ex18 — First Repository and Commit
• Ex20 — Build a Personal Tool
• Ex19 — First Pull Request
• Ex21 — Codebase Explainer

Follow the selected exercise’s instructions and checks; you choose which corrections to use.

This is alpha material. Report unclear instructions or errors through a public issue or email help@bigleverinstitute.org. Share only redacted or fictional material.