State machines are super underrated: they make complex logic explicit, impossible states impossible, and agents are extremely good at making them now ๐ฏ
Also, Matt is a state machine expert
I think I'm addicted to getting agents to build state machines
Every time I see an agent has built a state machine (or even just a reducer) I can feel a huge bump in the robustness
And I know that future updates will be trivial and testable
Would recommend for frontend
Introducing Expand Fetch, a new way to scrape and crawl the web.
Your agent has never seen the web. No wonder it gets basic questions wrong.
Traditional Markdown APIs lose critical details. So we trained two System one models to change that:
Iris, a vision model that sees
was at a community event and was asked a somewhat sad question: should developers be afraid of the labs eating the new possibilities jev opens up?
with AI (system one) + software (system two):
1. there's no going back to a world without system one models
2. you control the
Instead of .md specs, try this: make the system a state machine (or rather, a reducer). Ask your slopus to make an interactive diagram with real events from your flow and the real reducer. Step through them, asking the agent "whys" this and that.