story time. redis has a command called KEYS, which goes through every key. it’s a debug command, only to be run against an offline copy of your database. one day many years ago, a rails-lad at GitHub was on a machine trying to do some analysis via the ruby redis client..

guy at the function said he was learning Latin to read Marcus Aurelius “in the original”. was disappointed when I told him the Meditations were written in Greek.

the idea of guido asking chatgpt how to do mcp + embeddings!

I remember the first time I visited us-east-1. About 1973-74 I think. Around the first Oil Crisis. All in the Family biggest show on TV. The machines were humming along, but you could tell, even then, there was stress on the infra. Too much traffic, not enough thought. So it goes

LLM is good at search, summarizing Wikipedia, writing acceptable code, talking confidently while making some subtle mistakes. that’s about your average Stanford grad so I’m saying ASI achieved

have been informed all my useful open source work would “be a hit” if written in typescript. so yeah, alright. kit.js and sandboxes.js coming next week.

supply-chain attackers salivating

this is how I write b2b saas

now published; enjoy at

New in kit 2.1.3, with contributions from the community: - tree-sitter support for @ziglang - improvements & better batch size control for vector search cased-kit is a toolkit for code mapping, symbol extraction, code search + more, so you can build production AI devtools.

catching up on lovable drama

https://t.co/S4lgElEyu1

one of the sadder things that has happened in tech “discourse” is the amount of attention given to VCs, to rounds, and even to founders. the best words used to be from engineers; not founders and *absolutely* not from capital, but from people who worked.

It’s interesting (and a little jarring!) to see how opinions have changed about why to do open source. With some exceptions (that tend to prove the rule), open source is often assumed to be exclusively a go-to-market strategy (if you’re a company) or a résumé-builder (if you’re

a handful of important, correct commits and correct direction-setting from a truly senior engineer is far better than 5000 slop commits in the wrong direction.

sql over http is insane, and PS is (wisely) doing this just to take customers. no further investment should be made. do not standandize an vile anti-pattern. put your database close your app. talk to it over the ordinary secure protocol of the database. it's not hard.

this is the usual obvious click-bait shit that is destroying technical discourse. GitHub has enough problems, there’s no need to rage-bait for clicks.

“startup incubator” was not meant to be taken literally

when that dude wrote “rich dad poor dad”, I always wondered how the poor dad felt

This is actually a pretty profound thing if you're doing infra work. Traditionally you can turn all sorts of quality knobs to maintain availability. You can turn off an overloaded app feature, but keep the site up. Go read-only for a time. Force free users to the back of the