Try it in the book
Predict. Experiment. Explain.
Explore demos and check your understanding throughout the chapters. Switch between Explore and Practice, check your answers, and sign in to save your results for another visit.
Start with measurementCourse project
One contract. Three fresh builds.
Build the Work Activity Tracker with a local model, a foundation model, and an agent fleet. The behavior stays stable; the development system changes.
Open the specificationBook contents
Front matter
- Appendix A Evaluating agentic development workflows
- Appendix B Reproducible development environments
- Appendix C Advanced control boundaries in web applications
- Appendix D Agent-system security, control, and traceability
- Appendix E Formal scalability and reliability models
- Appendix F Durable workflows and retry-safe effects
Field evidence
Case studies
Project histories that connect the book’s concepts to concrete development decisions, failures, and lessons.
Browse the collection- Slideotter – Learning faster than the product converged How a technically ambitious precursor generated durable lessons faster than it established a production path.
- Thesis Journey Tracker – Small scope made production success possible How a narrow product boundary and simple runtime turned rapid agent-assisted development into a working production tool.
- Kirjolab – When code production scaled faster than architecture How a strong development harness enabled exceptional delivery speed while architectural understanding struggled to keep up.
- Webernetes – Comparing generated behavior with a real cluster How an agent-assisted port used reviewable source mappings and shared tests against a real cluster to make selected compatibility claims observable.
- Modern Web Guidance – Treating current knowledge as a tested dependency How fast-changing web-platform knowledge can become a retrieved, versioned, and task-evaluated development dependency.
- Elements of Scalable Web Development – When a book became a web project How an agent-assisted manuscript became a tested publishing system and made editorial judgment the limiting resource.