Understand what you build.

Your learning loop

1. Read and predict. Explain the inputs, state, decisions, and expected output.
2. Try a small experiment. Change one thing and compare the result with your prediction.
3. Check understanding. Take an assessment, read the feedback, and revisit mistakes.
4. Build and explain. Publish a project with a README, tests, and a record of your reasoning.
5. Review and improve. Use automated feedback, revisit errors, and strengthen your evidence.

Where AI fits

Use AI to explore alternatives, ask for explanations, and suggest tests. You remain responsible for the code.

• Describe the requirement before asking for an implementation.
• Check API names against the actual source and documentation.
• Predict behavior and test normal, boundary, and invalid inputs.
• Explain every important line in your own words.
• Record what AI suggested, what you changed, and what evidence supports the result.

Flying V and Agila

Flying V is Agila's application language. The lessons use the public Agila SDK's documented application, capability, and UI contracts.

The browser lab uses the public learning sandbox. It prints descriptions and lifecycle events; the full Agila OS supplies its own runtime and services.

What progress means

Each lesson has an automated completion check. Pass it to receive a lesson certificate, then follow the next-step link. Module assessments test broader understanding. Projects record your practice and do not require a mentor.

Independent competence develops through repeated practice and review. A completed module alone is not a guarantee of mastery.