I love the terms "programmer-at-arms" and "programmer archeologist." I wish more people read this book, so I could use the term and not have people look at me with a blank look in their eyes.
The above excerpt is actually an accurate description of what I do at my day job! ("program archeology") My coworker, who's been working on and off with this code base for over 12 years, never fails to point out if any of my ideas was already implemented once before. So far, everything I've suggested since starting this job 3 months ago has already been done in the past.
My job title at a previous job was Software Archaeologist, inspired by ADitS. Though my boss then went on to explain it to a customer more as an Indiana Jones of programmers than as someone working on old and crufty systems.
