Live data from Hacker News

Unix philosophy and filesystem access makes Claude Code amazing

alephic.com

51–60 of 223 posts

Re: Unix philosophy and filesystem access makes Claude Code amazing

#51
>The filesystem is a great tool to get around the lack of memory and state in LLMs and should be used more often.

This feels a bit like rediscovering stateless programming. Obviously the filesystem contents can actually change, but the idea of an idempotent result when running the same AI with the same command(s) and getting the same result would be lovely. Even better if the answer is right.

Re: Unix philosophy and filesystem access makes Claude Code amazing

#52
post #50

LLMs are one large binary that does everything (maybe, if you are lucky today) exact opposite of the unix philosophy

> LLMs are one large binary that does everything

Well, no, they aren't, but the orchestration frameworks in which they are embedded sometimes are (though a lot of times a whole lot of that everything is actually done by separate binaries the framework is made aware of via some configuration or discovery mechanism.)

Re: Unix philosophy and filesystem access makes Claude Code amazing

#53
post #10

> Anyone who can't find use cases for LLMs isn't trying hard enough That's an interesting viewpoint from an AI marketing company. I think the essential job of marketing is to help people make the connection between their problems and your solutions. Putting all on them in a kind of blamey way doesn't seem like a great approach to me.

That's fair. But it's what I believe. I spend a lot of time inside giant companies and there are too many people waiting for stone tablets to come down the mountain with their use cases instead of just playing with this stuff.

I think that a lot of very basic LLM use cases come down to articulating your need. If you're not the sort of person who's highly articulate, this is likely to be difficult for you.

I'm personally in the habit of answering even slightly complex questions by first establishing shared context - that is, I very carefully ensure that my conversational partner has exactly the same understanding of the situation that I do. I do this because it's frequently the case that we don't have a lot of overlap in our understanding, or we have very specific gaps or contradictions in our understanding.

If you're like many in this industry, you're working in a language other than what you were raised in, making all of this more difficult.

Re: Unix philosophy and filesystem access makes Claude Code amazing

#54
post #10

> Anyone who can't find use cases for LLMs isn't trying hard enough That's an interesting viewpoint from an AI marketing company. I think the essential job of marketing is to help people make the connection between their problems and your solutions. Putting all on them in a kind of blamey way doesn't seem like a great approach to me.

That's fair. But it's what I believe. I spend a lot of time inside giant companies and there are too many people waiting for stone tablets to come down the mountain with their use cases instead of just playing with this stuff.

I do understand about enterprise decision-making.

I think it's the pengiun approach to risk management -- they know they need to jump in the water to get where they need to go, but they don't know where the orcas are. So they jostle closer and closer to the edge, some fall in, and the rest see what happens.

BTW, I probably shouldn't have only commenting on the small part at the end that annoyed me. I'm fascinated by the idea that LLMs make highly custom software feasible, like your "claudsidian" system... that people will be able to get the software they want by describing it rather than being limited to finding something preexisting and having to adapting to it. As you point out, the unix philosophy is one way -- simple, unopinionated, building blocks an LLM can compose out of user-level prompts.

Re: Unix philosophy and filesystem access makes Claude Code amazing

#56

Earlier quoted context omitted.

I disagree actually. Saying things like “everyone else managed to figure it out” is a way of creating FOMO. It might not be the way you want to do it, marketing doesn’t have to be nice (or even right) to work.

"Good marketing" doesn't have to mean "Marketing that is maximally effective" Filling food with opioids would be great for business, but hopefully you understand how that is not "good business"

True, but you are arguing about the merit of the actual product, which neither I nor the comment I responded to were talking about at all. Marketing tactics can be applied to good and bad products, and FOMO is a pretty common one everywhere, from "limited remaining" to "early adopters lock in at $10/mo for life" to "everyone else is doing it".

Re: Unix philosophy and filesystem access makes Claude Code amazing

#57
post #50

LLMs are one large binary that does everything (maybe, if you are lucky today) exact opposite of the unix philosophy

wait until you find out about human programmers...

They write the individual tools that do the one specific thing?

Re: Unix philosophy and filesystem access makes Claude Code amazing

#58
post #8

I do really like the Unix approach Claude Code takes, because it makes it really easy to create other Unix-like tools and have Claude use them with basically no integration overhead. Just give it the man page for your tool and it'll use it adeptly with no MCP or custom tool definition nonsense. I built a tool that lets Claude use the browser and Claude never has an issue using it.

The light switch moment for me is when I realized I can tell claude to use linters instead of telling it to look for problems itself. The later generally works but having it call tools is way more efficient. I didn't even tell it what linters to use, I asked it for suggestions and it gave me about a dozen of suggestions, I installed them and it started using them without further instruction. I had tried coding with C…

The lightbulb moment for me was to have it make me a smoke test and to tell to run the test and fix issues (with the code it generated) until it passes. iterate over all features in the Todo.md (that I asked it to make). Claude code will go off and do stuff for I dunno, hours?, while I work on something else.

Re: Unix philosophy and filesystem access makes Claude Code amazing

#59

Earlier quoted context omitted.

>No, that’s not what it means. That's fair but it's what I believe. ...see? Being consistent with stating your beliefs isn't the same as engaging with and about those beliefs. Advertising isn't conversation. Evangelism isn't discussion.

I'm trying to engage with you on this, but I'm really not sure what you're getting at. You originally stated "I think the essential job of marketing is to help people make the connection between their problems and your solutions. Putting all on them in a kind of blamey way doesn't seem like a great approach to me." I agree that's the job of marketing, but I'm not someone who markets AI, I'm someone who helps large ma…

That was somebody else that said that.

Re: Unix philosophy and filesystem access makes Claude Code amazing

#60

I've done exactly this with MCP { "name": "unshare_exec", "description": "Run a binary in isolated Linux namespaces using unshare", "inputSchema": { "type": "object", "properties": { "binary": {"type": "string"}, "args": {"type": "array", "items": {"type": "string"}} }, "required": ["binary"], "additionalProperties": false } } It started as unshare and ended up being a bit of a yakshaving endeavor to make things work…

Would you be willing to share the sweater? Or the now-naked yak?

I'm curious to see what you've come up with. My local LLM experience has been... sub-par in most cases.

Post reply on HN