Static analyzers
Static analyzers
Posted Oct 10, 2026 2:42 UTC (Sat) by mathstuf (subscriber, #69389)In reply to: Static analyzers by mvollrath
Parent article: Coping with the onslaught of kernel security bugs
Now we have tools that multiply our time, and in my experience, also multiply learning rate. As of September, it's gotten to the point where I'd be kind of pissed if it went away. I'm still banking on human knowledge being valuable, but the act of typing code into an editor has never been the interesting part of the craft. The best programming language is one you read and write natively.
I've found a few things:
- For utilities that only I'll use or are only a means to an end: sure, slop is fine. Example: a TUI to help manage GitLab's issue boards because the web is clunky with label management. It is purely a means-to-an-end that makes many assumptions about the project at hand.
- For small things that are "Vim macro-able" or
sed-able: just do it; explaining it is probably not worth it (though one's editor proficiency may move this line around wildly).ast-grepcan raise the bar significantly (though LLM assistance to write theast-greprules may be useful). Many times, tools can do these things (e.g.,cargo update --breakingcan updateCargo.tomlfor you) - For "active development" where design is being done on-the-fly, the typing of the code gives me space to think about the design and seeing it unfold helps to clarify things. For example, after refactoring some LLM-assisted code recently, I found even more improvements and use cases that I wouldn't have without adding another feature utilizing many of the same codepaths. This original MR (see older revisions to see unreviewed patterns, particularly this diff) with this refactor leading to this feature further factored out into a dependent crate so that a long-requested feature boils down to this code. There's
<details>migration here as well that really should be a separate MR that I've not separated out yet. I'm not good enough at prompting to get this kind of leverage out of LLMs quicker than I can discover it while typing. - The sweet spot seems to be, for me, a "motivation bridge" where I know how something should be done in my head, but the activation energy is just too high. This seems to be the land of "good third to fifth issue" bugs and features (I definitely don't think LLMs belong in the "good first issue" field for long-lived projects because their value lies in being an onramp for humans).
