I am frankly tired of seeing this kind of post on HN. I feel like the population of programmers is bifurcating into those who are committed to mastering these tools, learning to work around their limitations and working to leverage their strengths… and those who are committed to complaining about how they aren’t already perfect Culture Ship Minds. We get it. They’re not superintelligent at everything yet. They couldn…
I trusted an LLM, now I'm on day 4 of an afternoon project
51–60 of 215 posts
Re: I trusted an LLM, now I'm on day 4 of an afternoon project
#52I've had a similar experience, shipping new features at incredible speed, then waste a ton of time going down the wrong track trying to debug something because the LLM gave me a confidently wrong solution.
Re: I trusted an LLM, now I'm on day 4 of an afternoon project
#53> AI isn’t a co-pilot; it’s a junior dev faking competence. Trust it at your own risk. This is a good take that tracks with my (heavy) usage of LLMs for coding. Leveraging productive-but-often-misguided junior devs is a skill every dev should actively cultivate!
Re: I trusted an LLM, now I'm on day 4 of an afternoon project
#54Earlier quoted context omitted.
> I am frankly tired of seeing this kind of post on HN. You've been here since 2016 and this is the kind of posting that finally gets to you? How in the world have you avoided all the shitposts in the last decade? What is your secret?
It’s the fact that it’s the same thing over and over. The 100th case of “Well I had a bad experience using LLM for coding!” is not interesting.
Re: I trusted an LLM, now I'm on day 4 of an afternoon project
#55In my experience LLMs will help you with things that have been solved thousands of times before and are just a matter of finding some easily researched solution. The very moment when you try to go off the beaten path and do something unconventional or stuff that most people won't have written a lot about, it gets more tricky. Just consider how many people will know how to configure some middleware in a Node.js projec…
> vs most things related to hardware or low level work. counter point: https://github.com/ggerganov/llama.cpp/pull/11453 > This PR provides a big jump in speed for WASM by leveraging SIMD instructions for qX_K_q8_K and qX_0_q8_0 dot product functions. > Surprisingly, 99% of the code in this PR is written by DeekSeek-R1. The only thing I do is to develop tests and write prompts (with some trials and errors)
Re: I trusted an LLM, now I'm on day 4 of an afternoon project
#56I've had a similar experience, shipping new features at incredible speed, then waste a ton of time going down the wrong track trying to debug something because the LLM gave me a confidently wrong solution.
Seems like LLMs would be well suited for test driven development. A human writes tests and the LLM can generate code passing all tests; ending with a solution that meets the humans expectations.
Re: I trusted an LLM, now I'm on day 4 of an afternoon project
#57For anything remotely complex, this is dead on. I use various models daily to help with coding, and more often than not, I have to just DIY it or start brand new chats (because the original context got overwhelmed and started hallucinating).
This is why it's incredibly frustrating to see VCs and AI founders straight-up gaslighting people about what this stuff can (or will) do. They're trying to push this as a "work killer," but really, it's going to be some version of the opposite: a mess creator that necessitates human intervention.
Where we're at is amazing, but we've got a loooong way to go before we can be on hover crafts sipping sodas Wall-E style.
Re: I trusted an LLM, now I'm on day 4 of an afternoon project
#58Counterexample: Ive been able to complete more side projects in the last month leveraging llms than i have ever in my life. One of which I believe to have potential as a viable product, and another which involved complicated rust `no_std` and linker setup for compiling rust code onto bare metal RISCV from scratch. I think the key to being successful here is to realize that you're still at the wheel as an engineer. Th…
If a topic is well represented in those places, then you will get your answer quicker and it can be to some extent shaped to your use case.
If the topic is not well represented there, then you will get circular nonsense.
You can say “obviously, that’s the training data”, and that’s true, and I do find it obvious personally, but the reaction to LLMs as some kind of second coming does not align with this reality.
Re: I trusted an LLM, now I'm on day 4 of an afternoon project
#59I am frankly tired of seeing this kind of post on HN. I feel like the population of programmers is bifurcating into those who are committed to mastering these tools, learning to work around their limitations and working to leverage their strengths… and those who are committed to complaining about how they aren’t already perfect Culture Ship Minds. We get it. They’re not superintelligent at everything yet. They couldn…
are you claiming LLMs function like computer program instructions? like they clearly don't operate like that at all.
Re: I trusted an LLM, now I'm on day 4 of an afternoon project
#60> AI isn’t a co-pilot; it’s a junior dev faking competence. Trust it at your own risk. This is a good take that tracks with my (heavy) usage of LLMs for coding. Leveraging productive-but-often-misguided junior devs is a skill every dev should actively cultivate!
It is quite remarkable that we are already at the stage where saying "this AI is about as competent as an inexperienced college graduate" constitutes criticism . It is entirely proper for people to be engaging sceptically with LLMs at their current level of capability, but I think we should also keep in mind the astonishingly rapid growth rate in their performance. LLMs were a toy two years ago, they're now a useful…