{"slug": "judging-a-project-by-the-tool-that-touched-it-is-a-proxy", "title": "Judging a project by the tool that touched it is a proxy", "summary": "A developer argues that rejecting projects solely because they are labeled 'AI-generated' is a flawed filter, citing examples where a two-year vectorization algorithm project without machine learning and a single-prompt project with no testing both get rejected. The author proposes a practical prompt that evaluates repositories on maintainability signals such as reproducibility and testing, ignoring code provenance entirely.", "body_md": "# Judging a project by the tool that touched it is a proxy\n\nThat's the broken filter.\n\n**Project A:** two years of work on a vectorization algorithm, with a deliberate decision *against* machine learning, corrected benchmarks, reproducible results, active maintenance.\n\n**Project B:** a single prompt, zero testing, no follow-up.\n\nBoth get labeled \"AI-generated.\" Both get rejected. Only one deserves a seat in a genuine developer community.\n\nSo instead of debating the label, I set up a practical prompt that evaluates repos on maintainability signals and completely ignores how the code was produced. It's a hands-on filter I use when triaging AI-assisted projects:\n\n``` text\n\nYou are a senior engineering reviewer. Evaluate the repository below and decide whether it belongs in a maintained, professional developer community.\n\nIgnore how the code was created — human, AI-assisted, or fully automated. Provenance is irrelevant to this review.\n\nAssess these signals only:\n\n1. Reproducibility: Is there a manifest, lockfile, or container setup that lets a new contributor run the project without guessing?\n\n2. Testing: Do tests exist? Do they cover the critical paths rather than just happy paths\n\n[Next Title: Prompt That Wires Internal Tools to Your Data →](/en/threads/4430/)\n\n## All Replies （8）\n\n[@ben](/en/users/ben/)\n\n[@jess](/en/users/jess/)\n\n[@francistrdev](/en/users/francistrdev/)— this is a choice.", "url": "https://wpnews.pro/news/judging-a-project-by-the-tool-that-touched-it-is-a-proxy", "canonical_source": "https://promptcube3.com/en/threads/4561/", "published_at": "2026-07-31 17:40:57+00:00", "updated_at": "2026-07-31 18:24:58.471654+00:00", "lang": "en", "topics": ["ai-ethics"], "entities": [], "alternates": {"html": "https://wpnews.pro/news/judging-a-project-by-the-tool-that-touched-it-is-a-proxy", "markdown": "https://wpnews.pro/news/judging-a-project-by-the-tool-that-touched-it-is-a-proxy.md", "text": "https://wpnews.pro/news/judging-a-project-by-the-tool-that-touched-it-is-a-proxy.txt", "jsonld": "https://wpnews.pro/news/judging-a-project-by-the-tool-that-touched-it-is-a-proxy.jsonld"}}