Recent searches
Search options
I love the term "software archaeology" because it implies the existence of subfields such as "software experimental archaeology" (attempting to reconstruct and demonstrate how people once built software) and "software paleoethnobotany" (quantifying what botanicals were culturally significant to software and the broader historic implications to the societies that wrote it), but also the existence of the broader field "software anthropology" and its offshoot "software sociology", and
You might say to yourself "Aeva, there's no such thing as Software Paleoethnobotany that's absurd", but some day a thousand years from now someone is going to be tasked with analyzing the remains of a surprisingly well preserved set of backup disks for an ancient industrial automation system to reconstruct the lost recipe for brewing the legendary "miller high life"
@aeva In my current project, I often use the term Git Archaeology. Which I think applies here.
- "git experimental archaeology" What problem was this commit intended to solve?
- "git anthropology" What was the culture and pressures that created these design decisions?
- "git paleoethnobotany" WTF WERE THEY ON!?
@aeva My very first job was as a Software Archaeologist back in the mid 90s. Printed on my business card 'n everything!
We dusted off millions of lines of COBOL, PL/I, and RPG to reveal the architecture...
