Dashboard
Signal #145233POSITIVE

Ask HN: Do we need a stronger process for vetting code?

75

Now that writing code is largely automated, I've seen Github being filled to the brims with slop, and it feels like the overall quality of everything produced with code (either the tooling or the software itself) has been getting worse. Pre-AI, times were a bit simpler: You looked at the stars, looked at the issues, poked around the code, and gave the repository a chance. Today there's just way too much stuff being produced. I don't see this changing in the future, so I was thinking that I'd be cool to make some spin out of it: My idea is to create a data aggregator based on https://github.com/explore that is targeted towards developers. Think of it as the "Rotten Tomatoes" of code. Here are a few ideas that I've been bouncing around: Repositories having different scores and being organized by tech stack, language, etc. Certified classics by category and technology.Each repository has a scorecard. - its dependencies (too much - potential bloat) - issue progression over time (number of ...

HackerNews AI Launchesabout 3 hours ago
Read Full Article

Explore with AI-Powered Tools

View All Signals

Explore more AI intelligence

Want to discover more AI signals like this?

Explore Steek
Ask HN: Do we need a stronger process for vetting code? | Steek AI Signal | Steek