The issue is that the majority relying on LLMs for their code are lazy with it or just want what they’re creating to work, so naturally some people will associate LLM usage with slop.

Lazy is a strong word... But I see that. Most of the companies have pushed so hard that any push back put you in the next layoff list. And in the capitalism, you either work or starve... So the choice is simple.

[...] difficult to balance light or hard usage [...]

I imagined that green field projects would be an easier path for LLM to help, I was wrong. Multiple times by the way. Continuing the work isn't also a good thing. My current workflow for coding I can see me using the tool to spot reviews before it happens. Naming variables that in my little head makes a lot of sense, but don't in a general sense.

But again, my focus is in quality over quantity. Specially for my pet projects. So this is something that I care.

Regarding time, if you don't look at the code it's a 1.000.000x productivity boost like the Theo’s online want to say, and if you push back is either skill issue or wrong model. But in my view, if you care about the code, and it's quality... the tool barely move the speed dial up.