5 ms·

Strange to think they are probably triaged by LLMs at this point

by steve_adams_86 27d ago

danudey 27d ago
AI finding issues in code and reporting them so that an AI can review and triage them for another AI to fix.
- eszed 27d ago
  I mean, isn't that the dream? I don't know if that's sarcasm or not. I know it doesn't work, but that's the future we've been promised, right?
  - tymscar 27d ago
    Who promised it?
  - jldugger 27d ago
    It's certainly someone's dream: https://devhumor.com/media/dilbert-s-team-writes-a-minivan https://devhumor.com/media/dilbert-s-team-writes-a-minivan
  - fg137 27d ago
    If the same AIs don't hallucinate and create bugs in the first place. I don't know how much my own time is wasted on Claude imagining API response formats that never existed.
  - markus_zhang 27d ago
    Not my dream…
  - mrheosuper 27d ago
    Let's just say my dream does not involve babysitting some robot
  - nozzlegear 27d ago
    > I mean, isn't that the dream? Unironically: no.
  - CrimsonRain 27d ago
    Why it doesn't work? It is working for me. It is working for bun. It is working for others who actually embraces it and puts in the work to get it working.
    - tonyhart7 27d ago
      sadly someone didn't have free unlimited Fable and Opus like Bun team does
    - SaucyWrong 27d ago
      I recognize your username from other comment threads and would classify you as a bun fanatic, but even so, I’d hold off on saying, “it’s working for bun,” until 1.4.0 has been out of canary for, like, more than 24 hours. Most real users haven’t onboarded to it yet.
      - CrimsonRain 26d ago
        so first it was rust rewrite bad. Then rewrite with ai can never work. Then it will be riddled with bugs. It'll crash. It'll take years to fix. On the other hand, rewrite was mostly done in record time. New version added massive number of features. Also huge bug fixes. Being used by Claude code by millions of people. Successfully used by some others even in canary. After release, multiple companies immediately switched due to massive amounts of resource savings and performance gains (and publicly posted about it). Can there still be problems? Yes, I'm sure there will be. But denying the feat Oven pulled off with Bun in last few months is nothing but phobia/fud. Many people are already posted about testing new bun version and I have yet to see a single post where the issue is the latest versions of bun. In some cases people posted it doesn't work but that's due to node compatibility etc and it didn't work on previous version either. One does not need to be bun fanatic to see and call things as they are. PS: I like bun because I hate how js ecosystem requires 100s of packages to do anything and bun is aiming to include batteries. This is good.
- collinmanderson 27d ago
  That seems to be what's happening. Like 2-4 bots talking to each other, then Jarred Sumner just does the final merge with little comment. https://github.com/oven-sh/bun/pull/39743 https://github.com/oven-sh/bun/pull/39743 https://github.com/oven-sh/bun/pull/39735 https://github.com/oven-sh/bun/pull/39735
  - rafram 27d ago
    github-actions: "If you need a paragraph-long comment to justify why the workaround is OK, the code is wrong — fix the code" robobun: "The ordering is load-bearing: reclaiming before this block made is_dead_request true and hung a parked textStream read (caught by body.test.ts in CI). The comment pins that constraint." Ah, well, if something is load-bearing, then I guess that settles it. Need a comment to pin that constraint, in case a read is parked. These are words that normal humans commonly use in these ways. (Always striking how much Claude obsesses over the minutiae of method contracts and side effects, exhaustively documenting them in comments. It’s much happier figuring out how to reorder some method calls with nonobvious side effects so the code works than it is refactoring them not to do unexpected things!)

Strange to think they are probably triaged by LLMs at this point

danudey 27d ago

AI finding issues in code and reporting them so that an AI can review and triage them for another AI to fix.

eszed 27d ago
I mean, isn't that the dream? I don't know if that's sarcasm or not. I know it doesn't work, but that's the future we've been promised, right?
- tymscar 27d ago
  Who promised it?
- jldugger 27d ago
  It's certainly someone's dream: https://devhumor.com/media/dilbert-s-team-writes-a-minivan https://devhumor.com/media/dilbert-s-team-writes-a-minivan
- fg137 27d ago
  If the same AIs don't hallucinate and create bugs in the first place. I don't know how much my own time is wasted on Claude imagining API response formats that never existed.
- markus_zhang 27d ago
  Not my dream…
- mrheosuper 27d ago
  Let's just say my dream does not involve babysitting some robot
- nozzlegear 27d ago
  > I mean, isn't that the dream? Unironically: no.
- CrimsonRain 27d ago
  Why it doesn't work? It is working for me. It is working for bun. It is working for others who actually embraces it and puts in the work to get it working.
  - tonyhart7 27d ago
    sadly someone didn't have free unlimited Fable and Opus like Bun team does
  - SaucyWrong 27d ago
    I recognize your username from other comment threads and would classify you as a bun fanatic, but even so, I’d hold off on saying, “it’s working for bun,” until 1.4.0 has been out of canary for, like, more than 24 hours. Most real users haven’t onboarded to it yet.
    - CrimsonRain 26d ago
      so first it was rust rewrite bad. Then rewrite with ai can never work. Then it will be riddled with bugs. It'll crash. It'll take years to fix. On the other hand, rewrite was mostly done in record time. New version added massive number of features. Also huge bug fixes. Being used by Claude code by millions of people. Successfully used by some others even in canary. After release, multiple companies immediately switched due to massive amounts of resource savings and performance gains (and publicly posted about it). Can there still be problems? Yes, I'm sure there will be. But denying the feat Oven pulled off with Bun in last few months is nothing but phobia/fud. Many people are already posted about testing new bun version and I have yet to see a single post where the issue is the latest versions of bun. In some cases people posted it doesn't work but that's due to node compatibility etc and it didn't work on previous version either. One does not need to be bun fanatic to see and call things as they are. PS: I like bun because I hate how js ecosystem requires 100s of packages to do anything and bun is aiming to include batteries. This is good.
collinmanderson 27d ago
That seems to be what's happening. Like 2-4 bots talking to each other, then Jarred Sumner just does the final merge with little comment. https://github.com/oven-sh/bun/pull/39743 https://github.com/oven-sh/bun/pull/39743 https://github.com/oven-sh/bun/pull/39735 https://github.com/oven-sh/bun/pull/39735
- rafram 27d ago
  github-actions: "If you need a paragraph-long comment to justify why the workaround is OK, the code is wrong — fix the code" robobun: "The ordering is load-bearing: reclaiming before this block made is_dead_request true and hung a parked textStream read (caught by body.test.ts in CI). The comment pins that constraint." Ah, well, if something is load-bearing, then I guess that settles it. Need a comment to pin that constraint, in case a read is parked. These are words that normal humans commonly use in these ways. (Always striking how much Claude obsesses over the minutiae of method contracts and side effects, exhaustively documenting them in comments. It’s much happier figuring out how to reorder some method calls with nonobvious side effects so the code works than it is refactoring them not to do unexpected things!)