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

推荐订阅源

宝玉的分享
宝玉的分享
B
Blog RSS Feed
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
MyScale Blog
MyScale Blog
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
S
SegmentFault 最新的问题
Y
Y Combinator Blog
月光博客
月光博客
IT之家
IT之家
T
Tailwind CSS Blog
Last Week in AI
Last Week in AI
L
LangChain Blog
博客园_首页
MongoDB | Blog
MongoDB | Blog
P
Proofpoint News Feed
博客园 - Franky
WordPress大学
WordPress大学
云风的 BLOG
云风的 BLOG
M
MIT News - Artificial intelligence
V
Visual Studio Blog
小众软件
小众软件
博客园 - 叶小钗
博客园 - 三生石上(FineUI控件)
N
Netflix TechBlog - Medium

LWN.net comments

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? A reasonably extreme point of view [LWN.net]
<soapbox> [LWN.net]
mjbommar · 2026-06-16 · via LWN.net comments

That "Assisted-by" guy here :)

For the record, I submitted a patch on 2.6.19 back in December 2006 when the 802.11 softmac stack was young and still broken on my laptop. I think that means I'm technically not a first timer, if anyone is really counting.

That said, your broader point remains. I think we all appreciate the difference between "understanding" something and the ability to recite the call graph with your eyes closed after three beers.

The gap between those two things is real and I don't think most people - myself especially in this context - should pretend to understand the code they submit in the latter sense. That's reserved for the select few whose shoulders we stand on.

But I doubt I'm ruffling too many feathers when I suggest that writing software of any complexity without formal verification (which is often impossible), especially in languages like C, especially when a code base spans many years and many authors and many styles, is practically guaranteed to induce human failure modes.

So I think the real question we ought to be asking, heavily motivated by the impact of LLM's on both the productivity function and the changing nature of offensive security, is how we can help more people like me safely contribute.

Safely can mean a lot of things. Yes, there's the Rust conversation re: memory management. But more broadly, I think it's documentation, testing, processes, and - probably most controversially - a little more convergence of standards, styles, and even, *gasp*, code.

All of these things are tools that transcend the individual maintainer. And in my opinion, much like the smartest, fastest, strongest hominids lost out to the ones who built the best tools and shared that knowledge, we are at a point where competitive dynamics will do the same to us.

P.S.: since I know some of you have asked or wondered about the why, I'll say that rolling up your sleeves and grabbing a shovel feels much better than sitting anxiously and worrying about what happens when frontier models fall into the wrong hands. I still remember when security was about Theo and Linus's latest argument; let's just say, we're not in Kansas anymore.