Job titles of the near future:
* Software gardener (the intersection of devops & maintenance)
* Software archaeologist (maintenance of old but important systems)
* Software anthropologist (maintenance of old but important systems whose behavior is confusing)
* Software documentary editor (a software anthropologist that annotates old broken software & its documentation for software historians)
* Software historian (studies old versions of software to make it understandable to modern users)
* Software etymologist (traces the genealogy of terms, processes, ideas, and systems)
* Software entomologist (classifies bugs and studies their behavior; offshoot of security research)
* Software ecologist (studies the interactions of vast numbers of huge, ancient systems)
* Software zoning manager (controls what software is allowed to exist based on concerns about stability raised by software ecologists & software historians)
* Software reenactor (usually a hobbyist; uses emulation to reenact important historical events like the flash crash of 1986, the Morris worm, and the Fuzzy Bear APT, sometimes for museums, schools, or local festivals)
* Software mythographer (studies the myths and folklore surrounding pieces of software, particularly its cultural impact; internet memes are primary sources)
* Software plumber (a software gardener who fixes things software ecologists notice are broken)
* Software exterminator (a software gardener who identifies and removes systems that pose a risk to the ecosystem or to services of historical interest)
* Historic Software Registrar (keeps a list of historically interesting or important pieces of software & services, and preserves them; an archivist, but one who keeps old code running as well)
* Software cartographer (works with software ecologists to understand & document data flows)
Ꮢ๐ϲoᴄo Ⅿoԁｅm Ᏼaｓіliｓk