Un agente de IA logra 74 merges en 24 repositorios open source en seis semanas

·1 views

Entre finales de septiembre y el 10 de noviembre de 2026, una cuenta operada por un agente de IA abrió 143 pull requests. De ellos, 74 fueron integrados, 49 de esos en 24 repositorios externos como browser-use y llama_index. Según el relato, cada PR se limitaba a una sola idea, llegaba con implementación, tests y CI en verde, y se respondía a los mantenedores en horas. Los autores también señalan que aceptaron los rechazos sin insistir, y que los PRs pequeños con tests fueron los que más rápido se aprobaron.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Daily Cognito Audit Job Could Silently Inflate AWS MAU Billing

A developer designing a multi-tenant SaaS with a single Cognito user pool planned a daily job to check for unexpected email changes and administrators lacking TOTP. AWS documentation states that AdminGetUser calls count toward monthly active user billing, so the job would make every account billable regardless of actual sign-ins. The author estimates costs on the Essentials tier, where each MAU beyond the 10,000 free allowance costs $0.015, and notes the cost scales with signed customers rather than usage. A shared free tier across an organization, including staging accounts, could push spending past the threshold earlier than expected. The author's planned safeguard, an AWS Budgets alert at 9,000 MAU, is unverified and may not function as intended.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Afterword: Measuring Which Blog Comments Actually Matter Using a Ledger of Claims

The author analyzed nine years of DEV data and found that the platform's dashboard metrics told them little about what they valued. They concluded that the most meaningful signal lay in reader comments, which often include corrections, extended arguments, and counterexamples that shape later writing. To test whether an AI model could help triage the comment stream, they recorded their hypotheses and falsification criteria in a documented ledger before writing any code. The project, called Afterword, is a local tool that organizes comments by priority without hiding or deleting any of them. Its success will be judged mainly by whether comments the author rates as consequential stay visible, rather than by raw accuracy, and performance will be compared against both full chronological reading and a simple keyword heuristic.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Bitcoin and 24/7 Stock Perpetuals Move Together in US Hours, Study Finds

Binance now lists perpetual futures on US stocks, gold, silver, and crude oil that trade around the clock, allowing minute-by-minute comparisons with Bitcoin. A study of 4 and 5 November showed Bitcoin rising while stocks were flat, then both falling, with stocks dropping far more on the second day. Over 139 trading days from April to November 2026, Bitcoin and the stock basket repriced together within the same minute during regular US hours, with neither clearly leading. When US markets were closed, the stock perpetuals followed Bitcoin by about a minute, though this relationship was weak. Daily correlation rose from near zero in late August to 0.84 recently, and 5 November was the largest divergence in the sample.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer builds open source subscription backend after a costly billing failure

After a misconfiguration left a customer's subscription status stale following a purchase, the developer set out to build more reliable infrastructure. The result is SubTru, a self-hostable, open source API that processes subscription events from Stripe, the Apple App Store, and Google Play. Apps can query its GET /access endpoint to check any user's subscription status. The article explains the difficulties involved, including duplicate, late, or out-of-order provider events and the need to verify each provider's differently structured payloads. The developer chose a single service design for receiving and processing events, weighing tradeoffs around failure isolation, scalability, and deployment simplicity.

0 comments Read more at DEV Community