Description
While testing the resume evaluation pipeline, I noticed that projects without a live demo receive a deduction during evaluation.
This works well for frontend or UI-based applications, but it may not be appropriate for backend-focused projects. Many backend, infrastructure, or cloud projects (e.g., REST APIs, Kafka, Redis, Docker, AWS services, CLI tools) are typically evaluated through their source code, architecture, documentation, and tests rather than a publicly hosted demo.
As a result, strong backend engineering projects may receive lower scores even when the repository demonstrates production-ready implementation.
Suggested Improvement
Consider applying the "live demo" expectation only to projects where a user interface is a core deliverable. For backend or infrastructure projects, evaluate the repository based on implementation quality, documentation, testing, and architecture instead of deducting points for the absence of a live demo.
This would make the evaluation more consistent across different software engineering domains.
Description
While testing the resume evaluation pipeline, I noticed that projects without a live demo receive a deduction during evaluation.
This works well for frontend or UI-based applications, but it may not be appropriate for backend-focused projects. Many backend, infrastructure, or cloud projects (e.g., REST APIs, Kafka, Redis, Docker, AWS services, CLI tools) are typically evaluated through their source code, architecture, documentation, and tests rather than a publicly hosted demo.
As a result, strong backend engineering projects may receive lower scores even when the repository demonstrates production-ready implementation.
Suggested Improvement
Consider applying the "live demo" expectation only to projects where a user interface is a core deliverable. For backend or infrastructure projects, evaluate the repository based on implementation quality, documentation, testing, and architecture instead of deducting points for the absence of a live demo.
This would make the evaluation more consistent across different software engineering domains.