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
"Functional shell, imperative core".
1
Replying to @gdb
minimize state in code and in life
Replying to @gdb
Have found this to be so true! I would also add, make dependencies explicit.
1
Replying to @gdb
If this is GPT I’m impressed
1
Replying to @gdb
can i have the private api key for open ai codex? plz big brother Greg
Replying to @gdb
art of the state software design
Replying to @gdb
100%. And in the context of a single program, state updates should happen in a minimum number of places and as high up in the call stack as possible.
1
Replying to @gdb
Many a time the initial development with less idea of the problem being solved is bloated with code and data. If you are willing to relook at the problem, then a lot of those bloat can be eliminated with sometimes total rewrites instead of continuing to work on it.