3 ms·

So what if this was vibe-coded? How do you know this was a "slop" if you did not try it?

by blutoot 9mo ago

acedTrex 9mo ago
> How do you know this was a "slop" if you did not try it? Because I have eyes and can look at the code for 2 seconds. It's not very difficult to check for the hallmarks of careless slop code. If you can't tell in a few seconds then you can continue testing it out just like any actual project.
- minimaxir 9mo ago
  And what are those hallmarks in this case? There is no heuristic that is applicable for every programming language. Unfortunately, ratatui requires a lot of verbose code that may be indistinguishable from LLM generated code: https://ratatui.rs/examples/apps/demo/ https://ratatui.rs/examples/apps/demo/
  - acedTrex 9mo ago
    Easiest one is ridiculous comments, always a dead ringer for an LLM. ESPECIALLY when its from a plan and comments '// STEP 2: ...' Like here in this posts repo https://github.com/huseyinbabal/taws/blob/2ce4e24797f7f32a52356cf61268529742c5ea5a/src/main.rs#L232 https://github.com/huseyinbabal/taws/blob/2ce4e24797f7f32a52... This a dead ringer for LLM slop that someone didnt even care enough to go through and clean up. Edit: Just to keep it going, you ever seen a human write dependencies like this for a small toy tui? https://github.com/huseyinbabal/taws/blob/2ce4e24797f7f32a52356cf61268529742c5ea5a/Cargo.toml https://github.com/huseyinbabal/taws/blob/2ce4e24797f7f32a52... Edit2: Sure why not, lets reimplement randomly a custom jsonpath when serde_json_path exists https://github.com/huseyinbabal/taws/blob/2ce4e24797f7f32a52356cf61268529742c5ea5a/src/app.rs#L253 https://github.com/huseyinbabal/taws/blob/2ce4e24797f7f32a52...
    - minimaxir 9mo ago
      That's not a smoking gun. I've definitely seen pre-2023 open source code mentioning steps in their comments. Even though that file also has a lot of tautological comments which are more indicative of LLM coding, it's not a smoking gun either: the frequency of comments is an editorial decision which has pros and cons. It's the equivalent of calling something an AI generated images just because the fingers are weird, and requires a judgment more concrete than "I have eyes." > you ever seen a human write dependencies like this for a small toy tui? Yes? That's just TOML syntax. I'm not sure which dependency in that list is excessive, especially for something that has to handle HTTP requests. If you mean adding a comment header for each section, then that's a better argument, but see argument above.
      - acedTrex 9mo ago
        I mean if you want bury your head in the sand and try to play semantics over if its ENOUGH proof or not go right ahead. But it's more than LLM enough for anyone who has experience with them to conclude the LLM drove the majority of the output. Hence, slop
        minimaxir 9mo ago
        To be clear, I agree that there was likely AI assistance with the code (as it will be a safe assumption going forward in SWE given the progress agentic LLMs have achieved in the past few months), but a) that doesn't intrinsically mean it's slop and b) the "all AI is slop" bit is intellectually lazy at best especially without objective evidence and doesn't lead to constructive HN discussion.
        acedTrex 9mo ago
        > a) that doesn't intrinsically mean it's slop If it can quickly and easily be identified as LLM code then yes, it is intrinsically slop and of no value. The person who submitted it did not even value it enough to look at/clean it up. Why would anyone else care to look at it. If it is LLM generated but then HAS BEEN cleaned up then you cant immediately see the LLM and it passes the check anyways.
  - joshka 9mo ago
    https://ratatui.rs/examples/apps/demo/ https://ratatui.rs/examples/apps/demo/ is pretty much the oldest untouched remnant of code from tui-rs days (pre-ratatui fork in Feb 2023). Ratatui itself has a lot of much nicer AI generated code in it since then ;) We've also done a bunch of things to help drive down some of the boilerplate (not all of it mind you - as it's a library, not a framework like other TUI libs)
satvikpendem 9mo ago
Vibe code is by definition slop.
- acedTrex 9mo ago
  They are indeed synonyms
llimllib 9mo ago
I'm not generally opposed to vibe-coded tools, I've even created some. However I wouldn't be excited to trust one with my AWS key and read/write access to my infra
- rvz 9mo ago
  Especially if it is has zero tests.
  - minimaxir 9mo ago
    Zero tests are actually a better argument that it’s not AI generated. Agents love tests.
- lijok 9mo ago
  Then don’t use AWS keys
bcb_1000 9mo ago
This guy took this idea from my post on reddit and made an open source version. It is def just ran through some agent, I can tell because look at how he defines regions? Look how he defines credentials, it doesn't make coherent sense. He read my reddit post saw the interest and is trying to run with it. Thats crazy.
7777332215 9mo ago
[dead]

So what if this was vibe-coded? How do you know this was a "slop" if you did not try it?

by blutoot 9mo ago

So what if this was vibe-coded? How do you know this was a "slop" if you did not try it?

> How do you know this was a "slop" if you did not try it? Because I have eyes and can look at the code for 2 seconds. It's not very difficult to check for the hallmarks of careless slop code. If you can't tell in a few seconds then you can continue testing it out just like any actual project.

minimaxir 9mo ago
And what are those hallmarks in this case? There is no heuristic that is applicable for every programming language. Unfortunately, ratatui requires a lot of verbose code that may be indistinguishable from LLM generated code: https://ratatui.rs/examples/apps/demo/ https://ratatui.rs/examples/apps/demo/
- acedTrex 9mo ago
  Easiest one is ridiculous comments, always a dead ringer for an LLM. ESPECIALLY when its from a plan and comments '// STEP 2: ...' Like here in this posts repo https://github.com/huseyinbabal/taws/blob/2ce4e24797f7f32a52356cf61268529742c5ea5a/src/main.rs#L232 https://github.com/huseyinbabal/taws/blob/2ce4e24797f7f32a52... This a dead ringer for LLM slop that someone didnt even care enough to go through and clean up. Edit: Just to keep it going, you ever seen a human write dependencies like this for a small toy tui? https://github.com/huseyinbabal/taws/blob/2ce4e24797f7f32a52356cf61268529742c5ea5a/Cargo.toml https://github.com/huseyinbabal/taws/blob/2ce4e24797f7f32a52... Edit2: Sure why not, lets reimplement randomly a custom jsonpath when serde_json_path exists https://github.com/huseyinbabal/taws/blob/2ce4e24797f7f32a52356cf61268529742c5ea5a/src/app.rs#L253 https://github.com/huseyinbabal/taws/blob/2ce4e24797f7f32a52...
  - minimaxir 9mo ago
    That's not a smoking gun. I've definitely seen pre-2023 open source code mentioning steps in their comments. Even though that file also has a lot of tautological comments which are more indicative of LLM coding, it's not a smoking gun either: the frequency of comments is an editorial decision which has pros and cons. It's the equivalent of calling something an AI generated images just because the fingers are weird, and requires a judgment more concrete than "I have eyes." > you ever seen a human write dependencies like this for a small toy tui? Yes? That's just TOML syntax. I'm not sure which dependency in that list is excessive, especially for something that has to handle HTTP requests. If you mean adding a comment header for each section, then that's a better argument, but see argument above.
    - acedTrex 9mo ago
      I mean if you want bury your head in the sand and try to play semantics over if its ENOUGH proof or not go right ahead. But it's more than LLM enough for anyone who has experience with them to conclude the LLM drove the majority of the output. Hence, slop
      - minimaxir 9mo ago
        To be clear, I agree that there was likely AI assistance with the code (as it will be a safe assumption going forward in SWE given the progress agentic LLMs have achieved in the past few months), but a) that doesn't intrinsically mean it's slop and b) the "all AI is slop" bit is intellectually lazy at best especially without objective evidence and doesn't lead to constructive HN discussion.
        acedTrex 9mo ago
        > a) that doesn't intrinsically mean it's slop If it can quickly and easily be identified as LLM code then yes, it is intrinsically slop and of no value. The person who submitted it did not even value it enough to look at/clean it up. Why would anyone else care to look at it. If it is LLM generated but then HAS BEEN cleaned up then you cant immediately see the LLM and it passes the check anyways.
- joshka 9mo ago
  https://ratatui.rs/examples/apps/demo/ https://ratatui.rs/examples/apps/demo/ is pretty much the oldest untouched remnant of code from tui-rs days (pre-ratatui fork in Feb 2023). Ratatui itself has a lot of much nicer AI generated code in it since then ;) We've also done a bunch of things to help drive down some of the boilerplate (not all of it mind you - as it's a library, not a framework like other TUI libs)

satvikpendem 9mo ago

Vibe code is by definition slop.

acedTrex 9mo ago
They are indeed synonyms

llimllib 9mo ago

I'm not generally opposed to vibe-coded tools, I've even created some. However I wouldn't be excited to trust one with my AWS key and read/write access to my infra

rvz 9mo ago
Especially if it is has zero tests.
- minimaxir 9mo ago
  Zero tests are actually a better argument that it’s not AI generated. Agents love tests.
lijok 9mo ago
Then don’t use AWS keys

bcb_1000 9mo ago

This guy took this idea from my post on reddit and made an open source version. It is def just ran through some agent, I can tell because look at how he defines regions? Look how he defines credentials, it doesn't make coherent sense. He read my reddit post saw the interest and is trying to run with it. Thats crazy.

7777332215 9mo ago

[dead]