jessmartin
Joined 18 years ago
Karma
418
Submissions
125
Member since
Aug 18
Recent submissions
Comment · 1 month ago
Start with Jayber Crow.
Then read Hannah Coulter.
Then the whole Port Williams collective will open before you like a beatific field.
Comment · 2 months ago
Philosophy and CS double major here, love reading old books. Read a lot of theology and ancient literature. Homeschooling my kids, part of the curriculum is learning Latin.
Comment · 5 months ago
Waiting for “JSONL is all you need for durable workflows.”
Comment · 6 months ago
Agree. I ~never see that stuff.
Comment · 6 months ago
I love the idea of using a shared event log for coordination. Smart!
I have a Symphony-style[1] factory, which keeps all the context in a single session, but I want to start splitting into stations with separate sessions, and I hadn’t worked out how to do communication between sessions.
Comment · 7 months ago
Really cool to see JSON Canvas getting attention. (Hi, kepano!) It was one of the inspirations for OCIF (Open Canvas Interchange Format), which we've been working on since JSON Canvas came out.
JSON Canvas nails the simplicity-it's easy to read and easy to implement. We wanted to build on that spirit while tackling some of the challenges showing up in this thread: nested canvases, extensibility for custom app data, text styling, coordinate systems, and round-tripping between different canvas apps without data loss.
OCIF v0.7.0 just came out. It's designed to be an interchange format — so different canvas tools (Excalidraw, TLDraw, Obsidian, etc.) can export/import each other's canvases.
Some highlights:
- Extensible: apps can attach their own data via extensions, so nothing gets lost even if the features aren't supported
- Nested canvases via parent-child node relationships
- Local coordinate systems (addresses the pixel positioning concerns raised in another comment here)
- Text styling, viewport control, and more via built-in extensions
If JSON Canvas isn't quite meeting your needs, OCIF[1] might be worth a look.
Comment · 7 months ago
strong agree. I always have the LLM put an actual markdown doc in a docs/plans/ folder before starting work. I often, but not always review it.
Aside: it also helps for code review! Review bots can point out the diff between plan and implementation.
Some examples for the curious: https://github.com/sociotechnica-org/symphony-ts/tree/main/d...
Comment · 7 months ago
none yet!
Comment · 7 months ago
Not a small amount :)
I spend $140/mo on Anthropic + OpenAI subs and I use all my tokens all the time.
I've started spending about $100/week on API credits, but I'd like to increase that.
Comment · 7 months ago
I got my own level 8 factory working in the last few days and it’s been exhilarating. Mine is based on OpenAI’s Symphony[1], ported to TypeScript.
Would be happy to swap war stories.
<myhnusername>@gmail.com
Comment · 8 months ago
I wonder if this is just a byproduct of factories being very early and very inefficient. Yegge and Huntley both acknowledge that their experiments in autonomous factories are extremely expensive and wasteful!
I would expect cost to come down over time, using approaches pioneered in the field of manufacturing.
Comment · 8 months ago
They have a Products page where they list a database and an identity system in addition to attractors: https://factory.strongdm.ai/products
For those of us working on building factories, this is pretty obvious because once you immediately need shared context across agents / sessions and an improved ID + permissions system to keep track of who is doing what.
Comment · 8 months ago
I’ve been building using a similar approach[1] and my intuition is that humans will be needed at some points in the factory line for specific tasks that require expertise/taste/quality. Have you found that the be the case? Where do you find that humans should be involved in the process of maximal leverage?
To name one probable area of involvement: how do you specify what needs to be built?
Comment · 9 months ago
Wow. This is exactly my kitchen faucet. Which makes sense, because my house was built in 1961.
Works great. Amazing how durable the faucet is!
Inventing tools for a better tomorrow.