Live data from Hacker News

The current state of LLM-driven development

blog.tolki.dev

81–90 of 244 posts

Re: The current state of LLM-driven development

#81
People that comment on and get defensive about this bit:

> Learning how to use LLMs in a coding workflow is trivial. There is no learning curve. You can safely ignore them if they don’t fit your workflows at the moment.

How much of your workflow or intuition from 6 months ago is still relevant today? How long would it take to learn the relevant bits today?

Keep in mind that Claude Code was released less than 6 months ago.

Re: The current state of LLM-driven development

#82
post #25
post #11

I have a biased opinion since I work for a background agent startup currently - but there are more (and better!) out there than Jules and Copilot that might address some of the author's issues.

And those mythical better tools tools that you didn't even bother to mention are?

Presumably if they did, they would be accused of promoting their startup :)

Re: The current state of LLM-driven development

#83

LLM’s are basically glorified slot machines. Some people try very hard to come up with techniques or theories about when the slot machine is hot, it’s only an illusion, let me tell you, it’s random and arbitrary, maybe today is your lucky day maybe not. Same with AI, learning the “skill” is as difficult as learning how to google or how to check stackoverflow, trivial. All the rest is luck and how many coins do you ha…

We know what random* looks like: a coin toss, the roll of a die. Token generation is neither.

[deleted]

Re: The current state of LLM-driven development

#84
post #63
post #29

Earlier quoted context omitted.

This is all just ignorance. We've all worked with LLMs and know that creating an effective workflow is not trivial and it varies based on the tool.

Define "not trivial". Obviously, experience helps, as with any tool. But it's hardly rocket science. It seems to me the biggest barrier is that the person driving the tool needs to be experienced enough to recognize and assist when it runs into issues. But that's little different from any sophisticated tool. It seems to me a lot of the criticism comes from placing completely unrealistic expectations on an LLM. "It's…

I don’t think anyone expects perfection. Programs crash, drives die, and computers can break anytime. But we expect our tools to be reliable and not fight with it everyday to get it to work.

I don’t have to debug Emacs every day to write code. My CI workflow just runs every time a PR is created. When I type ‘make tests’, I get a report back. None of those things are perfect, but they are reliable.

Re: The current state of LLM-driven development

#85

LLM’s are basically glorified slot machines. Some people try very hard to come up with techniques or theories about when the slot machine is hot, it’s only an illusion, let me tell you, it’s random and arbitrary, maybe today is your lucky day maybe not. Same with AI, learning the “skill” is as difficult as learning how to google or how to check stackoverflow, trivial. All the rest is luck and how many coins do you ha…

This is not a good analogy. The parameters of slot machines can be changed to make the casino lose money. Just because something is random, doesn't mean it is useless. If you get 7 good outputs out of 10 from an LLM, you can still use it for your benefit. The frequency of good outputs and how much babysitting it requires determine whether it is worth using or not. Humans make mistakes too, although way less often.

Re: The current state of LLM-driven development

#86
Strange post. It reads in part like an incoherent rant and in part as a well made analysis.

It’s mostly on point though. Although, in recent years I’ve been assigned to manage and plan projects at work, and the skills I’ve learnt from that greatly help to get effective results from an LLM I think.

Re: The current state of LLM-driven development

#87

LLM’s are basically glorified slot machines. Some people try very hard to come up with techniques or theories about when the slot machine is hot, it’s only an illusion, let me tell you, it’s random and arbitrary, maybe today is your lucky day maybe not. Same with AI, learning the “skill” is as difficult as learning how to google or how to check stackoverflow, trivial. All the rest is luck and how many coins do you ha…

This is not a good analogy. The parameters of slot machines can be changed to make the casino lose money. Just because something is random, doesn't mean it is useless. If you get 7 good outputs out of 10 from an LLM, you can still use it for your benefit. The frequency of good outputs and how much babysitting it requires determine whether it is worth using or not. Humans make mistakes too, although way less often.

I didn’t say it’s useless.

Re: The current state of LLM-driven development

#88
post #82
post #25

Earlier quoted context omitted.

And those mythical better tools tools that you didn't even bother to mention are?

Presumably if they did, they would be accused of promoting their startup :)

But he said there are more and better out there. "More" implies more than one :)

And promoting own startups are usually okay if that is phrased okay :)

Re: The current state of LLM-driven development

#89
> By being particularly bad at anything outside of the most popular languages and frameworks, LLMs force you to pick a very mainstream stack if you want to be efficient.

Do they? I’ve found Clojure-MCP[1] to be very useful. OTOH, I’m not attempting to replace myself, only augment myself.

1: https://github.com/bhauman/clojure-mcp

Re: The current state of LLM-driven development

#90
post #88
post #82

Earlier quoted context omitted.

Presumably if they did, they would be accused of promoting their startup :)

But he said there are more and better out there. "More" implies more than one :) And promoting own startups are usually okay if that is phrased okay :)

By no means are better background agents "mythical" as you claim. I didn't bother to mention them as it is easy enough to search for asynchronous/background agents yourself.

Devin is perhaps the one that is most fully featured and I believe has been around the longest. Other examples that seem to be getting some attention recently are Warp, Cursor's own background agent implementation, Charlie Labs, Codegen, Tembo, and OpenAI's Codex.

I do not work for any of the aforementioned companies.

Post reply on HN