Ship a Project End to End

About this course

This is the capstone course of Kolom's Developer track and the Full-Stack Developer path. Earlier courses taught one tool at a time; here you use all of them together on a real delivery path. You build a store stock checker for Mangrove Market, a fictional grocery chain, as a small Node and TypeScript API with a web page, and take it from a GitHub issue through CI on two Node versions, review, a squash merge and a tag-triggered release to GitHub Pages and a container registry, then ship a test-first hotfix the next morning.

The second lesson turns that path into team rules: a short CONTRIBUTING.md, a PR template, CODEOWNERS and rulesets that enforce what a tool can enforce. You measure whether the rules help with DORA's four keys, read straight from tags, pull requests and incident issues, and learn to turn the numbers into one process change instead of a ranking. The third lesson adds a new kind of teammate, AI coding assistants, with an instruction file, a test-first prompt, a review checklist and a CI guard.

Each lesson has diagrams, a worked Mangrove example, real commands and outputs, quick checks, practice tasks (some auto-checked in your browser), flashcards and a podcast episode. The course project is a small app of your own with a real release history, and the final exam earns a free certificate.

What you will be able to do

• Take a feature from a GitHub issue to a reviewed, squash-merged pull request with required CI on two Node versions
• Ship a static page to GitHub Pages and an API image to GitHub's container registry from a version tag, with least-privilege workflow permissions
• Run a hotfix the safe way: failing test first, a small PR, a patch version and a written rollback plan
• Write a team playbook (CONTRIBUTING.md, PR template, CODEOWNERS and rulesets) that enforces what tools can enforce
• Measure delivery with DORA's four keys from tags, PRs and incident issues, and turn the numbers into one process change
• Brief, review and guard AI coding assistants with an instruction file, test-first prompts and CI checks

Syllabus

3 stops, about 2 h in total. Each stop fills in when you complete the lesson.

1. 1

   Project: ship a small app end to end

   Every earlier course on the Developer track taught one tool. This lesson uses all of them on one small project, in the order a real team would: an issue, a branch, commits, a pull request with a review, CI, a tagged release, a deployment, and a hotfix the next day. Follow along and you will have done, once, everything a product team's engineers do every week.

   40 minAdvancedEpisode1 exercise

   CI/CD with GitHub ActionsRelease managementHotfixes

2. 2

   Your team's engineering playbook

   A playbook is the short set of rules your team agrees on: how branches are named, how big a PR may be, who approves, what "done" means, when you release and how you hotfix. A product manager does not write the code but is often the best person to get these rules written down, agreed and kept, and every developer is the one who follows them. This lesson gives you a complete starter set and a way to measure whether it works.

   40 minIntermediateEpisode1 exercise

   Engineering playbooksCode reviewDORA metrics

3. 3

   Working with AI coding assistants

   AI assistants now write a real share of the code in many teams, from one-line completions to whole pull requests. They are fast and tireless, and they are confidently wrong often enough that the team's habits matter more than the tool. This lesson explains how they work in plain words and gives you the instruction file, prompt, review checklist and CI check that keep them useful and safe.

   30 minIntermediateEpisode1 exercise

   AI-assisted developmentAI code reviewCI guardrailsPrompt writing

4. Capstone: Ship the Partner app's delivery slot checker

   A realistic project with a rubric and a model answer.

5. Final exam and certificate

   10 questions drawn at random, 70% to pass.

Capstone project

Check what you know

Questions