This is almost a year behind Steve Yegge's first post on beads. Gas Town and Gas City provide orchestration for the swarm. So far I haven't seen a perfect implementation but this idea isn't new.
I don't think Gas Town was actually all that much ahead of the curve - see Cursor's swarm post from January this year, mentioned at the very top of this blog post.
I also don't know that beads is a very strong example that Yegge knows what he's doing - it's famously been described as (pseudo)malware.
Everything Steve yegge has done has been trash. That's why nobody is talking about beads or gas town. It was clear even in the beginning that it was a borderline AI-psychosis-fueled trash fire.
I think if you're suggesting that Steve Yegge somehow invented having agents collaborate, you're way off base. People started talking about agents collaborating very, very early on, and people have been doing experiments like this for ages. There have been libraries to build e.g. graph-based (possibly multi-agent) workflows from the early days, before even structured output was a standard thing in the APIs.
The only thing Yegge did was come up with really stupid, convoluted and anthropomorphized language to describe the process and then write unhinged articles about it
For real concentration I can't have lyrics but that's a great idea for other flow states. Mozart and Brahms are good for me ... Not slow enough to put me to sleep not fast enough or unusual to make me pay attention to the music.
I vary a lot but when I do classical music Mozart has occupied quite a lot of my stats, in particular a clarinet concerto by Katherine Lucy [1] and also things like Beethoven's 6th (pastoral, it's beautifully featured in Fantasia) or Grieg's morning mood.
If this site actually provided privacy-preserving recommendations, there are many of us in the U.S. who would (or should?) also be interested in these services. Sadly, this is SPAM.
You had to be careful with MySQL back then as constraints were syntactic sugar but not enforced. PostgreSQL was indeed much tougher to manage but more full-featured.
Really, you've always had to be careful with MySQL. It really was the PHP of RDBMSs.
The silent "SHOW WARNINGS" system, nonsense dates like Feb 31, implicit type conversions like converting strings to 0s, non-deterministic group by enabled by default, index corruption, etc.
Not just constraints, transactions were also a no-op. The MyISAM engine is still available in modern versions if you want to experience this, it's just not default anymore.
Yep, I've had to work with a MyISAM project with no transactions - it's a reasonably simple system thank goodness but a little scary all the same (and lots of boilerplate to deal with partial failures).
I love Postgres in 2026, but it really was not a viable enterprise option before 2010. MySQL had decent binlog replication starting in 2000 which made up for a lot of the horrible warts it had.
Not to mention there was Percona, and both Google & Facebook contributed a number of patches that made monitoring MySQL top notch (such as finding slow running queries, unused indexes, locks etc.).
