Urgent.News

What's breaking now, across thousands of outlets.

Tech

Every Rule We Added Had a Bug. So We Stopped Adding Rules.

We wrote a handful of small rules on November 12. Each one was a line or two. Each one was obviously right. A read-only review found a real bug in nearly every one of them before they shipped. That is not a story about bad rules. I think it is a story about the wrong kind of question being answered with rules at all. I build Since, which tracks the packages, AI models, APIs and runtimes your code…

On November 12, a handful of small rules were written for a tool called Since. Since tracks packages, AI models, APIs and runtimes that code depends on, and informs developers about changes and fixes. The team added rules for prefixes, keywords and dotted versions of model IDs, but each rule had a bug. A read-only review found a real bug in nearly every rule before they shipped.

The issue was that rules were being used to answer questions that a person would answer by reading the code. For example, determining which provider a model ID goes to requires understanding the context and how the code uses the model. Instead of adding more rules, the team decided to rely on code analysis and human reviewers to determine the correct answer.

They drew a line: code only settles what it can prove. Rules are only used for questions that cannot be answered by the existing code review process. The team also discovered that their existing code for checking pasted snippets had its own smaller matcher, which was not integrated with the main rule set. This caused additional bugs and inconsistencies.

To fix the problem, the team decided to route the snippet check through the shared reader, delete the copy of rules, and write the agreement as a test. They found that rules had been the source of problems before, and it was time to stop being overly strict and allow for more flexibility in code analysis.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

OpenAPI Components: Reuse vs Duplication

Quick answer: Reuse an OpenAPI component with $ref whenever the same schema, parameter, or response is genuinely one concept used in multiple places; it gives you a single source of truth and keeps…

scrapy-playwright

scrapy-playwright 是 Scrapy 官方插件组织维护的下载处理器,用 Playwright for Python 驱动真实浏览器来抓取请求。它的定位是处理需要执行 JavaScript 的页面,同时保留 Scrapy 原有的调度和 item 处理流程。和前面聊的 curl_cffi 方案相比,它不是"模拟"浏览器指纹,而是直接用真浏览器,所以 TLS、HTTP/2、JS…

  • scrapy-playwright is official Scrapy plugin using Playwright for Python.
  • Enables handling JavaScript pages while preserving Scrapy flow.
  • Requires pip install scrapy-playwright playwright install chromium.

Scope Was Always a Test-Design Question

Originally published at tddbuddy.com . Related reading: Agent PRs Do Not Converge Under Design Review argued the current-PR review turn is the wrong artifact for an agent author.

  • Agentic PRs revert due to scope creep in 2.66% of cases
  • Agents rewrite code without considering broader impact
  • Scope assertions can prevent inadvertent modifications

Fixing the Daily Content Generator’s Bluesky Payload – A Code‑First Walkthrough

Fixing the Daily Content Generator’s Bluesky Payload – A Code‑First Walkthrough TL;DR: I rewrote the payload builder for the daily post generator so it correctly writes bluesky_es.json and updates…

  • CI pipeline skipped git add and commit steps due to payload file location issue
  • Utility created to manage locales for correct file name generation
  • Metadata file updated atomically to record published status and URIs

More from Monday 16 November →