> I think this could work
> well as a blog post…
A blog post ain't a bad idea.
But I only set out to get the overall vibe of what Yegge is doing. The static analysis [1] and the automaton's take [2] were plenty for doing that.
> …maybe you could at least
> go through the report yourself
> and point out issues it highlights
I suppose. But to be frank, I'm not
that interested in the project to do a super deep dive.
It was all I could do to muster up the will to even do as much as I did eventually force myself to do.
I'm not the faniest fan boy of AI-assisted coding. But I appreciate them for what they're good at. To me, it delivered a stellar code review here.
> …show the relevant code,
> and explain why that's
> actually bad
I humbly don't think I could add anything that the LLM and static analysis haven't brilliantly illuminated already.
The Sonar Cloud analysis is super detailed. And the automaton's code review is on the money. Digging into their respective nitty gritty is left as an exercise for the reader.
[1] https://g2ww.short.gy/CCWutUHalfDone
[2] https://g2ww.short.gy/ItsaGasGasGas
