4 ms·

How you type is a poor proxy for code quality. Code quality is a good proxy for code quality. Inspect the code, build a verification pipeline for it, use agents

How you type is a poor proxy for code quality. Code quality is a good proxy for code quality. Inspect the code, build a verification pipeline for it, use agents to explore the code and the architecture, see if you can unearth anything fowl.

yjftsjthsd-h 3mo ago
It's not "how you type", it's "whether any human so much as laid eyes on the code". I wouldn't automatically discard code from an LLM, but let's put the goalposts where they actually are.
- gchamonlive 3mo ago
  How do you know nobody laid eyes on the code in the project?
  - SwellJoe 3mo ago
    Have you look at the commits? A bunch of empty ones (seemingly all empty ones, though there must be some real ones in there somewhere). It's a bizarre looking repo. I don't even know how you make a repo look like that, but it certainly doesn't allow tracing of what code was added when and why. It looks suspicious, even if it isn't. All those empty commits look like an intentional obfuscation of something, though I have no idea what.
    - gchamonlive 3mo ago
      It's indeed strange, it's likely some agent running amok. Doesn't look good indeed, but if I was interested in the project I'd still investigate the code itself
zamadatix 3mo ago
How big a video file is a poor proxy for the encode, quality is a good proxy. The problem is finding the actual quality of a video file is a hell of a lot more work and resources than using a proxy to see if doing so is a good use of our resources. See if you can go the extra mile you described for a few hours/dollars tonight and let us know what you find, it would be appreciated!
- gchamonlive 3mo ago
  I do for projects I have interest in running and for my own projects. For instance I had agro with https://github.com/Mord3rca/gamma-launcher https://github.com/Mord3rca/gamma-launcher so I pulled my trusted agent, hammered the code with architectural and static analysis and made it my own here https://gitlab.com/gabriel.chamon/yagi https://gitlab.com/gabriel.chamon/yagi
  - zamadatix 3mo ago
    Oh, I'll just have to stick with what info SwellJoe provided using the proxy on this project for now then as it seems none of us have the time or resources to go much further :/. Thanks!
    - gchamonlive 3mo ago
      You are welcome! My point stands though. Evidence of agentic loop is a bad proxy for code quality. If you are interested in a project you need to do the legwork, vibecoded or not.
      - deleted 3mo ago
        [deleted]
      - deleted 3mo ago
        [deleted]
      - zamadatix 3mo ago
        Sure - that's always valid - but now I know I'm no longer interested before having put the legwork in! A cool security project that has been reviewed multiple ways already is one thing, a C project nobody else (even the author) was very involved with is another. I don't need to put the legwork in on this codebase to know it's not worth putting the manual legwork in for because I can already get such unverified things out of AI the same as the author, so i'd just review my projects the same as you'd review yours. That's what the proxy provided, not an override of an actual review.
SwellJoe 3mo ago
I'm not judging based on how they type. I can't see how they type, they vibed the README. And, it's not my monkey. You can inspect the code, build a verification pipeline for it, use agents to explore the architecture and see if you can unearth anything fowl. My heuristic is to dismiss purely vibe-coded apps from people I don't know, particularly for security sensitive stuff. If the README is written by a human and is coherent and exhibits some kind of desire and competence to make good software on the part of the author, I'm more likely to trust they drove their agents with care. Here's the thing: you can make good software with agents, if you exhibit good judgement and put yourself in the path as a gate on quality. Too many clues point at this being loop engineering. And, C for this task, given 100% agent authorship, gives me the ick. Seems like bad judgement or opting out of making judgement calls.
- gchamonlive 3mo ago
  Took a look at the readme and seems coherent enough. A readme is also a technical entrypoint, no problem in parts of it being generated, specially if you have quick start, tables and loose documentation there you need updating.

yjftsjthsd-h 3mo ago

It's not "how you type", it's "whether any human so much as laid eyes on the code". I wouldn't automatically discard code from an LLM, but let's put the goalposts where they actually are.

gchamonlive 3mo ago
How do you know nobody laid eyes on the code in the project?
- SwellJoe 3mo ago
  Have you look at the commits? A bunch of empty ones (seemingly all empty ones, though there must be some real ones in there somewhere). It's a bizarre looking repo. I don't even know how you make a repo look like that, but it certainly doesn't allow tracing of what code was added when and why. It looks suspicious, even if it isn't. All those empty commits look like an intentional obfuscation of something, though I have no idea what.
  - gchamonlive 3mo ago
    It's indeed strange, it's likely some agent running amok. Doesn't look good indeed, but if I was interested in the project I'd still investigate the code itself

zamadatix 3mo ago

How big a video file is a poor proxy for the encode, quality is a good proxy. The problem is finding the actual quality of a video file is a hell of a lot more work and resources than using a proxy to see if doing so is a good use of our resources. See if you can go the extra mile you described for a few hours/dollars tonight and let us know what you find, it would be appreciated!

gchamonlive 3mo ago
I do for projects I have interest in running and for my own projects. For instance I had agro with https://github.com/Mord3rca/gamma-launcher https://github.com/Mord3rca/gamma-launcher so I pulled my trusted agent, hammered the code with architectural and static analysis and made it my own here https://gitlab.com/gabriel.chamon/yagi https://gitlab.com/gabriel.chamon/yagi
- zamadatix 3mo ago
  Oh, I'll just have to stick with what info SwellJoe provided using the proxy on this project for now then as it seems none of us have the time or resources to go much further :/. Thanks!
  - gchamonlive 3mo ago
    You are welcome! My point stands though. Evidence of agentic loop is a bad proxy for code quality. If you are interested in a project you need to do the legwork, vibecoded or not.
    - deleted 3mo ago
      [deleted]
    - deleted 3mo ago
      [deleted]
    - zamadatix 3mo ago
      Sure - that's always valid - but now I know I'm no longer interested before having put the legwork in! A cool security project that has been reviewed multiple ways already is one thing, a C project nobody else (even the author) was very involved with is another. I don't need to put the legwork in on this codebase to know it's not worth putting the manual legwork in for because I can already get such unverified things out of AI the same as the author, so i'd just review my projects the same as you'd review yours. That's what the proxy provided, not an override of an actual review.

SwellJoe 3mo ago

I'm not judging based on how they type. I can't see how they type, they vibed the README. And, it's not my monkey. You can inspect the code, build a verification pipeline for it, use agents to explore the architecture and see if you can unearth anything fowl. My heuristic is to dismiss purely vibe-coded apps from people I don't know, particularly for security sensitive stuff. If the README is written by a human and is coherent and exhibits some kind of desire and competence to make good software on the part of the author, I'm more likely to trust they drove their agents with care. Here's the thing: you can make good software with agents, if you exhibit good judgement and put yourself in the path as a gate on quality. Too many clues point at this being loop engineering. And, C for this task, given 100% agent authorship, gives me the ick. Seems like bad judgement or opting out of making judgement calls.

gchamonlive 3mo ago
Took a look at the readme and seems coherent enough. A readme is also a technical entrypoint, no problem in parts of it being generated, specially if you have quick start, tables and loose documentation there you need updating.