why would you want ai to suggest high level ideas ?
Why not?
It’s so hard to finish an idea that is not yours and is just suggested by AI
151–160 of 162 posts
Re: It’s so hard to finish an idea that is not yours and is just suggested by AI
#152Earlier quoted context omitted.
Why? You own the pager, I assume. You own the mental hit when something you let go live (especially with your name on the PR) leaks customer data or deleted someone’s work. And if you’re not reading your own work, is someone else during the PR? Are you reading other people’s PRs? How do you know what your product does and how it does it?
When the combustion engine was invented, and we got the means by which we could accelerate our trip by 10x, and at the same time scale it to multiple people, we didn't tell the humans to keep pushing the vehicles by their hands, didn't we?
Speed doesn't mean anything if you end up driving off a cliff.
Re: It’s so hard to finish an idea that is not yours and is just suggested by AI
#153Earlier quoted context omitted.
> Why are you submitting the code to the git repo like that, with all the wrong text? According to my enterprise architect I shouldn't be reviewing code, it's a waste of time in this new reality. I'm still doing it because it's going to be me answering that 3 AM call. But I don't know for how long I'll be allowed to swim upstream like that.
I have found manual reviewing of LLM generated code to be an uphill battle. LLMs does not believe in abstraction. So complexity spills everywhere. Some details in the lowest level might be handled separately in more than one place, at the higher levels. In a short while it is a copiously documented unreadable mess (both code and documentation). LLM written PR descriptions and comments are a sight to behold. I am not…
Yeah, that happens when you vibe code and just let the LLM be in control of everything. If you take responsibility for the architecture and instruct it to do things properly it will do them properly. You can tell it exactly how to do it or you can ask it to handle it in a way that avoids duplication, you can tell it to design a reusable abstraction for this usecase etc.
Re: It’s so hard to finish an idea that is not yours and is just suggested by AI
#154I have this problem even in codebases. Claude will work on something, and add detailed comments in which it extrapolates the from the design and confidently states intentions and decisions which aren't actually grounded in reality. Then, later sessions suffer when it reads back those hallucinations and treats them as canonical.
So, I admit that I'm finally getting into this "let Claude help you write code" stuff, and I'm enjoying it a bit for the stuff I, honestly, just don't want to write; but ... I still read it. I still review it. I still look at the code like I'm peer-reviewing it and go, "Uh ... I don't like this area at all. That's going to be really hard to debug at 3am" and so on. I guess my thought / question is: this is your code.…
The problem, in my experience is:
1. It writes SO MUCH code, in minutes, that theres no way I as a human can review it.
2. I am not very motivated to read/review this code anyway: it was cheaply written, by some _thing_ that is not going to improve from my feedback.
3. If you DO review it conscientiously , it becomes a never ending thing: you keep finding issue upon issue.
4. If you report the issues for fixes, the fixes normally fix that immediate issue, and typically add another parallel path/another option/another 100-odd lines of code, instead of a structural fix.
5. If the code base is large, and if you let AI write a meaningful amount of code in it, its no longer _your_ code. You lose the depth+width of understanding needed to reason thru things mentally, cause you no longer KNOW enough about the code.
6. If you do review seriously, and either fix things yourself, or have the ai/harness fix the issues for you, the rounds of fixes take so long, if you look back you realize it would have been better to just do it yourself in the first place.
My personal opinion there are really only two choices:
A. If you want to build FAST, using an agent, just let the agent write tests, validations, extensively, have it keep running them (it likes to call them gates), and just let it loose. Give up on the idea that its your code, and that you understand it. The bottom line becomes: does it work, and WHEN it breaks in weird ways, just use the agent to find and fix the issue (probably breaking something else in the process).
B. limit AI use for non trivial, prod-quality projects to limited research, very tiny targeted changes, write most of the code yourself still, and review every line. You won't get much speedup, maybe 20-30%, but it will still be YOUR code, and you will still be able to reason about it.
Re: It’s so hard to finish an idea that is not yours and is just suggested by AI
#155Earlier quoted context omitted.
I completely block all LLM comments via pi extension, it makes using them significantly more enjoyable. If the LLM wants to add a comment it must ASK me explicitly to do so. Seeing LLM comments in other peoples code is very upsetting because theres just so much meaningless noise.
What's the extension, please?
Author probably cobbler it together themselves.
Re: It’s so hard to finish an idea that is not yours and is just suggested by AI
#156Earlier quoted context omitted.
When the combustion engine was invented, and we got the means by which we could accelerate our trip by 10x, and at the same time scale it to multiple people, we didn't tell the humans to keep pushing the vehicles by their hands, didn't we?
Speed doesn't mean anything if you end up driving off a cliff.
Evidence so far does not suggest people driving off a cliff so while a valid concern it's not a likely one. We also acknowledged that the benefit of using a vehicle is such that it outnumbers the risks it may introduce. We never said there will be no risks attached.
Re: It’s so hard to finish an idea that is not yours and is just suggested by AI
#157Earlier quoted context omitted.
I have found manual reviewing of LLM generated code to be an uphill battle. LLMs does not believe in abstraction. So complexity spills everywhere. Some details in the lowest level might be handled separately in more than one place, at the higher levels. In a short while it is a copiously documented unreadable mess (both code and documentation). LLM written PR descriptions and comments are a sight to behold. I am not…
Yeah, that happens when you vibe code and just let the LLM be in control of everything. If you take responsibility for the architecture and instruct it to do things properly it will do them properly. You can tell it exactly how to do it or you can ask it to handle it in a way that avoids duplication, you can tell it to design a reusable abstraction for this usecase etc.
>If you take responsibility for the architecture and instruct it to do things properly it will do them properly.
The problem here is that after a while it is impossible to detect when such potential abstractions is overlooked in the generated code. Because it has become hard to reason about the existing code.
Not all work is green field.
Re: It’s so hard to finish an idea that is not yours and is just suggested by AI
#158I have this problem even in codebases. Claude will work on something, and add detailed comments in which it extrapolates the from the design and confidently states intentions and decisions which aren't actually grounded in reality. Then, later sessions suffer when it reads back those hallucinations and treats them as canonical.
So, I admit that I'm finally getting into this "let Claude help you write code" stuff, and I'm enjoying it a bit for the stuff I, honestly, just don't want to write; but ... I still read it. I still review it. I still look at the code like I'm peer-reviewing it and go, "Uh ... I don't like this area at all. That's going to be really hard to debug at 3am" and so on. I guess my thought / question is: this is your code.…
Yeah - the comments it writes are often "waypoint comments" [1] - great for the LLM during creation but just crap for us - I ask it to remove those before committing.
[1] Not sure if I read that or came up with it.
Re: It’s so hard to finish an idea that is not yours and is just suggested by AI
#159Earlier quoted context omitted.
So, I admit that I'm finally getting into this "let Claude help you write code" stuff, and I'm enjoying it a bit for the stuff I, honestly, just don't want to write; but ... I still read it. I still review it. I still look at the code like I'm peer-reviewing it and go, "Uh ... I don't like this area at all. That's going to be really hard to debug at 3am" and so on. I guess my thought / question is: this is your code.…
Yeah - the comments it writes are often "waypoint comments" [1] - great for the LLM during creation but just crap for us - I ask it to remove those before committing. [1] Not sure if I read that or came up with it.
I believe the general phenomenon is metadiscourse and those in specific are signposting constructions.
Re: It’s so hard to finish an idea that is not yours and is just suggested by AI
#160Earlier quoted context omitted.
I completely block all LLM comments via pi extension, it makes using them significantly more enjoyable. If the LLM wants to add a comment it must ASK me explicitly to do so. Seeing LLM comments in other peoples code is very upsetting because theres just so much meaningless noise.
Which extension is it?
Its a personal extension i wrote myself, maybe I should put it up somewhere.. Its so simple though i dont know if its worth it vs just "go build it yourself"