News for hackers. Stuff that matters.
Re:Unix philosophy and filesystem access makes Claude Code a... by derefr on Wednesday October 01, 2025 @03:19PM (#45442053)
It's a bit annoying that you have to tell it to do it, though. Humans (or at least programmers) "build the tools to solve the problem" so intuitively and automatically when the problem starts to "feel hard", that it doesn't often occur to the average programmer that LLMs don't think like this.

When you tell an LLM to check the code for errors, the LLM could simply "realize" that the problem is complex enough to warrant building [or finding+configuring] an appropriate tool to solve the problem, and so start doing that... but instead, even for the hardest problems, the LLM will try to brute-force a solution just by "staring at the code really hard."

(To quote a certain cartoon squirrel, "that trick never works!" And to paraphrase the LLM's predictable response, "this time for sure!")

Re:Unix philosophy and filesystem access makes Claude Code a... by libraryofbabel on Wednesday October 01, 2025 @04:32PM (#45443083)
As the other commenter said, these days Claude Code often does actually reach for a script on its own, or for simpler tasks it will do a bash incantation with grep and sed.

That is for tasks where a programmatic script solution is a good idea though. I don't think your example of "check the code for errors" really falls in that category - how would you write a script to do that? "Staring at the code really hard" to catch errors that could never have been caught with any static analysis tool is actually where an LLM really shines! Unless by "check for errors" you just meant "run a static analysis tool", in which case sure, it should run the linter or typechecker or whatever.

Re:Unix philosophy and filesystem access makes Claude Code a... by derefr on Wednesday October 01, 2025 @07:17PM (#45444767)
Running “the” existing configured linter (or what-have-you) is the easy problem. The interesting question is whether the LLM would decide of its own volition to add a linter to a project that doesn’t have one; and where the invoking user potentially doesn’t even know that linting is a thing, and certainly didn’t ask the LLM to do anything to the project workflow, only to solve the immediate problem of proving that a certain code file is syntactically valid / “not broken” / etc.

After all, solving an immediate problem that seems like it could come up again, by “taking the opportunity” to solve the problem from now on by introducing workflow automation to solve the problem, is what an experienced human engineer would likely do in such a situation (if they aren’t pressed for time.)

Re:Unix philosophy and filesystem access makes Claude Code a... by theshrike79 on Friday October 03, 2025 @02:26AM (#45459659)
I've had multiple cases where it will rather write a script to test a thing than actually adding a damn unit test for it :)
Re:Unix philosophy and filesystem access makes Claude Code a... by kuboble on Thursday October 02, 2025 @04:29AM (#45447416)
I have the opposite experience.

I used claude to translate my application and I asked him to translate each text in the application to his best abilities.

That worked great for one view, but when I asked him to translate the rest of the application in the same fashion he got lazy and started to write a script to substitute some words instead of actually translating sentences.

Re:Unix philosophy and filesystem access makes Claude Code a... by coldtea on Thursday October 02, 2025 @06:38AM (#45448054)
>It's a bit annoying that you have to tell it to do it, though.

https://www.youtube.com/watch?v=kBLkX2VaQs4

Re:Unix philosophy and filesystem access makes Claude Code a... by lloeki on Thursday October 02, 2025 @08:30AM (#45448781)
> Humans (or at least programmers) "build the tools to solve the problem" so intuitively and automatically when the problem starts to "feel hard", that it doesn't often occur to the average programmer that LLMs don't think like this.

Hmm. My experience of "the average programmer" doesn't look like yours and looks more like the LLM :/

I'm constantly flabbergasted as to how way too many devs fumble through digging into logs or extracting information or what have you because it simply doesn't occur to them that tools can be composed together.

Re:Unix philosophy and filesystem access makes Claude Code a... by visarga on Thursday October 02, 2025 @10:03AM (#45449725)
Cursor likes to create one-off scripts, yesterday it filled a folder with 10 of them until it figured out a bug. All the while I was thinking - will it remember to delete the scripts or is it going to spam me like that?
Re:Unix philosophy and filesystem access makes Claude Code a... by phito on Thursday October 02, 2025 @10:24AM (#45450012)
> Humans (or at least programmers) "build the tools to solve the problem" so intuitively and automatically

From my experience, only a few rare devs do this. Most will stick with (broken/wrong) GUI tools they know made by others, by convenience.