Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| plipplop:start [2024/07/21 15:40] – [Some Problems That Must Be Solved for Plip Plop Programming To Work] gedbadmin | plipplop:start [2024/07/21 15:45] (current) – [Some Problems That Must Be Solved for Plip Plop Programming To Work] gedbadmin | ||
|---|---|---|---|
| Line 19: | Line 19: | ||
| Designing such a system presents an interesting architectural challenge. | Designing such a system presents an interesting architectural challenge. | ||
| - | ====== | + | ====== Problems That Must Be Solved ====== |
| - | * You cannot turn it off and on again | + | * How do you fix problems when you cannot turn it off and on again? |
| - | * You cannot predict everything that is going to happen over such a long time | + | |
| * How do you manage change to code that runs over months and years? | * How do you manage change to code that runs over months and years? | ||
| + | * How do you anticipate everything that might happen over such a long time? | ||
| + | |||
| + | Over in the following sections I'm going to explore some novel solutions for these problems. | ||
| + | |||
| + | ===== Robust state that persists over time ===== | ||
| + | |||
| + | ===== Creating new features without breaking existing functionality ===== | ||
| + | |||
| + | ===== Fixing problems when they are encountered ===== | ||
| + | |||