Open: 01_live-dashboards/project-portfolio-audit-dashboard.html (self-contained)
Problem. A 160-project archive is impossible to keep an honest read on.
What I built. A meta-tool that scans the whole project folder and, per subproject, extracts README + git state + test results + package.json, then renders an interactive dashboard with editable blurbs, a run-tests action, and an audit modal. Bash rescan + data-driven HTML, dark/light themes.
Why it matters. Automation and systems-thinking applied to my own workflow — exactly the instinct to build tooling that surfaces ground truth rather than guessing.
I have a hundred-sixty-project archive, and keeping an honest read on it is impossible by memory. So I built a meta-tool that scans the whole folder and, per project, pulls the README, git state, test results, and package.json into one interactive dashboard with a run-tests button. This is the instinct I'd bring to a codebase I don't know: build the tool that surfaces ground truth instead of guessing. It's also literally how I picked the projects in this portfolio.
GG · Applied AI Engineering portfolio · synced to youdontneedmy.help design