← Retour au fil
Ridges construit des ingénieurs logiciels IA capables de surpasser les humains
TAO Daily26 sept., 16h · il y a 4j

Ridges construit des ingénieurs logiciels IA capables de surpasser les humains

Ridges décompose le métier de développeur en compétences et fait s'affronter des agents IA : 76 % de réussite en linting en une semaine, coût ramené à 0,02 $ par tâche.

Ridges (SN62), sous-réseau de Bittensor, fait s'affronter des agents de code soumis par les mineurs et testés sur des problèmes cachés. L'idée : décomposer le génie logiciel en compétences spécialisées. Le linting (#27) a atteint 76 % sur le jeu de test caché en une semaine, à environ 0,02 $ par tâche. Les requêtes de bases de données (#28, PostgreSQL, ClickHouse) captent 90 % des émissions ; la génération de tests (#29) suit.

Objectif : Ridgeline, produit qui rend ces agents utilisables au quotidien. Le développeur connecte un dépôt GitHub, crée une issue ; plusieurs agents s'affrontent et le meilleur résultat revient en pull request, sans fusion automatique. L'enjeu : réunir ces compétences en une IA capable de surpasser les ingénieurs humains.

Bittensor

Détails

Source
TAO Daily
Publication
26 sept. à 16h41

Contenu source (brut)

<p class="wp-block-paragraph">Ridges is changing how it trains AI software engineers.&nbsp;Instead of putting every agent into one big coding competition, <a href="https://ridges.ai/">Ridges</a> (SN62) is now breaking software engineering into smaller skills. Agents can compete in different tracks for things like fixing code problems, working with databases and writing good tests.</p> <p class="wp-block-paragraph">Two competitions are already live. <strong>Linting</strong> and <strong>Database Query Engineering</strong>. A third, <strong>Test Generation</strong>, is coming next.</p> <p class="wp-block-paragraph">The whole point behind all these isn&#8217;t far-fetched. Typical software engineers do many different jobs. Ridges wants AI agents that can get very good at each of those jobs, then bring those skills together inside <strong>Ridgeline</strong>, its product for completing software tasks.</p> <h2 class="wp-block-heading">A quick primer on Ridges</h2> <p class="wp-block-paragraph">Ridges is a Bittensor subnet focused on building better AI software engineers.</p> <p class="wp-block-paragraph">Miners build coding agents and submit them to competitions. Ridges then tests those agents on hidden software problems inside controlled environments. The better agents earn more rewards, while new challengers keep trying to beat them.</p> <p class="wp-block-paragraph">This has already taken Ridges through broader software-engineering competitions based around solving coding problems. But software engineering is much bigger than simply asking an AI to fix a GitHub issue.</p> <p class="wp-block-paragraph">That is where the new specialist competitions come in.</p> <h2 class="wp-block-heading">First came Linting</h2> <figure class="wp-block-image size-large"><img fetchpriority="high" decoding="async" width="1024" height="519" src="https://taodaily.io/wp-content/uploads/2026/09/image-263-1024x519.png" alt="" class="wp-image-25063" srcset="https://taodaily.io/wp-content/uploads/2026/09/image-263-1024x519.png 1024w, https://taodaily.io/wp-content/uploads/2026/09/image-263-300x152.png 300w, https://taodaily.io/wp-content/uploads/2026/09/image-263-766x388.png 766w" sizes="(max-width: 1024px) 100vw, 1024px" /><figcaption class="wp-element-caption">Different <a href="https://www.ridges.ai/competitions">competitions</a> on Ridges</figcaption></figure> <p class="wp-block-paragraph">Competition #27 on Ridges focuses on <strong>linting</strong>.</p> <p class="wp-block-paragraph">Linting tools such as <a href="https://docs.astral.sh/ruff/">Ruff</a> scan code for mistakes, unsafe patterns, and other problems. But finding a warning is the easy part; the agent still has to understand what caused it and make a fix without breaking the rest of the program.</p> <p class="wp-block-paragraph">Ridges reported that agents reached <strong>76% on its hidden test set within the first week</strong>, while the cost fell to around <strong>$0.02 per task</strong>.</p> <figure class="wp-block-embed is-type-rich is-provider-x wp-block-embed-x"><div class="wp-block-embed__wrapper"> <div class="embed-x"><blockquote class="twitter-tweet" data-width="500" data-dnt="true"><p lang="en" dir="ltr">We&#39;ve kicked off Niches with a Linting competition! <br><br>In just one week we&#39;ve seen performance hit 76% on our hidden test set with cost reduction down to $0.02 per task.<br><br>Results like these help us validate the Niches model and adjust where needed.<br><br>We&#39;re excited for the next… <a href="https://t.co/GtTursqsfU">pic.twitter.com/GtTursqsfU</a></p>&mdash; Ridges AI | SN62 (@ridges_ai) <a href="https://x.com/ridges_ai/status/2092684102595961119?ref_src=twsrc%5Etfw">August 26, 2026</a></blockquote><script async src="https://platform.x.com/widgets.js" charset="utf-8"></script></div> </div></figure> <p class="wp-block-paragraph">For Ridgeline, this skill is important because an AI-generated pull request should not only work, but also leave the codebase in good shape.</p> <h2 class="wp-block-heading">Then Ridges moved into databases</h2> <p class="wp-block-paragraph">Competition #28 goes deeper into <strong>Database Query Engineering</strong>.</p> <p class="wp-block-paragraph">Here, agents work with live applications and databases such as <a href="https://www.postgresql.org/">PostgreSQL</a> and ClickHouse. They may need to fix a query returning the wrong data, build a new way to fetch information, or make an existing query cheaper and faster.</p> <p class="wp-block-paragraph">This is much closer to the everyday work software teams deal with.</p> <p class="wp-block-paragraph">A website might be showing the wrong users. An API might be pulling too much data. A database request might work but take far too long.</p> <p class="wp-block-paragraph">Ridges is training agents to find and fix those kinds of problems.</p> <p class="wp-block-paragraph">The database competition currently receives the large majority of emissions (90%) between the two live specialist tracks, showing where Ridges is putting much of its attention right now.</p> <h2 class="wp-block-heading">Tests are next</h2> <figure class="wp-block-image size-large"><img decoding="async" width="1024" height="576" src="https://taodaily.io/wp-content/uploads/2026/09/image-264-1024x576.png" alt="" class="wp-image-25064" srcset="https://taodaily.io/wp-content/uploads/2026/09/image-264-1024x576.png 1024w, https://taodaily.io/wp-content/uploads/2026/09/image-264-300x169.png 300w, https://taodaily.io/wp-content/uploads/2026/09/image-264-768x432.png 768w, https://taodaily.io/wp-content/uploads/2026/09/image-264-678x381.png 678w, https://taodaily.io/wp-content/uploads/2026/09/image-264.png 2048w" sizes="(max-width: 1024px) 100vw, 1024px" /><figcaption class="wp-element-caption">About tests (from Ridges)</figcaption></figure> <p class="wp-block-paragraph">Competition #29 will focus on <strong>Test Generation</strong>.</p> <p class="wp-block-paragraph">Writing tests sounds simple until you think about what a good test needs to do.</p> <p class="wp-block-paragraph">It should catch the bugs when something breaks. But it should not fail just because a developer renamed something or changed the internal structure of the code.</p> <p class="wp-block-paragraph">Ridges plans to test this by introducing small hidden bugs and harmless code changes. The agent&#8217;s tests need to catch the actual problems while ignoring changes that do not affect how the software works.</p> <p class="wp-block-paragraph">And this fits directly into what Ridgeline needs because if an AI agent is going to change a codebase on its own, it also needs to know how to prove that its change works.</p> <h2 class="wp-block-heading">All of this is building toward Ridgeline</h2> <p class="wp-block-paragraph">This is where the different competitions start to make sense when viewed as a whole.</p> <p class="wp-block-paragraph"><a href="https://taodaily.io/ridgeline-beta-lauches-autonomous-ai-engineers-for-github-issues/">Ridgeline</a> is Ridges&#8217; product for turning these agents into something developers can utilize for everyday use.</p> <p class="wp-block-paragraph">A developer connects a GitHub repository and creates an issue. Ridgeline&#8217;s agents read the code, make the change, test their work and return a pull request for the developer to review. Nothing gets merged automatically.</p> <p class="wp-block-paragraph">The current product describes the flow simply as <strong>issues in and pull requests out</strong>. It also says multiple agents can compete on a task, with the strongest result being returned.</p> <p class="wp-block-paragraph">Now think about one normal software ticket.</p> <p class="wp-block-paragraph">A developer might ask Ridgeline to fix a page that is pulling the wrong data, make sure the change does not create new code problems and add tests so the bug