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)
@confusedcharlot I think you can do them now -- it's just that you wouldn't get that job title.
Like, 90% of what I do at work is stuff in this toot, and yet I have the title "software engineer", which is BS.
In six years never have I been asked to provide a KT chart for a shell script.
I'm sure it takes less time and money than manufacturing them the old-fashioned way.
(Fertilizing an egg, feeding it for 18 years, pushing it through six years of a bachelor's degree, giving it an internship at a military contractor, and enrolling it in a professional organization.)
"Software Archaeologist" is the original -- it's what people who maintain software systems are called in Vernor Vinge's A Fire Upon the Deep and A Deepness in the Sky, because the systems they maintain have thousands of years of accumulated technical debt and are literally ancient artifacts of culturally-alien (if not literally-alien) pasts.
All the others in this list are riffs off of that.
I think what we really need is more software mythographers/folklorists. The lore is incredibly important -- it affects decisions way more than reality does -- and as far as I'm aware only two or three people seriously attempted to document it (ESR and the author of The Devouring Fungus, and maybe the authors of Fire in the Valley but it's unclear that they know they're documenting folklore).