Introduction
On this page
Who this book is for
This book is designed for developers who already have experience in software development and want to learn how to use coding assistants effectively. It assumes you are comfortable with Git, some programming knowledge, and basic command-line operations. The exercises will help you understand how to evaluate and integrate coding assistant suggestions into your workflow.
The exercises use a small Task API. You’ll read the code, refine a request, diagnose a bug, plan a larger change, document the system, and investigate a simulated outage. You’ll use what you find to decide which checks belong in the repository. Bring the editor and terminal you already use.
What to install
- Git to clone your fork, start exercises from known revisions, and review a diff.
- Node.js 24 or later and npm to run the TypeScript service and its tests. The starter uses the standard library.
- OpenCode 2.3.2 for the terminal exercises. Follow the setup chapter to install it and verify one model.
- Docker with Compose for the postmortem and alerting chapters. You can install it when you reach the incident.
The examples use a POSIX shell. On Windows, use Git Bash for commands like PORT=3100 npm start. The lab runs on your machine. The hosted model option needs network access.
Get the lab
Fork the Task API on GitHub, then clone your fork. Replace YOUR_LOGIN in the URL.
git clone https://github.com/YOUR_LOGIN/hands-on-coding-assistants-lab.git
cd hands-on-coding-assistants-lab
git fetch https://github.com/woliveiras/hands-on-coding-assistants-lab.git --tags
git rev-parse --verify lab-start
git status --short
npm test
The fetch gives you the exercise tags even if your fork copied only the default branch. Expect a revision hash, an empty status, and three passing tests.
You can download the starter source to inspect it offline. Use the fork for the exercises that name a Git tag or use GitHub Actions.
What you need to know
The service uses fictional data and keeps it in memory. Start it with npm start and open http://127.0.0.1:3000/health. Expect {"status":"ok"}. Stop it with Ctrl+C. Each test starts its own server on a free port.
A chapter may give you a start tag such as lab-start or lab-debugging. Check git status --short before switching. Commit the work you want to keep or start a separate worktree. A tag gives you the same starting code even if your previous exercise took a different route.
References
- GitHub. Fork a repository. GitHub documentation.
- Git maintainers. git-worktree. Git reference manual.
- Node.js contributors. Modules: TypeScript. Node.js API reference.
- OpenCode maintainers. Migrate from V1. OpenCode 2 installation documentation.