Write Linters and Tools Before Code
cookie.engineer
cookie.engineer
Maybe I am using agentic environments a little too much lately? In the case of the weblog articles I wrote everything myself first and let the agents check against missed formatting rules, so the LLM was e.g. adding the references section and cutting/pasting the overview section together.
I usually use agents for fact checking most though, so e.g. in my malware writeups that I wrote I let my agents fact check if (parts of) what I discovered was also confirmed by other parties that analyzed e.g. the same malware samples.
The wiki learning courses were written by me, then rewritten by my agents, that's why there's still lots of unicode stuff in there. The articles were from my old website, but I let agents rewrite them to fit the new (linted) document format.
I have to now proofread everything and change/rewrite them over the course of the next weeks or months, and have to do that incrementally because it was just soo much content.
That was kinda the point behind the posted article: How to get to a point where most of the gruntwork is automated so you'll only have to proofread afterwards.
Usually that still takes a long while, especially when it's exploit or hardware errata or memory errata related. Verification of binary exploits is not as automated yet as I want it to be, hence my other projects and experiments with eBPF etc.