Visual programming and executable models
Farzad Yousefzadeh
Farzad Yousefzadeh
Lead Engineer @Stately
Feature programming
Feature programming
Feature programming improved v1
Other improvements
Enter Diagrams
Benefits of diagrams
👉🏻 See entire system
👉🏻 Edge cases
👉🏻 Zooming
👉🏻 Plan and estimate
👉🏻 Integrations
👉🏻 See layers
Diagram types
👉🏻 Hierarchy (spawning)
👉🏻 Sequences
👉🏻 Multi actor (event drive)
purchase only items exist in cart
a part of logic that needs to be checked only if a parent condition is met
Continuous integration
Multi step consent form
separate modules or functions
cloud functions, web workers, k8s pods
Actors
Diagrams show you how the software you're building is a collection of actors structured in a certain way
If diagrams are so good, why not just diagram the software instead of programming it?
Stately.ai
Your entire software can be a collection of graphs
Stately.ai
Finite state machines
Statecharts
state ==> state
(state+ event) ==> next state + side effects
How is Stately different
👉🏻 Diagrams are the source of truth
👉🏻 Diagram ➡ model ➡ execute
👉🏻 Export to more than just code
👉🏻 Import from more than just code
👉🏻 Multi-purpose
👉🏻 Across the stack
Diagrams to the next level
👉🏻 Generate event sequences
👉🏻 Collaborative
👉🏻 Smart reshaping by analytics
Recap
👉🏻 Diagrams improve modeling
👉🏻 Diagrams are low code and abstract
👉🏻 Diagrams can be the single source of truth
👉🏻 Diagrams are not enough
👉🏻 Start diagramming for new features
👉🏻 Start diagramming when refactoring