Someone posted a PR this week, mostly coded using LLMs and spec driven development, which I left 15~20 comments on for stuff that didn't make any sense or was coded inconsistently. It's encouraging to see all of them addressed, and the general code of the PR look a lot better, as I approved it this morning. Despite all the things I don't like about this current shop, after 25+ years in software, this is the most I've really felt like a "senior engineer," as far as really guiding project design and mentoring people.

Don't blame the llm, blame the dev.

Yeah, but what I think is that a senior Im not there to do the task for the junior. They shouldnt push just any llm code and call it done and then have me do all the research to make sure the code makes sense. The dev is responsible for the llm slop and they should be the first filter, not the guy that fixes it after I already left 30 comments on code that needs to be removed or code that doesn't follow our style Guide, or code that duplicates solutions we already have done and are part of the code base or architecture... If the dev can't even do that then why do we need him? I can run a bullshit generator on my own just fine, but thats not useful