Part III
Deconstruct#
Deconstruct is about explaining what the constructed and reconstructed system reveals. In the earlier parts, students have seen how quickly AI-assisted development can produce working software, how that speed can create technical debt, and how a system that works locally may need to change when users, events, failures, teams, and operating constraints grow. This part shifts the emphasis from making changes to analyzing evidence, trade-offs, boundaries, review practices, and scaling decisions.
In this part, scalability has two meanings. The first is the traditional scalability of the web application itself. The second is the scalability of the development system around the application. As students use agentic tools more actively, they should be able to explain what the tools made easier, what they made riskier, and what project structures made the work legible enough to review.