01 / TRAJECTORY
From having a project evaluated to taking responsibility for evaluation.
Before joining the committee, Liviu competed and earned awards at InfoEducație. That participant experience helps him assess both code and architecture, as well as how clearly a team can defend its decisions.
02 / LIVIU'S ROLE
Two years of judging, feedback and mentorship.
As a national committee member, Liviu reviews software projects, participates in evaluation and gives feedback that helps competitors see the next level of their product.
- 01
Code & architecture
Implementation quality, technical decisions and system robustness.
- 02
Utility
The problem solved and the relevance of the solution.
- 03
Product
Experience coherence, completeness and room to evolve.
- 04
Feedback
Concrete, useful and respectful observations for each team.
03 / PERSPECTIVE
Not only “does it work?”, but “why was it built this way?”.
Implementation
Quality and technical choices.
Architecture
Structure and robustness.
Utility
Impact and relevance.
Argument
Clarity of presentation.
04 / IMPACT
Experience flows back into the community.
The committee role complements product work: standards used in real projects become feedback for young people building their first serious systems.