I think the greater issue here is the possibility of the entire article being AI slop and the 'doomed' direction in which we are heading where reputed sources of information are churning out slop.
I am doing the same but with LLVM. For starters, I filtered issues with the "good first issue" label and found something to work on [1]. It took 2 months in review and about a month to research and write the code. Finally got merged yesterday. I am writing about it so that when someone else bumps into the same problem, they hopefully take 1 hour instead of 1 month. Compilers, like the kernel, are a lot of fun!
Pretty cool. A drawback of such a hard filter is we also lose all the human generated content posted after Nov 2022. I am no expert in this but a ad-block like list based filter but for AI generated content may work for this or dare I say, an AI-based filter but alas.
Equality saturation (something that luminal uses at its core) is a topic for hardware synthesis and verification too. Something like dynamic hardware generation (instead of kernel generation). For example, see this thesis [1] by Samuel Coward of Imperial.
I found todo apps to be clunky and bloated. I decided to use github issues (of a private repository) as my notes. I even made a little script around it (via gh-cli) to edit it from the command line [1]. I don't update TODO very often from my phone, but in case I want to, I use the Github mobile app. I am finally content with this solution (although I don't know for how long).
It appears that rendering for code blocks (```) is still not implemented (see here https://gitclassic.com/llvm/llvm-project/issues/100045).
Would love to see this grow