Earlier 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?
It’s so hard to finish an idea that is not yours and is just suggested by AI
171–180 of 194 posts
Re: It’s so hard to finish an idea that is not yours and is just suggested by AI
#172Earlier 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 used to. I've stopped in recent months, only bec…
Exactly. That would mean going back to square one, and I also personally don't review the code anymore but I am more focused on asking the model to demonstrate the value it created through benchmarks, workload-generators, and e2e tests. Mostly it proves as a valid approach, barring the bugs the model can introduce to value-demonstrating benchmarks which can of course skew the evidence on hypotheses, and thus code tra…
Re: It’s so hard to finish an idea that is not yours and is just suggested by AI
#173Earlier quoted context omitted.
>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.
I have wondered about this. Can’t you ask the AI to find the patterns than need abstracting?
I find myself having to use Claude to untangle its own mess piece by piece, a as it charged full steam ahead with the design we made together. However, not everything can be foreseen in a design, unless you go full waterfall. Sometimes I find myself in front of a mountain of bad abstractions stemming from a subtle oversight in the design. Before AI coding, I would find details while coding and catch them in time before they became sinful abominations
Re: It’s so hard to finish an idea that is not yours and is just suggested by AI
#174Earlier quoted context omitted.
you'd probs want a commit hook for that
Does "don't write comments" not work?
You’re using a non-deterministic algorithm to generate output. If you want deterministic rules applied to it, you have to use deterministic systems to do it.
Re: It’s so hard to finish an idea that is not yours and is just suggested by AI
#175Earlier 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.…
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 f…
Re: It’s so hard to finish an idea that is not yours and is just suggested by AI
#176Earlier quoted context omitted.
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 f…
Route A seems genuinely horrifying to me - maybe not for small and/or helper scripts; but for anything substantial. For anything that bites you or someone else hard when things go bad. I don’t want a vibe-coded, mass-produced diabetes tracking app, or banking tool, or tax management software. I don’t want a vibe-coded power grid analysis software. I don’t care if a person’s little, local scripting thing is vibe-coded…
Re: It’s so hard to finish an idea that is not yours and is just suggested by AI
#177Earlier 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 used to. I've stopped in recent months, only bec…
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?
Re: It’s so hard to finish an idea that is not yours and is just suggested by AI
#178Earlier quoted context omitted.
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
#179Earlier quoted context omitted.
Route A seems genuinely horrifying to me - maybe not for small and/or helper scripts; but for anything substantial. For anything that bites you or someone else hard when things go bad. I don’t want a vibe-coded, mass-produced diabetes tracking app, or banking tool, or tax management software. I don’t want a vibe-coded power grid analysis software. I don’t care if a person’s little, local scripting thing is vibe-coded…
Route A is good for rapid, disposable prototyping. If you ever have a stray thought, “I wonder how this would work if the whole paradigm were turned sideways”, you now have a chance to preview a “working” version of your idea. If you like it, discard the code and reimplement it correctly. In this way, I think it can be a good adjunct to sketches and other lofi prototyping techniques. Just don’t outsource the creative…
That’s not “disposable prototyping” that’s whole versions of the codebase written with barely a human in sight.
Re: It’s so hard to finish an idea that is not yours and is just suggested by AI
#180Earlier quoted context omitted.
The ultimate goal of project capitalism is to make ownership the only thing in the world that’s valued or valuable. The only thing that matters is how much and who you own.
The actual goal of capitalism is the direct the impulses of the capitalist to align with the interests of the public.