nathants

how are bite sized models going to solve bad writing?

coding agents, co-agents, and coco-agents.

Just exchange json.

Backend in python/ruby/go/rust.

Frontend in javascript/typescript.

Scripts in bash/zsh/nushell.

One upon a time there was a low amount of friction and boilerplate with this approach, but with Claude and Codex it’s changed from low to none.

400 - 128 = 272. Codex cli source.

Usable input limit has not changed, and remains 400 - 128 = 272. Confirmed by looking for any changes in codex cli source, nope.

TTL=1day

Just have SES put the email in s3, then do stuff.

Interesting. I'm not trying to restore bootable systems, just data. Still, probably worthwhile to rebuild in Go soon.

Definitely similar.

Git LFS is 50k loc, this is 891 loc. There are other differences, but that is the main one.

I don't want a sophisticated backup system. I want one so simple that it disappears into the background.

I want to never fear data loss or my ability to restore with broken tools and a new computer while floating on a raft down a river during a thunder storm. This is what we train for.

This is cool. Do you always --link-dest to the last directory, and that traverses links all the way back as far as needed?

Perl still exists?

How do you version your rsync backups?