> For the complete documentation index, see [llms.txt](https://ltkmn.gitbook.io/brendex/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ltkmn.gitbook.io/brendex/essays/different-efficiencies.md). # Different Efficiencies Ask anyone, I am an *efficient* person. Always looking for ways to maximize, organize, realize, conceptualize and fraternize with using less to do more. But there’s many kinds of efficiency. Imagine, if you will, a garden. You walk up from the street and on the other side there’s a cafe in a nice greenhouse. It’s muddy in the dirt from recent rains but there’s a cobblestone path that meanders back and forth from side to side as it eventually gets to the destination. What is efficient? Is it most efficient to walk straight ahead, through the wet earth, in a direct line of conquest towards the cafe? Or is it efficient to take the dry stone path back and forth, never once stepping in the muck. The answer, of course, is a definition of goals: are you trying to get there faster, or trying to get there with clean shoes? So too must we ask these questions of our own goals in everything. --- # 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://ltkmn.gitbook.io/brendex/essays/different-efficiencies.md?ask=&goal= ``` `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.