> For the complete documentation index, see [llms.txt](https://www.isaacbowen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.isaacbowen.com/2024/04/04/9-28pm.md).

# 9:28pm

My Uber driver had something to say [again](https://www.isaacbowen.com/2024/04/04/12-21pm.md). :) This time it was an engineer driving a Tesla, sharing aloud a nuanced understanding of what is and isn't made under that name.

They made a specific point, almost hesitated to do so, but it was really important to them.

"Have you heard of Herbalife?"

"Woah, that's out of left field, but yes?"

"Right, been around forever, multi-level marketing and people have a problem with that and all *but* they're onto *something*. The way the layers move, and have moved for a long time, it *works well*. There's a responsiveness inside the structure. Tesla's missing that. Tesla has incredible ability to execute, but there's some piece missing inside the structure."

"They're missing care."

"Yeah. Thank you."

They shook my hand.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.isaacbowen.com/2024/04/04/9-28pm.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
