you are viewing a single comment's thread
view the rest of the comments
[–] 7 points 1 week ago (1 child)

So we need to stop calling everything generated by automation slop. Because there is good automation and bad automation, and they don’t live in the same room.

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.

I’ve found it quite difficult to balance light or hard usage of LLMs. Either I end up having to correct and adjust the model’s output all the time, which costs me more time than just writing by hand, or I have to let it go loose on the codebase and end up with code that’s hard or even impossible to maintain without an LLM.

So I decided to stop using LLMs to write code for me a long time ago and I find it hard to believe there are many people out there who can get this right (not saying they don’t exist).

  • source
  • hideshow 1 child comment
  • [–] [S] -4 points 1 week ago

    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.

  • source
  • parent