upvote
Anyone who's seen the author communicate here and on Lobsters will know that this particular critique irks them and they tend to react exactly like this when it comes up. It's a sore spot, and one the author should probably try to work through on their own since they seem to spend a lot of time vibecoding things.
reply
If you have 27 years of professional experience in this field and still think that you can have total knowledge of how a piece of functionality interacts with the overall codebase in a large software project, then I really don't know what to tell you. If that was the case we'd be writing perfect software that never has bugs.

Also, I have no idea what any of this has to do with LLMs. Nothing discussed here was LLM related in any way. Nor am I doing any apologetics for anything here. I'm stating basic facts that anybody with even a modicum of intellectual integrity would acknowledge.

But if you have any actual counterpoints to what I said then feel free to share them.

reply
Don't let the anti-AI people bug you. They seem to pounce on every thread and complain about LLM usage to the point where it drowns out any legitimate discussion.

I'm a heavy LLM user myself and it's reinvigorated my passion for coding again. I'm making things I never would have otherwise made. I probably wouldn't even be writing code anymore. I've worked on large codebases in my career and I felt like I understood them well. Still, it was so time consuming to get to that point in the first place and I would still have to familiarize myself all over again when working on components that didn't get touched often. An LLM makes it so much easier.

Ultimately, the developer has to own the code and be accountable for it. As long as that's true, I don't see what difference it makes what tools the developer uses. It's true that you can shoot yourself in the foot with an LLM, but you're probably going to shoot yourself in the foot without one too.

Anyway, cool project. Thanks for sharing it.

reply
Thanks, and completely agree with all that. If we treat LLMs as a simply a new tool that developers use, then nothing has really changed. The person working on the project is still responsible for all the decisions, code quality, and the direction of the project.

And these tools are fascinating to me because it's a completely new way to develop software. I've been writing code for over two decades now, and most code you end up writing isn't interesting or novel in any way. Any app will need to talk to a database, have some services, have a UI, and so on. Once you've built enough of these things, you're just repeating the same patterns over and over.

LLMs are something that's genuinely new and different. Nobody really knows how to get the most out of them. Everybody is still figuring out how they work, what they can do, what workflows to use around them. And that's really exciting because you can discover some new trick that nobody's tried before. So, I find this reinvigorating as well because it brings back the novelty and excitement that I remember having when I initially got into programming.

reply