4 ms·

I think Steve somewhat predicted the future well. He might be slightly off, because he is overly optimistic and operates at the edge, but look at Gas Town, when

I think Steve somewhat predicted the future well. He might be slightly off, because he is overly optimistic and operates at the edge, but look at Gas Town, when it was released it felt like dystopian, today it looks not too far away, I am sure most of your orgs are already running some kind of agent to triage the tickets and in some cases automatically open the PR in your git repo. I think he is onto something this time as well

threecheese 23d ago
This weekend I stumbled across a codebase unlike anything I’d ever seen: Swamp Club[]. Came out of nowhere, lots of useful features, but with a coherent philosophy and architecture and a large body of working code. Change volume is high - notably so, but it looks nothing like the vibe slop I’d expected. A “swamp” contains tools that you build - with the help of agents - intended for use not just by apps and scripts, but agents (to add deterministic behavior, like code mode). Tools are ops things, product things, whatever. *And so it’s a tool plus a factory to update the tool.* The factory though isn’t only used for building your tool - that’s just a set of skill.md files. It can build your whole app, which itself can _use_ your tools - either for product features or ops tasks. *And so it’s a factory that can build any app, including a tool which can operate any app. * Right now, looking at the commit volume of the swamp stuff, it’s not stupid to suppose that the swamp is being used to create the swamp. *And so it’s a factory which makes, among other things, factories.* We’re cooked. - https://swamp-club.com/use-cases https://swamp-club.com/use-cases