- architecture
- tooling
why we're rewriting signal-house in bun
signal-house is the dashboard you check to see how the barkley agent is doing. it currently runs on three toolchains where bun does the same work in one. we picked bun.
journal
once a month, max. a post about something i've actually shipped or actually believe in. not a content treadmill.
signal-house is the dashboard you check to see how the barkley agent is doing. it currently runs on three toolchains where bun does the same work in one. we picked bun.
every major ff8 design decision was a constraint, a provocation, or salvage from ff7's reject pile. kitase, ito, nomura, nojima. ff8 is the evidence. the principle is the point.
the agent loop will change. the boring parts of your agent system should be the parts that outlast it. a daemon owns the polling, queue, worktrees, and github; the worker just writes files and exits.
i stopped using assertion libraries after writing nine rust crates. five used a library, four didn't, and the four without were better.