Progress & evaluation
Progress should be demonstrated, not assumed.
Evaluation should focus on evidence from work rather than attendance or completion alone.

Dimensions
Technical foundations
- Exercises
- Code/design review
- Technical explanations
Problem solving
- Debugging
- Approach selection
- Trade-off reasoning
Quality
- Testing
- Validation
- Maintainability
- Security awareness
Delivery habits
- Git
- Issue tracking
- Documentation
- Task completion
Communication
- Questions
- Updates
- Demos
- Technical explanations
Ownership
- Independent planning
- Follow-through
- Risk escalation
- Revision after feedback
Professional conduct
- Reliability
- Respect
- Integrity
- Confidentiality