Like true archaeology, software archaeology involves investigative work to understand the thought processes of one's predecessors.[1] At the OOPSLA workshop, Ward Cunningham suggested a synoptic signature analysis technique which gave an overall "feel" for a program by showing only punctuation, such as semicolons and curly braces.[8] In the same vein, Cunningham has suggested viewing programs in 2 point font in order to understand the overall structure.[9] Another technique identified at the workshop was the use of aspect-oriented programming tools such as AspectJ to systematically introduce tracing code without directly editing the legacy program.[7]