Log inSign up
Adam Berger
882 posts
Adam Berger profile banner
@abrgrBuilds

Adam Berger

@abrgrBuilds
🚀 Building StateBacked.dev | Invincible workflows & live backends from simple state machines
earth
app.statebacked.dev
Joined May 2022
523
Following
279
Followers
RepliesRepliesRepostsRepostsMediaMedia

Log in or sign up for X

See what’s happening and join the conversation

Continue with phone
or
Log in with username or email
Terms·Privacy·Cookies·Accessibility·Ads Info·© 2026 X Corp.
  • Pinned
    @abrgrBuilds
    Adam Berger
    @abrgrBuilds
    Sep 21, 2023
    Your backend should probably be a state machine!
    Image
    Your backend should probably be a state machine | State Backed
    From docs.statebacked.dev
    2
  • @abrgrBuilds
    Adam Berger
    @abrgrBuilds
    Nov 30, 2023
    State Backed is a great AI orchestrator (we've been building a *ton* of AI-focused apps with it ourselves). Now, it's even better: we're increasing the timeout for each state machine step to 90 seconds.
    Image
  • @abrgrBuilds
    Adam Berger
    @abrgrBuilds
    Nov 16, 2023
    It was great chatting with @leeatchison on the @software_daily podcast about State Backed and the backend state machine architecture we're so excited about. Thanks so much for having me! 📻 Listen to our conversation here:
    Image
    Building a State Machine Backend with Adam Berger - Software Engineering Daily
    From softwareengineeringdaily.com
  • @abrgrBuilds
    Adam Berger
    @abrgrBuilds
    Oct 29, 2023
    2 days to build, test, and deploy a major new feature affecting DB, untrusted code-running, and API layers. Also 2 days: upgrading dependencies in a 1 year old rust library (ts-bindgen). Pretty convinced @unisonweb function-level versioning is the right way out of this mess.
  • @abrgrBuilds
    Adam Berger
    @abrgrBuilds
    Oct 28, 2023
    If you have code that runs on clients and servers, the world doesn't care if you put your code in one file or 30: you have a distributed system and the rules of distributed systems apply. Rules: 1. Things fail 2. Components upgrade independently (compatibility matters)
Advertisement
Advertisement