Programming code is usually written with comments, if it's done in good form. This is possibly where the hashtag was first widely used in digital spaces, as the comments always begin with #. The hashtag is necessary so that the program does not interpret the sentence as code. For example, code might look something like this:
# Search spreadsheet and count tax entries from 2006. Word count function using lines, not great lol...
taxes2006 =(grep "tax*" jerometaxes92_19.csv | grep "2006" | wc -l)
echo "The number tax entries from 2006 is $taxes2006"
I've heard stories from telecom engineers who have to fix weird shit in the backlogs of telus, due to some incompatibility with newer tech, which means they have to go through all this old, unintelligible code. These companies never stopped growing and running their show, so instead of improving on old infrastructure, a lot of the time they just built new stuff on top of it. These engineers are looking through the writings of other engineers from a by-gone era. They have different grammar in their code, different functions available to them, different styles, but most interestingly, probably different comments.
Way in the future we might have computer scientists and historians looking into old code to figure out how things were once done. Or old techniques and algorithms now lost to modern knowledge. A lot of this stuff wouldn't be accessible online right? You'd have to dig up an old hard drive from some dusty server from the basement of a Rogers office. That would be the future archaeologist's work.
