5 ms·

As someone who loves FE the slop people are pushing where I work is really quite upsetting to me. I reviewed some code earlier which clearly wasn't intended fo

by kypro 13d ago

As someone who loves FE the slop people are pushing where I work is really quite upsetting to me. I reviewed some code earlier which clearly wasn't intended for consumed by humans and I know with certainty this dev wouldn't have understood 90% of what that code did. It looked like hours of Claude trying to force square into a round hole tbh, but it worked. Was I going to reject the PR because of my code preferences? No, of course not. Ultimately it doesn't matter anymore. If Claude can maintain it then who cares... Even if it's broken (which it didn't seem to be) it's just FE anyway so not the end of the world. I wish it did matter of course, but like most of coding these days, it just doesn't.

bigstrat2003 13d ago
> Was I going to reject the PR because of my code preferences? No, of course not. Ultimately it doesn't matter anymore. You absolutely should've rejected it. Putting slop into production is a huge trap, because now the humans can't understand it and the LLM is just going to make it worse and worse over time.
- sci_prog 13d ago
  I think what OP is saying is that the fact that a human can't understand it won't matter as the code will only ever be read by AI.
  - kypro 13d ago
    Yes exactly. I think we all understood at a high-level what it was doing. The issue I had was that it was doing a lot of weirdness like using `Object.defineProperty` to try to force an existing library to do something it wasn't suppose to do. No human would have written that code. Although I generate most of my code with AI I still personally try to keep it understandable by a competent developer. Where as most people on my team are not good at FE so they just trust the LLM to get it right. But ultimately it just doesn't matter anymore.
lnrd 13d ago
> Even if it's broken (which it didn't seem to be) it's just FE anyway so not the end of the world. Last week alone I was unable to access two major websites because their auth flow was broken (I was attempting to log in with Apple, so not "the happy path"). I was just locked out, had to contact support. I guess this mentality is what causes it. We had safeguards and best practices built over the years of learnings to avoid introducing these kind of regressions. And we threw them away in half a year to...gain some productivity in delivering features that most likely the users don't even want.

by kypro 13d ago

bigstrat2003 13d ago

> Was I going to reject the PR because of my code preferences? No, of course not. Ultimately it doesn't matter anymore. You absolutely should've rejected it. Putting slop into production is a huge trap, because now the humans can't understand it and the LLM is just going to make it worse and worse over time.

sci_prog 13d ago
I think what OP is saying is that the fact that a human can't understand it won't matter as the code will only ever be read by AI.
- kypro 13d ago
  Yes exactly. I think we all understood at a high-level what it was doing. The issue I had was that it was doing a lot of weirdness like using `Object.defineProperty` to try to force an existing library to do something it wasn't suppose to do. No human would have written that code. Although I generate most of my code with AI I still personally try to keep it understandable by a competent developer. Where as most people on my team are not good at FE so they just trust the LLM to get it right. But ultimately it just doesn't matter anymore.

lnrd 13d ago

> Even if it's broken (which it didn't seem to be) it's just FE anyway so not the end of the world. Last week alone I was unable to access two major websites because their auth flow was broken (I was attempting to log in with Apple, so not "the happy path"). I was just locked out, had to contact support. I guess this mentality is what causes it. We had safeguards and best practices built over the years of learnings to avoid introducing these kind of regressions. And we threw them away in half a year to...gain some productivity in delivering features that most likely the users don't even want.