I’m excited to welcome George Kierstein to speak at Clojure SYNC.
We’ve got a problem. It’s called bit rot. We have some working code. We don’t run it for a few months. And when we try to run it again, it doesn’t work. How did that happen? The system it was running on changed enough (packages upgraded, libraries deleted, passwords changed, permissions, hardware, IP addresses, ……..) that it just doesn’t work. The only way we know how to keep software working is to pay someone to run it all the time. It’s a bit like in the Dark Ages where you had to have monks copy books to keep the skill of reading and writing alive, and also to stave off the natural entropy (fires, rotting, losses, etc.) that would befall the books. There has to be a better way.
Here’s George’s abstract:
Can we store code and expect to ever get it to run again? Perhaps for a year or two but what about 10? 20? How we can begin to reason about the problem domain? Taking a page from climate science, this talk explores models to better frame the problem which could provide insight into how to design systems that can outlast us.
George Kierstein will talk about this problem and a solution she came up with to mitigate some of the challenges with archiving software for the indefinite future. We’re spending more and more time creating software. If it’s so important, maybe we should think about how to keep it.