惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

云风的 BLOG
云风的 BLOG
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
IT之家
IT之家
Recent Announcements
Recent Announcements
B
Blog
D
Docker
V
V2EX
GbyAI
GbyAI
L
LangChain Blog
博客园 - Franky
U
Unit 42
T
The Blog of Author Tim Ferriss
A
About on SuperTechFans
博客园 - 【当耐特】
Google DeepMind News
Google DeepMind News
H
Hackread – Cybersecurity News, Data Breaches, AI and More
Vercel News
Vercel News
博客园_首页
D
DataBreaches.Net
人人都是产品经理
人人都是产品经理
Y
Y Combinator Blog
量子位
Blog — PlanetScale
Blog — PlanetScale
罗磊的独立博客

LWN.net comments

blocking algif_aead side effects? tcmalloc's weird hack [LWN.net] Fixed? [LWN.net] mpd [LWN.net] Userspace AX.25 [LWN.net] RIP [LWN.net] My two cents... [LWN.net] pipx [LWN.net] Tragedy [LWN.net] A young man destined for glory [LWN.net] And 'less' won't let you search [LWN.net] A great loss [LWN.net] Sad and shocking news [LWN.net] Easy migration from Clementine [LWN.net] Sad coincidence [LWN.net] GNOME is actually usable thanks to Seth et al [LWN.net] Sad news :( [LWN.net] armhf supports preempt_rt [LWN.net] MusicBrainz accurracy [LWN.net] On open source maintainership [LWN.net] Let's stop here [LWN.net] Not a new thing [LWN.net] uv is indeed great pgmoneta Some comments on this on a Postgres blog feed [LWN.net] uv [LWN.net] going to Debian [LWN.net] Upgrading 64-bit-capable systems to 64-bit kernels? [LWN.net] Free Software foundations Maintainers can wait for code review but not for publish review?
"Defensive" AI use [LWN.net]
dottedmag · 2026-04-17 · via LWN.net comments

"Defensive" AI use

Posted Apr 17, 2026 6:56 UTC (Fri) by dottedmag (subscriber, #18590)
In reply to: Pointless by jorgegv
Parent article: Forking Vim to avoid LLM-generated code

Increasingly sophisticated linters, code formatting tools and static code analysers have decreased the burden of mechanical checks. AI semantic supercharged linting is a great step in the same direction: it can easily shoot down contributions that don't pass the bar. It even can do some architectural checks. That's a natural place of agentic help in the contribution process: smart linter.

The scarce resource remains judgement: Does this change need to be made at all? Does it have repercussions beyond the developed system? Are these repercussions positive or negative? What are architectural rules that are worth having in the first place? Is this approach for solving the problem acceptable? These are much harder to encode in a set of rules in the current state of AI. If it changes then we'll just be pressing the button "make me an app", I guess.