---
title: "Discussion on \"Road to State Machines Part I\" | Hashnode"
description: "Discussion on \"Road to State Machines Part I\". Let's begin with a very fundamental question whose answer is not so obvious.\nHow to design software that always takes the correct action?\nDesigning Systems When the Past Determines What Is Allowed Nex"
url: "https://hashnode.com/posts/road-to-state-machines-part-i/6ab423709306aef0e3f79d7e"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Road to State Machines Part I](https://webmeister.hashnode.dev/road-to-state-machines-part-i?utm_source=hashnode&utm_medium=feed)

Let's begin with a very fundamental question whose answer is not so obvious. How to design software that always takes the correct action? Designing Systems When the Past Determines What Is Allowed Nex

Sep 23 · 9 min read · webmeister.hashnode.dev  
Read the article

-   [#python](https://hashnode.com/tag/python)
-   [#state-machines](https://hashnode.com/tag/state-machines)
-   [#system-design](https://hashnode.com/tag/system-design)

## Written by

[Can Burak Sofyalioglu](https://hashnode.com/@webmeister)

@webmeister · Istanbul

  
[View profile](https://hashnode.com/@webmeister)

Software Engineer specializing in Python, backend systems, AI, search and web technologies.

Builds backend systems, AI applications, search systems, integrations, automation and web applications. Writes about software engineering and experiments with AI agents, RAG, GraphRAG, state machines, developer tooling and systems programming.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
