Workshop 7: Engineering Standards & Avoiding AI Technical Debt

Duration: 60 minutes You will leave with: three governance docs (CI/CD, AI usage, coding standards) and one working enforcement mechanism, all built live in session.

📊 Slides: (link coming)

📓 Logbook: record today's results in your course logbook as we go.

What we do

Together, in this session, we design the rules that protect everything you've built. I demonstrate the enforcement mechanism live, and we draft the governance docs together so the rules survive contact with future developers.

1. We draft a CI/CD governance doc, an AI usage policy, and coding standards together.
2. We implement one enforcement mechanism live: pre-commit hook, lint rule, PR template, or coverage gate.
3. We debate the trade-off: developer freedom versus engineering standards.

In this workshop

• CI/CD governance template: template we fill in together for the CI/CD governance doc
• AI usage policy template: template we fill in together for the AI usage policy
• Coding standards template: template we fill in together for coding standards
• Husky pre-commit setup: reference Husky + lint-staged setup

Keep your logbook

• Everything we build today goes in your course logbook: your three governance docs and the working enforcement mechanism you committed to the repo, plus a clean final state of OrbitTasks.
• In Workshop 8 your proposal comes straight out of it.