The whole point of the MS Access reference is that similar situations have been tropes since at least the 1990s. Bad code generated by someone who doesn't know how to program well -- whether that person is supposed to be a professional programmer but is incompetent, or has a different job -- is nothing new, and neither is having competent programmers clean it up. LLMs probably generate more of it, but can also fix a lot of it, or at least patch it up.

A year ago, LLMs were not useful for me as a programmer. Now they are: the models are better, they can use long contexts more effectively, and the harnesses are better at helping the models. Nowadays my job is mostly not programming, but LLMs let me organize and prepare tools in spare time rather than needing days or weeks of attention. I would not trust them on a 200k+ line project -- and Claude Opus 5 has issues even on 50k LOC projects -- but they absolutely can help given good direction and a narrow enough scope.