I haven’t kept up to date on Gastown, but I’m familiar with the mindset. A lot of people who want to go all-in on AI start with how they currently produce soft

I haven’t kept up to date on Gastown, but I’m familiar with the mindset. A lot of people who want to go all-in on AI start with how they currently produce software and they try to add AI everywhere they can until things start going wrong. At this point they’ve found the threshold for “we can automate as much as possible without compromising on quality” and they can expand their AI use when models improve. A minority of people like Yegge start by automating absolutely everything possible but still trying to get everything to work, even if it’s low quality. At this point they’ve found the threshold for “as automated as possible while still basically working” and they can improve their quality when models improve. Both sets of people are trying to do the same thing – automate software development as much as possible – but they are approaching it from starting points on the opposite ends of the spectrum. One starts with quality and increases automation; the other starts with automation and increases quality. The latter approach is insane if you have to ship and maintain production quality software, but it’s also where some of the ideas that will be eventually used by the people taking the former approach come from.