zlacker

>>scared+(OP)
LLM anything makes me queasy. Why would any self respecting software developer use this tripe? Learn how to write good software. Become an expert in the trade. AI anything will only dig a hole for software to die in. Cheapens the product, butchers the process and absolutely decimates any hope for skill development for future junior developers.

I'll just keep chugging along, with debian, python and vim, as I always have. No LLM, no LSP, heck not even autocompletion. But damn proud of every hand crafted, easy to maintain and fully understood line of code I'll write.

>>jgb198+Wg4
I use it all the time, and it has accelerated my output massively.

Now, I don't trust the output - I review everything, and it often goes wrong. You have to know how to use it. But I would never go back. Often it comes up with more elegant solutions than I would have. And when you're working with a new platform, or some unfamiliar library that it already knows, it's an absolute godsend.

I'm also damn proud of my own hand-crafted code, but to avoid LLMs out of principal? That's just luddite.

20+ years of experience across game dev, mobile and web apps, in case you feel it relevant.

>>cachvi+Qp4
I have a hard time being sold on “yea it’s wrong a lot, also you have to spend more time than you already do on code review.”

Getting to sit down and write the code is the most enjoyable part of the job, why would I deprive myself of that? By the time the problem has been defined well enough to explain it to an LLM sitting down and writing the code is typically very simple.

>>ericwo+Qw4
For me it's typically wrong not in a fundamental way but a trivial way like bad import paths or function calls, like if I forgot to give it relevant context.

And yet the time it takes me to use the LLM and correct its output is usually faster than not using it at all.

Over time I've developed a good sense for what tasks it succeeds at (or is only trivially wrong) and what tasks it's just not up for.