A universal design trick in software: make as much of your application stateless as possible, and concentrate your persistent state in a central, simple, perhaps unscalable solution (database, custom process). State is a fundamentally-hard part of software, so work to minimize it

Apr 27, 2022 · 7:05 PM UTC

17
43
2
389
Replying to @gdb
github.com/papers-we-love/pa… is a classic in the genre
2
Replying to @gdb
True of both symbolic systems and of neural ones.
1
12
Replying to @gdb
Why not work with functional paradigm altogether?
Replying to @gdb
old web
Replying to @gdb @yawaramin
BINGO in one of my prototypes all of the state is persisted to a JSON file. cuz it Just Works & is good enough for now. I know how & (approx) when to refactor into a SQL database, or whatever is better for longterm but single file, single Thing, even a single ref root is ideal
Replying to @gdb
I just use sqlite for everything.
1
1
Replying to @gdb
Good practice is to push state out into components naturally susceptible to failures, like client. If it fails no one will care about the lost state anyway.
1