Earlier quoted context omitted.
> we'd be in a much better place what code-archaeology is concerned. This sounds like a great setup for a sci-fi novel. 500 years into the future, the infrastructure their distant ancestors coded has begun to fail. Now Biff Miffington, code-archaeologist, must sift through millions of forgotten messages using a mysterious tool remembered only as "git." Its interface is arcane and the remaining messages broken, tainte…
Testing the waters, I'd played with the idea of a story with basically this setup: Two new developers start at a company/startup, and are brought in to do a six-month sprint to fix a stalled/broken product after the development team becomes unavailable because reasons . So, they're dropped into a codebase and are trying to pull everything together. However, as they work through into deeper and deeper parts of the sys…
Every member of the programming team was attacked and killed by wolves in unrelated incidents on the same night.
And they said it couldn't happen...