Comment by embedding-shape
11 hours ago
I think people tend to forget that not only do we ourselves have different skillsets and can be amazing at one thing but horrible but another, but this also applies to other people in the world! Far all we know, there is an amazing developer out there who without LLMs, might have been the single best developer in the country, but even this person might not be able to figure out how to effectively work with LLMs. And vice-versa too.
Maybe this «spearheading AI person» just sucks at AI related stuff, as clearly that approach is bananas, but they could still be a OK developer.
> Far all we know, there is an amazing developer out there who without LLMs, might have been the single best developer in the country, but even this person might not be able to figure out how to effectively work with LLMs. And vice-versa too.
If working with LLMs effectively means accepting subpar results or be a reverse centaur, then I’d be glad not to be able to work with them.
I’ve never seen a good example where AI is a net positive to any development workflow. No one argues against compilers, build tools, IDEs, task runners, deploy and orchestration tools. Because they are great levers that lets you create more with less effort.
Many developers have narrow job descriptions, and the creative, productive uses of AI aren’t really obvious.
Where it shines is glueing systems together or building one-off automations that would take days, or weeks, to figure out. It’s for things you don’t have time to figure out or didn’t think were possible.
> If working with LLMs effectively means accepting subpar results
Why would it mean that? That's one way of using them, sure. Personally, my code is better as I have more time to think about the software design than before, and I'm less avoidant of refactoring in my personal projects.
> I’ve never seen a good example where AI is a net positive to any development workflow
Alright, does that mean you also believe it's impossible then that anyone out there is using AI in a "net positive" way for their development workflow? Or just that you've never seen it, but you're open to it existing?
> Or just that you've never seen it, but you're open to it existing?
This one. Only a sith deals in absolute.
I don’t mind experiments to try to find methodologies for those tools. And I believe there are instances where they’ve been successfully used. The issue I have is the kind of generic statements that they are good enough to replace currently established methodologies. Like using AI is a panacea.
> Personally, my code is better as I have more time to think about the software design than before, and I'm less avoidant of refactoring in my personal projects
That’s a bit what I’m talking about. Have you investigated how it has helped you? And if there are other, more economical way to get the same result? Your statement seems more ritualistic than logical.
3 replies →
I think many people did argue against these things when they were new. Compilers, for instance, were seen as a waste of the computer's resources and produced less than optimal code.
Eh. The useful LLM usage I see is in internal tools (bugs don’t matter because the output or UI is the only thing that counts and they are throw away) or personal projects that otherwise wouldn’t exist.
Both of these can be quite invisible. But the benefit is there.
> No one argues against compilers, build tools, IDEs, task runners, deploy and orchestration tools.
Uhm ... I've heard quite alot arguing against IDEs. And I feel IDEs are too much of a lock in.