The limitations of Twitter's design today, and how it's hard to structure conversations:
miniblog.
Related Posts
One subtle behaviour of Claude that wasn't obvious to me: whilst each conversation is transient, permissions persist across conversations.
So if you've given permission to run e.g. 'cargo test' or even 'cargo run', you need to be sure that all future invocations are safe too.
You can see the current permissions with /permissions.
I've had a ton of great conversations on Twitter: there's a bunch of programming expertise (even programming language design) here. There are niches here that don't exist elsewhere.
I've also found a great job through Twitter on two occasions.
No idea what the future will be. https://twitter.com/_wilfredh/status/1592389610457673729
Excellent discussion of verbosity (many keywords), orthogonality (scalar vs record expressions, calling conversations) and semantics (bizarre equality for NULL) in database query languages, focusing on SQL: https://edgedb.com/blog/we-can-do-better-than-sql/
(Uses 'design by implementation' as derogatory!)