LLM-Assisted Coding
Discussions revolve around experiences using LLMs for programming tasks, debating their benefits for speeding up development and learning versus drawbacks like producing low-quality code, bugs, and the risks of over-reliance without understanding.
Activity Over Time
Top Contributors
Keywords
Sample Comments
LLMs can help with programming. But you cannot just copy/paste the code from LLMs and push to production. You need to understand the code that LLMs are producing otherwise soon or later you will get in trouble.
It's happened to me recently, I've relied so much on LLMs for coding and after hours of spinning the wheel, I realized, it has no idea, when it fixes something it's mostly a guess, most I've the time we're just debugging by adding logging statements and the code we've created looks crap and is mostly wrong, full of fluff, or hard to understand.I've been coding without my LLM for 2 hours and it's just more productive...yes it's good for getting thin
I really think people are approaching LLMs wrong when it comes to code. Just directing an agent to make you something you’re unfamiliar with is always going to end up with this. It’s much better to have a few hours chat with the LLM and learn some about the topic, multiple times over many days, and then start.And ask questions and read all the code and modify it yourself; and read the compile errors and try to fix then yourself; etc. Come back to the LLM when you’re stuck.Having the machin
You seem to be evaluating the LLM based on a single response rather than the whole "conversation." The user usually interacts with the LLM through 3-4 different responses to reach the right answer, which is valuable in itself. They're using both systems just as anyone would in a conversation.I find LLMs useful for:- Building bridges from familiar concepts to new ones.- Checking my analysis and implementation for mistakes and gaps. This includes detecting subtle logic erro
One thing I've noticed about working with LLMs is that it's forcing me to get _better_ at explaining my intent and fully understanding a problem before coding. Ironically, I'm getting less vibey because I'm using LLMs.The intuition is simple: LLMs are a force multiplier for the coding part, which means that they will produce code faster than I will alone. But that means that they'll also produce _bad_ code faster than I will alone (where by "bad" I me
LLM isn't replacing any actual coders... yet!
Is most code not written by LLMs these days anyway?
Your experience in coding is enough, you need more practice in "problem solving" with crazy ideas and working through them to the finish line.Besides, this is just a thin layer on an LLM, with questionable actual quality. Learn to do the real work, no magic machine can take learning and skill building off your shoulders.
This over reliance on llms is crazy. People are going to forget how to code. Sometimes the llm makes up shit or uses the wrong version of the API. Sometimes it's easier to look up the documentation and write some code.
You're only show as your typing speed and working memory. I noticed that LLM quickly spits out the code and thus I can iterate faster while typing myself I have focus on course and thus lose a lot of design context. Overall I haven't found any benefit of LLM. For me, it's just a probabilistic text generator that guesses my intent.