> 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/2026/03/29.md).

# 20260329

the main thing that pisses me off is when someone says "no, what you made needs to be better"

I received that line early on in the my involvement with shopify stuff, and I received it early on in the development of (foam) the measurement solution

the reaction might be to the idea that their definition of "better" isn't something that I can simulate, and the reviewer isn't offering relationship, so I recoil, looking for a platonic form that - under review - *interacts with* penetration testing and redirects it harmlessly, like aikido

am mulling over how this works, mechanically. the nature of that reflex of mine. it's constitutional, I think. like "ah, 'make this better'? what if I render moot the evaluation of 'better'? I can rest then. I don't know another way to handle 'better' without structuring a business around the ongoing answering."


---

# 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://www.isaacbowen.com/2026/03/29.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.