"FILE WILL BE DELETED AFTER PRINTING"

hah I've never seen that before but reminds me to roguelike games.

"permadeath coding" would be actually fun. IF compiler error THEN erase code repository or something like this

teddyh 36 minutes ago | parent | next [-]

Kent Beck called this “test && commit || revert” in 2018, and credits Oddmund Strømme for the idea: <https://medium.com/@kentbeck_7670/test-commit-revert-870bbd7...>

▲

WillAdams an hour ago | parent | prev | next [-]

Or, just buy the source for a dollar and bury it:

https://www.folklore.org/MacBasic.html

▲

bitwize an hour ago | parent | prev [-]

The source code (and original assets) to many video games from as late as the 90s has been lost. The publishing company often deleted it after the game shipped, thinking it just took up space. This is one reason why, for example, there hasn't been a substantive remaster of Final Fantasy VII.

Also, it sounds like you described Vigil: https://github.com/munificent/vigil

	▲	reaperducer 7 minutes ago \| parent [-]
		The publishing company often deleted it after the game shipped, thinking it just took up space. Floppy disks were not cheap, expensive, easy to get, or reliable. It sucked. Even on the U.S. east coast, I remember having to travel over an hour to get to the nearest store that sold floppy disks. Each BASF FlexyDisk cost $18 in 2026 money. So $50 if you wanted redundant long-term storage of one program. That's why we printed everything out all the time; especially for archive storage. …which also turned out to be a bad idea. Just in a different way.