ai-hpc/ai-hardware-engineer-roadmap: Grade D (67/100)

/ 100

HTML205MIT1d ago

Popular for its size, but the engineering basics lag behind the interest.

Master AI inference, AI agent harness systems, and hardware engineering — then design a physical AI chip. That is the goal.

Documentation

1 checks need work

Contributing guide5pt

No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).

→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.

README12pt

README is present.

Install and run instructions9pt

README documents how to install the project.

License6pt

100

Licensed under MIT.

Engineering

3 checks need work

Linting and formatting5pt

No linter or formatter config found.

→ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.

Issue and PR templates6pt

No issue or PR templates found (−100 pts).

→ Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.

CI/CD14pt

CI is configured (.github/workflows/deploy-docs.yml).

Reproducibility6pt

Lockfile present (Phase 4 - Track B - Nvidia Jetson/5. Application Development/5. ML and AI/non-contact-monitoring-edge/phase1/requirements.txt). Installs are reproducible.

Tests18pt

Test files detected (Projects/jetson-llm-runtime/tests).

Project health

1 checks need work

Housekeeping3pt

.gitignore present.

Dependency manifest6pt

100

Dependency manifest found (Phase 4 - Track B - Nvidia Jetson/5. Application Development/5. ML and AI/non-contact-monitoring-edge/phase1/requirements.txt).

Repository metadata5pt

100

Repository has a description.

Activity5pt

100

Actively maintained (pushed within the last month).

Repository health signals

Activity, community, and responsiveness at scan time

Activity

—
Commits (30d / 90d)
35
Forks
0
Releases

Community

—
Community health
—
authors own >50% of commits
205
Watchers

Responsiveness

1d
Median issue response
<1h
Median PR merge time
0
Open issues

Repository files23 root entries

.github
Good: CI is configured (.github/workflows/deploy-docs.yml).
Assets
overrides
Phase 1 - Foundational Knowledge
Phase 2 - Embedded Systems
Phase 3 - Artificial Intelligence
Phase 4 - Track A - Xilinx FPGA
Phase 4 - Track B - Nvidia Jetson
Good: Lockfile present (Phase 4 - Track B - Nvidia Jetson/5. Application Development/5. ML and AI/non-contact-monitoring-edge/phase1/requirements.txt). Installs are reproducible.
Good: Dependency manifest found (Phase 4 - Track B - Nvidia Jetson/5. Application Development/5. ML and AI/non-contact-monitoring-edge/phase1/requirements.txt).
Issue: Build artifacts or local files may be committed (Phase 4 - Track B - Nvidia Jetson/5. Application Development/5. ML and AI/non-contact-monitoring-edge/phase1/__pycache__/calibration.cpython-314.pyc) (−40 pts).Fix: Remove them and add to .gitignore.
Phase 4 - Track C - ML Compiler and Graph Optimization
Phase 5 - Advanced Topics and Specialization
Phase 6 - Interview Preparation
Projects
Good: Test files detected (Projects/jetson-llm-runtime/tests).
scripts
.gitignore
Good: .gitignore present.
.gitmodules
AI-Hardware-Engineer-Roadmap.html
Curriculum-Authoring-Guide.md
LICENSE
Good: Licensed under MIT.
llms.txt
mkdocs.yml
README.md
Good: README is present.
Good: README is well structured with multiple sections.
Good: README includes screenshots or visuals. Great for first impressions.
Good: README has code examples.
Good: README links to a live demo or deployed app.
Issue: No status badges in the README (−10 pts).Fix: Add CI/build status badges from shields.io or your CI provider to signal project health.
Good: README documents how to install the project.
Good: README documents how to run the project.
robots.txt
Roles and Market Analysis.md