It's funny how coding agents really lack self-awareness when making time estimates. They're just spitting out the timelines they've seen in the training data. Here they estimate 1-2 weeks for something that will take 30 minutes at most.

GM

Trick for when you want the AI to make a good spec

gm

a smart phone that runs debian

FuriPhone FLX1s Linux Phone

Shop

Shop - FuriPhone FLX1s Linux Phone

!robot what time is it?

On our flight to Madeira for Sovereign Engineering, I asked @Paul how he liked his dinner via bitchat and @vnprc responded instead. Didn’t even know he was on the flight 😂

GN

Catholics have some funny saints

git worktrees are extremely useful when you're running concurrent coding agents. Last couple days I made this[1] little `vibe` bash script that you can call like `vibe ~/code/ziggurat "please make me a nostr rely in zig"` and it will - create a tmux session called "vibe" if one doesn't already exist - create a tmux window in the "vibe" session - use gpt-4o-mini to summarize your prompt into 15 chars and use this as git branch, git worktree and tmux window name. neat thing here is that i'm reading the api key out of 1password cli: `OPENAI_API_KEY=$(op read "op://cli/openai/configs" 2>/dev/null)` - launch claude code with the prompt Now my workflow is that I usually have ~5 agents running at once in a tmux session. The tmux window name at the bottom changes color when the agent stops running (forgot how i did that lol). Pretty slick. [1]

Gist

vibe

GitHub Gist: instantly share code, notes, and snippets.

If you want to help me and @Paul re-write the entire Nostr ecosystem in Zig, please apply to Sovereign Engineering

Sovereign Engineering

Sovereign Engineering

The program that brought you Blossom, Nutzaps, Wikifreedia, Nsite, TollGate, Zapstore, and more...

I want to start a podcast but don’t know anybody who laughs good enough to be my sidekick