3 ms·
Thought exercise: if you wanted to write code to support a business or nonprofit, and you knew that the software would be used for many years, and probably neve
by peatmoss 8y ago
Thought exercise: if you wanted to write code to support a business or nonprofit, and you knew that the software would be used for many years, and probably never see an update, and wouldn’t have anyone to tend network services, how would you build it?
Me, I'd probably go with a static executable with a terminal UI and a flat file sqlite database that could be copied by mortals, and hope that whatever I set up as a backup regime would survive future migrations to new hardware.
- smacktoward 8y agoA fascinating idea -- kind of a software analogue to the 10,000-year clock (https://en.wikipedia.org/wiki/Clock_of_the_Long_Now https://en.wikipedia.org/wiki/Clock_of_the_Long_Now).