> 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/3-44pm.md).

# 3:44pm

I did it live. I said it, as it happened, in the presence of five friends who are maybe the only total set of five people I could do this in front of.

They were talking about acting gigs, and how you never know about the maybes, you only know about the ones that land.

It came to me very clearly, to be said in the presence of these humans:

*Your life is exactly the same thing.*

*You have no idea how close you came to everything you ever wanted.*

*Time, and time, and time again. You were mostly paying attention to when it* didn't *happen. But you have no idea how close you came, there and there and there and there, to having it happen right in front of your eyes.*

*You have no idea how close you came to everything you ever wanted.*

This is new, as I'm writing this now:

*Everything is about to happen. At every moment,* everything *is on the verge of happening. Take your pick. It's harder to* stop *something from happening, actually. Keeping everything else out of this moment so that you could have the* specific *experience you're having is a fucking difficult job. You're welcome! ;)*


---

# 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/3-44pm.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.
