My experience is that the biggest factor is how large is the codebase, and can I zoom into a specific spot where the change needs to be made and implement it divorced from all the other context.
Since the answer to both of those in may day job is “large” and “only sometimes” the maximum benefit of an LLM to me is highly limited. I basically use it as a better search engine for things I can’t remember off hand how to do.
Also, I care about the quality of the code I commit (this code is going to be continuously worked on), and I write better code than the LLM, so I tend to rewrite it all anyway, which again allows the LLM to save me some time, but severely limits the potential upside.
When I’m writing one off bash scripts, yeah it’s vibe coding all the way.
Yeah, that makes sense. I think with a big enough codebase some specific tooling might be necessary, a generic “dump everything in the context” won’t help.
My experience is that the biggest factor is how large is the codebase, and can I zoom into a specific spot where the change needs to be made and implement it divorced from all the other context.
Since the answer to both of those in may day job is “large” and “only sometimes” the maximum benefit of an LLM to me is highly limited. I basically use it as a better search engine for things I can’t remember off hand how to do.
Also, I care about the quality of the code I commit (this code is going to be continuously worked on), and I write better code than the LLM, so I tend to rewrite it all anyway, which again allows the LLM to save me some time, but severely limits the potential upside.
When I’m writing one off bash scripts, yeah it’s vibe coding all the way.
Yeah, that makes sense. I think with a big enough codebase some specific tooling might be necessary, a generic “dump everything in the context” won’t help.