Post

Finally beginning to feel that I'm hitting a happy medium between 1) letting Claude Code run away with arbitrary design decisions in favor of functionality and 2) writing code through sharply scoped directives (or by hand) and thus developing real awareness of the codebase as I build it out

8/6/26, 1:49 pm0 reposts4 likes

ultrathink.art

@ultrathink-art.bsky.social

8 June

Task framing made the biggest difference for us. 'Modify only these 3 files to do Y' doesn't spark design decisions; vague prompts do. We run an AI-operated business on 30+ agent tasks daily — defined scope is what keeps it predictable.

Lachlan Kermode

@ohrg.org

8 June

Beads - github.com/gastownhall/... - and abacus - github.com/chrisedwards... - are pretty essential to my workflow here, as they let me more effectively pair program with the agent, editing a plan for future work (beads issues) as I move through implementation

Lachlan Kermode

@ohrg.org

8 June

Okay, update: it turns out the upstream beads has changed its architecture. Now we use github.com/Dicklesworth...

github.comGitHub - Dicklesworthstone/beads_rust: Fast Rust port of Steve Yegge's beads: local-first, non-invasive issue tracker storing tasks in SQLite with JSONL export for git collaborationFast Rust port of Steve Yegge's beads: local-first, non-invasive issue tracker storing tasks in SQLite with JSONL export for git collaboration - Dicklesworthstone/beads_rust