abrgr

7 ms·

1.
by abrgr 9mo ago
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 valuable in the small, doesn't contribute very meaningfu
2.
by abrgr 3y ago
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 a ton of additional guarantees and capabilities around consi
3.
Architecture Is Drawing Lines(docs.statebacked.dev)
1 points by abrgr 3y ago|0 comments
4.
Show HN: State Backed Machine Visualizer Bot(docs.statebacked.dev)
2 points by abrgr 3y ago|0 comments
5.
by abrgr 3y ago
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 well.
6.
by abrgr 3y ago
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 your transition logic in the From impls between the enum st
7.
by abrgr 3y ago
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 can be grouped into parent states, which gives you s
8.
by abrgr 3y ago
Very true!
9.
by abrgr 3y ago
Well put and thank you!
10.
by abrgr 3y ago
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.
11.
by abrgr 3y ago
Thank you! These workflow systems were such an amazing advance over what came before but we can do even better.
12.
by abrgr 3y ago
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 that it's doing what you want it to and it&#
13.
Your backend should probably be a state machine(docs.statebacked.dev)
14 points by abrgr 3y ago|14 comments
14.
by abrgr 3y ago
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 about. Recently opened up access to a backend as a service [0] f
15.
Cohesion *Is* a Good Explanation(docs.statebacked.dev)
1 points by abrgr 3y ago|0 comments
16.
Show HN: React-statechart: OSS components to visualize and edit state machines(github.com)
4 points by abrgr 3y ago|1 comments
17.
Show HN: Multiplayer tic tac toe with nothing but state machines(docs.statebacked.dev)
2 points by abrgr 3y ago|0 comments
18.
Visually building an onboarding flow with 1-command deployment(docs.statebacked.dev)
1 points by abrgr 3y ago|0 comments
19.
Let's build an email automation flow using only statecharts(docs.statebacked.dev)
2 points by abrgr 3y ago|0 comments
20.
by abrgr 3y ago
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 plugin to connect designs to states (didn't rea
21.
The Team Pando flow editor(blog.teampando.com)
1 points by abrgr 3y ago|0 comments
22.
Atoms of Products(blog.teampando.com)
2 points by abrgr 3y ago|0 comments
23.
Building Team Pando in Team Pando(blog.teampando.com)
2 points by abrgr 3y ago|0 comments
24.
A serverless, versioned, local-first data syncing back end(simplystated.dev)
2 points by abrgr 4y ago|0 comments
25.
by abrgr 4y ago
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 comes from an epistemological stance that you can't k
26.
Sorry to tell you this but your epistemology is showing(simplystated.dev)
4 points by abrgr 4y ago|2 comments
27.
F-of-xstate: open-source project to run some logic on your logic(simplystated.dev)
1 points by abrgr 4y ago|0 comments
28.
Show HN: f-of-xstate - query & transform XState logic for metaprogramming(github.com)
2 points by abrgr 4y ago|0 comments
29.
Engineering Is Tradeoffs Right?(simplystated.dev)
2 points by abrgr 4y ago|0 comments
30.
by abrgr 6y ago
Sorry, more investigation prior to mitigation than mitigation. I think moving the lambda aspects of sst to a lambda extension would allow for a workflow like this: 1. Find production issues 2. Replicate production issues in user facing tool

More ›