> For the complete documentation index, see [llms.txt](https://0xn3va.gitbook.io/cheat-sheets/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://0xn3va.gitbook.io/cheat-sheets/linux/overview/philosophy.md).

# Philosophy

The philosophy behind UNIX:

* Write programs that do one thing and do it well
* Write programs to work together (no extra output, don't insist on interactive input)
* Write programs to handle text streams, because that is a universal interface

UNIX also embraced the ["Worse is better"](https://en.wikipedia.org/wiki/Worse_is_better) philosophy.

This thinking is powerful. On a higher level, you can see it a lot in functional programming: build atomic functions that focus on one thing, no extra output, and then compose them together to do complicated things; all functions in the composition are pure; no global variables to keep track of.

Perhaps as a direct result, the design of UNIX focuses on two major components:

* Processes
* Files

{% hint style="info" %}
Everything in UNIX is either a process or a file. Nothing else.
{% endhint %}

## References

* [How Unix Works: Become a Better Software Engineer](https://neilkakkar.com/unix.html)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://0xn3va.gitbook.io/cheat-sheets/linux/overview/philosophy.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.