Viewing profile — abrgr

Great article! > There exists a higher level problem of holistic system behavior verification This is the key observation. Strict, code-level verification of every line, while valu…

Modeling workflows as state machines is incredibly powerful. In addition to everything the author mentioned, the constraints of state machines allow a workflow platform to provide …

This is really cool. Love to see usage of state machines on the backend! It's such a good fit for multi-step LLM apps and a really nice abstraction for generic backend flows as wel…

Rust ADTs and pattern matching are so much better than other mainstream languages I find that once my code compiles it actually is almost always correct. The next step is to encode…

Great points. It's very similar to a DAG you'd make for a workflow but not necessarily acyclic and events can be sent from external sources as well as internal processes. States ca…

Very true!

Well put and thank you!

Thanks! Running systems with this pattern for the past few months, it has been so nice being able to cleanly upgrade instances. The old Joel on Software blog has some gems.

Thank you! These workflow systems were such an amazing advance over what came before but we can do even better.

Great point! State machines are a really nice way to orchestrate multi-step LLM invocations. They're also a great way for LLMs to produce code. It's human-readable so you can vet t…

So happy that others are getting behind this idea. Protecting critical backend state by establishing a state machine that owns it makes so many things so much easier to reason abou…

Love sketch.systems! We built https://www.teampando.com out of a similar love for state-based thinking. We turn natural language requirements into state machines, have a Figma plug…

Thanks for the recommendation. Ontology should take up the most mental effort. Unfortunately, much of the advice in vouge today argues against thinking about ontology. That advice …