For me, Copilot is the sweet spot (or insert your favorite auto-complete tool). It saves me significant time when coding and I’ve gotten really good at knowing when it pause for 1-2 seconds and then have it spit out the suggestion I hoped it would.
Agentic workflows are cool and have their place but essentially turn me into a full time code reviewer. Sometimes that’s acceptable/ok, sometimes I don’t like it. Essentially, if the agent gets even slightly off the path I want it on, I need to just do it myself. I give up on trying to prompt my out of a mistake it made. You get stuck thinking “one more prompt/round and it will fix the problem and everything will be perfect”, then you find yourself 4+ rounds in with the agent flip-flopping between 2 things it’s already tried.
repsiace · 7h ago
I work daily in Cursor, producing around 200k lines of code per week, though only a small portion ends up being truly effective (still significantly more than what I could achieve on my own before). I think we need to adapt to these changes and focus on shaping better workflows to fully harness the potential of AI.
joshstrange · 3h ago
That works out to 5K/hr (200k/5/8), that’s absurd verging on insane. It’s over a line of code a second.
I’d fire someone who was putting out that “code”.
Seriously, there is no way someone can review all that code so you must be solo (or at a place that doesn’t code review). If you aren’t reviewing your code then you are “vibe coding” (said with maximum derision) and what you are “building” is a house of cards.
mittensc · 7h ago
Why do you need yo write that much?
Is it all just throw away code to test out ideas?
Would libraries to help abstract stuff and you writing a few lines at a higher lever be better?
Since you throw away most of the code, could you design a bit before jumping to code and just develop something near desired solution?
boothby · 7h ago
I've gotta ask. Who wants you to write that much code and why?
repsiace · 7h ago
It's just one way of working. In reality, I only need a few thousand lines of effective code out of it. If I were to do it all on my own, it would likely take two to three times longer—perhaps with better or worse quality. While LLMs generate code incredibly fast, the full process of trial, error, and debugging takes more time. Additionally, since this involves multiple projects and contexts, a lot of junk code inevitably gets generated along the way.
mittensc · 6h ago
> In reality, I only need a few thousand lines of effective code out of it. If I were to do it all on my own, it would likely take two to three times longer—perhaps with better or worse quality.
Have you tried doing it on your own as comparison?
Any lessons why that might be true?
Are you missing some design/brainstorming stage that you are doing now by iterating through junk code and which might not be necessary?
You might be right now, but you gain experience that you otherwise lose by delegating to the LLM. With experience the reverse might be true.
d00mB0t · 8h ago
I think of AI as a better version of Google. There's a lot of Hype around AI and productivity, I don't think it will make anyone a 10x programmer.
cookiemonsieur · 5h ago
Exactly, for me it's just a glorified stack overflow.
mittensc · 7h ago
I am in the same boat.
I don't need AI to generate code.
Pipelines are non existant (who wants useless code?, just make better abstractions)
Copy-and-paste code is non existant - taboo to duplicate, just find libraries to reuse within the project or write them.
I don't need it to write tests, I want to write tests myself to force myself to think of the problem.
Code base is large enough that it's generally useless for search (and old tools work much better)
And I don't see what else it would be useful for though I'm trying. (writing a class skeleton?, maybe?, but then, I can do that fast as well)
herbst · 6h ago
From your examples the libraries are what AI is actually helpful for me.
If I find any API I want to use I let the Claude built an API wrapper for me. Or any other specific issues that typically end up in a Lib.
So a isolated, single purpose file that doesn't depend on any other files where the code base already includes similar files where it can steal the style from.
This is a situation where it does really well usually without breaking anything.
mittensc · 5h ago
Fair point, I'll give it a go to see for myself, thanks.
Alternative, if it's web calls then openAPI and a specific generator will work faster long term... (write generator once then import swagger files for whatever you need or tell claude to generate the swagger if not available?)
That would help with api changes longer term (just update swagger file, regen code and update where needed)
If it's actual library calls (C/C++), then why would wrapper be needed?, doesn't add yet-anothet-layer that makes things more difficult to grasp?
herbst · 4h ago
I am mostly coding with ruby so I constantly find myself wrapping APIs or Linux tools to get things done faster.
Usually I just send a link to the API doc with a sentence or two to let it wrap one or two functions leading to small, specialized and mostly efficient wrappers without overhead. Easy to fix should something change.
It's just a random aspect where I find AI to work really well for coding (for me).
herbst · 6h ago
Auto complete actually saves me a lot time. Discussing and fixing architecture Claude has built often takes just as long as just building it. But tab/automcomplete is crazy.
(Especially for html layouts and repetitive changes)
ifonlyenigmax · 6h ago
For me, AI mostly simplifies life rather than complicates it. Definitely a productivity helper, even if it’s not magic.
Agentic workflows are cool and have their place but essentially turn me into a full time code reviewer. Sometimes that’s acceptable/ok, sometimes I don’t like it. Essentially, if the agent gets even slightly off the path I want it on, I need to just do it myself. I give up on trying to prompt my out of a mistake it made. You get stuck thinking “one more prompt/round and it will fix the problem and everything will be perfect”, then you find yourself 4+ rounds in with the agent flip-flopping between 2 things it’s already tried.
I’d fire someone who was putting out that “code”.
Seriously, there is no way someone can review all that code so you must be solo (or at a place that doesn’t code review). If you aren’t reviewing your code then you are “vibe coding” (said with maximum derision) and what you are “building” is a house of cards.
Is it all just throw away code to test out ideas?
Would libraries to help abstract stuff and you writing a few lines at a higher lever be better?
Since you throw away most of the code, could you design a bit before jumping to code and just develop something near desired solution?
Have you tried doing it on your own as comparison?
Any lessons why that might be true?
Are you missing some design/brainstorming stage that you are doing now by iterating through junk code and which might not be necessary?
You might be right now, but you gain experience that you otherwise lose by delegating to the LLM. With experience the reverse might be true.
I don't need AI to generate code.
Pipelines are non existant (who wants useless code?, just make better abstractions)
Copy-and-paste code is non existant - taboo to duplicate, just find libraries to reuse within the project or write them.
I don't need it to write tests, I want to write tests myself to force myself to think of the problem.
Code base is large enough that it's generally useless for search (and old tools work much better)
And I don't see what else it would be useful for though I'm trying. (writing a class skeleton?, maybe?, but then, I can do that fast as well)
If I find any API I want to use I let the Claude built an API wrapper for me. Or any other specific issues that typically end up in a Lib.
So a isolated, single purpose file that doesn't depend on any other files where the code base already includes similar files where it can steal the style from.
This is a situation where it does really well usually without breaking anything.
Alternative, if it's web calls then openAPI and a specific generator will work faster long term... (write generator once then import swagger files for whatever you need or tell claude to generate the swagger if not available?)
That would help with api changes longer term (just update swagger file, regen code and update where needed)
If it's actual library calls (C/C++), then why would wrapper be needed?, doesn't add yet-anothet-layer that makes things more difficult to grasp?
Usually I just send a link to the API doc with a sentence or two to let it wrap one or two functions leading to small, specialized and mostly efficient wrappers without overhead. Easy to fix should something change.
It's just a random aspect where I find AI to work really well for coding (for me).
(Especially for html layouts and repetitive changes)