Build Your Own X: Production
In the production phase, Build Your Own X projects are about applications, not mechanisms. By this point you have implemented enough internals (databases, networks, languages) — the elective projects here are full applications that exercise the operating model you've been building: front-end frameworks, game engines, physics, and graphics.
Each project is a self-contained tutorial with research links, the curated BYO-X external tutorial list preserved, milestones with code sketches, evidence requirements, common pitfalls, and module integration notes.
For production work, prefer official documentation for cloud services, Kubernetes, Terraform, CI, security, and observability. Use BYO-X to understand mechanisms, then cite the source and write your own operating guide.
Projects in this phase
| Project | Primary module fit | Difficulty | Languages typically used |
|---|---|---|---|
| Front-end Framework (React-like) | Sem 8 M1 — system design | Medium | JavaScript, TypeScript |
| 2D Game Engine | Capstone elective | Medium | C++, JavaScript, Lua |
| Physics Engine | Capstone elective | Medium–Hard | C++, JavaScript |
These three are positioned as capstone-adjacent: they are ambitious applications that can stand alone in a portfolio. None of them are required for graduation, but each makes a strong portfolio centerpiece if you choose to invest the time.
The 3D Renderer (Ray Tracer) is also a strong capstone-adjacent project but lives in the Foundations phase — its content (linear algebra + Monte Carlo) is Sem 1 math, even though the output is portfolio-grade visual art. Reach for it whenever you need a math-heavy graphics anchor in your portfolio.
Production module → project map
Semester 08: System Design and Leadership
| Module | Recommended BYO projects | Why it fits |
|---|---|---|
| Module 1 — System design methodology | Front-end Framework (capacity & API design surfacing) | A framework forces explicit API surface decisions |
| Module 2 — Microservices & decomposition | None — required project is better | Use Sem 8 required project for service decomposition |
| Module 3 — Event-driven architecture | None — required project is better | Use Sem 8 required project for event-driven work |
| Module 4 — Scale, reliability, performance | Physics Engine, 3D Renderer | Both expose performance tradeoffs that you can measure |
| Module 5 — Technical leadership | (each finished BYO project produces a decision memo) | The ADRs from any BYO project feed leadership artifacts |
Semester 09: Cloud and DevOps
BYO-X is not the right source for cloud, Terraform, Kubernetes, CI/CD, or observability work — official docs (HashiCorp, CNCF, OpenTelemetry, provider docs) are sharper and current. Treat Sem 9 as a docs-first phase.
Semester 10: Capstone
The capstone is your own project, not a BYO-X project. However, a finished BYO-X tutorial can become a portfolio anchor that supports the capstone — for example, if your capstone is a web platform, a finished Front-end Framework signals depth on the client side.
Build rules (production-flavored)
- Do not build a bigger app to hide weak operations. Three pages with health checks, metrics, and rollback beats thirty pages without.
- Every service needs a health check, metric, log shape, and rollback path.
- Every infrastructure choice needs a cost and security note.
- Every leadership artifact must make a decision easier for someone else.
- Portfolio release passes a stranger test. Someone with no degree-plan context can clone, run, and understand it.
Source
- Catalog:
codecrafters-io/build-your-own-x - Browsable mirror:
build-your-own-x.vercel.app - Books, paid tutorials, and 3rd-party guides for every project: see the Build Your Own X — Books & Paid Resources guide in the portal.