7 ms·

I have to imagine that like pair programming, this multi-AI approach would be significantly more tiring than one-window, one-programmer coding. Do you have to f

I have to imagine that like pair programming, this multi-AI approach would be significantly more tiring than one-window, one-programmer coding. Do you have to force yourself to take breaks to keep up your stamina?

throw-10-13 1y ago
The human context window is the limiting factor. That and testing/reviewing the insane amounts of ai slop this method generates.
- csar 1y ago
  If you're getting AI slop you're doing it wrong. You should be getting high quality code. Of course that's easier said than done, but AI slop is a sign that things have gone off the rails.
  - throw-10-13 1y ago
    Spare me the koolaid.
  - segfaultex 1y ago
    I have scarcely gotten decent code. The best a model has spat out is 'fine', which is ok for menial tasks. I have yet to see anyone show me an AI generated project that I'd be willing to put into production. IDK, I feel like 'vibe coders' or people who heavily rely on LLM's have allowed their skills (if they ever existed) to atrophy such that they're generally not great at assessing the output from models.
XenophileJKO 1y ago
Well I don't use as many instances as they do, but using codex for example will take some time researching the code. It mostly just becomes a practice so that I don't have to wait for the model, I just context switch to a different one. It probably helps that I am ADHD, I don't pay much of a cost to ping pong around. So I might tell one to look back in the git history to when something was removed and add it back into a class. So it will figure out what commit added it, what removed it, and then add the code back in. While that terminal is doing that, on another I can kick off another agent to make some fixes for something else that I need to knock out in another project. I just ping pong back to the first window to look at the code and tell it to add a new unit test for the new possible state inside the class it modified and I'm done. I may also periodically while working have a question about a best practice or something that I'll kick off in browser and leave it running to read later. This is not draining, and I keep a flow because I'm not sitting and waiting on something, they are waiting on me to context switch back.
joshribakoff 1y ago
Its bad because basic stuff like “please commit these changes” can sometimes take 10+ minutes at times and causes it to spiral doing tangential stuff. By running them in parallel you avoid sitting there watching paint dry for a task that takes 3 seconds by hand. Its really not comparable to a junior, its more comparable to a salty maliciously compliant optimized to burn tokens and deceive you.

throw-10-13 1y ago

The human context window is the limiting factor. That and testing/reviewing the insane amounts of ai slop this method generates.

csar 1y ago
If you're getting AI slop you're doing it wrong. You should be getting high quality code. Of course that's easier said than done, but AI slop is a sign that things have gone off the rails.
- throw-10-13 1y ago
  Spare me the koolaid.
- segfaultex 1y ago
  I have scarcely gotten decent code. The best a model has spat out is 'fine', which is ok for menial tasks. I have yet to see anyone show me an AI generated project that I'd be willing to put into production. IDK, I feel like 'vibe coders' or people who heavily rely on LLM's have allowed their skills (if they ever existed) to atrophy such that they're generally not great at assessing the output from models.

XenophileJKO 1y ago

Well I don't use as many instances as they do, but using codex for example will take some time researching the code. It mostly just becomes a practice so that I don't have to wait for the model, I just context switch to a different one. It probably helps that I am ADHD, I don't pay much of a cost to ping pong around. So I might tell one to look back in the git history to when something was removed and add it back into a class. So it will figure out what commit added it, what removed it, and then add the code back in. While that terminal is doing that, on another I can kick off another agent to make some fixes for something else that I need to knock out in another project. I just ping pong back to the first window to look at the code and tell it to add a new unit test for the new possible state inside the class it modified and I'm done. I may also periodically while working have a question about a best practice or something that I'll kick off in browser and leave it running to read later. This is not draining, and I keep a flow because I'm not sitting and waiting on something, they are waiting on me to context switch back.

joshribakoff 1y ago

Its bad because basic stuff like “please commit these changes” can sometimes take 10+ minutes at times and causes it to spiral doing tangential stuff. By running them in parallel you avoid sitting there watching paint dry for a task that takes 3 seconds by hand. Its really not comparable to a junior, its more comparable to a salty maliciously compliant optimized to burn tokens and deceive you.