
This is me thinking aloud about a thing that is very specific to my life and situation but maybe useful to someone else for something but not really about you, it's just me trying to articulate without needing to edit or fear throwing casting a Wall of Text spell on the work Slack.
So. Short version. A computer doesn't know anything it has not been told.
I mean, neither does a human, but, importantly, humans learn passively, all the time. We know stuff no one ever set out to teach us (and we don't know WHY we know it, which is a whole thing all by itself).
This can lead to interesting failures.
Long Version.
My job these days is to collect stuff from addresses. Which means, I drive a big cargo van to a specific street address, get stuff, and then drive to the next address on my list. On any given day, I will do this 100+ times. I work on a team, so there are about 30 of us doing this each work day.
That is a lot of addresses.
And ideally, the each address is as close to the last and the next as possible. We have a program that generates the routes, and a Real Human Person who reviews the routes. However. There are at least 30 routes, every day, with specific parameters (not all the routes are the same). What I am saying is, the system is not perfect, there are mistakes. Things like "to get from Here to There, I would have to go under an overpass that is too short for the actual vehicle, so I have to drive around, taking much longer"). Things the computer generating the route would not know, having not actually driven on the actual streets in the actual vehicles we use. In fairness, not something that a Real Human Person would necessarily know, either.
Which is why there is a feedback channel, where we tell Real Human Person (RHP) about issues like that.
So, with that in mind, knowing that as I do. Yesterday. I was sent to pick up from an address at the Ass end of a one lane street on the extreme Northeast corner of Seattle. Right up against the lake. And I am driving, as noted, a cargo van, so NOT a small or agile vehicle, and DOES NOT have a small turn around radius. I did this pick up once before, and tried to pull into a driveway to get turned around. And that driveway was loose gravel, and it was raining, and I was stuck there for more than two hours. Great fun. Lesson learned.
I got the pick up, got turned around (a classic 14 point turn, just like they teach in drivers ed), and I was on my way to the next address. It was on a completely different street. But as I was driving, I noticed that there was a house that seemed to want a pick up from me. It wasn't the next pick up, though. SO, i looked at my whole route, and there that address was, five or six stops away.
I was able to make that pick up, and, being Smart, I looked at the rest of my route, and saw that there were four more stops on that same street. I got all those, and then resumed my route as written.
The thing I noticed, though. Some people write their address as "Street Name Here East". And some people write "Street Name Here E". And, this being Seattle, where we have 5437 streets, and 243 street names, EVERYTHING is East Street, or Street West (and each of those has the most tangential connection to each other (to say nothing of the fact that street numbers are not always sequential, or we skip numbers, or replace numbers with names and then resume numbers, right where we left off (such that 10th ave is, in fact, Nine full blocks east of Ninth ave (Street naming conventions in Seattle are the subject to a long, detailed, and angry rant all it's own (and don't even get me started about how house numbers are hidden))))). What I realized, yesterday, is that the program we use probably doesn't know that those two streets (Street Name East and Street Name E) are the Same Thing. Likewise, and at the same time, a RHP wouldn't Know that the computer DOESN'T Know that. A RHP looks at the addresses, and doesn't even think once about how those two addresses are on the same street, because OF COURSE they are. RHP Doesn't need to think about that, RHP is Busy and has better things to think about.
And that is how I end up going on The Street of Doom Northeast, leaving it, and then Returning to Street of Doom Northeast.
Computers don't know anything they have not been told. And People don't necessarily know that they know stuff that a computer would NOT know. There is nothing that is obvious to a computer; A computer (and obviously i am using "computer" in the broadest possible sense for a computer program or App or AI or algorithm or whatever the current technology is here; I don't know the correct word and it is not important to the thing I am trying to articulate) only knows what someone told it to know, and lacks the foundational experiential knowledge that all RHP get (which is NOT remotely the same from one RHP to the next, of course; But everyone has stuff they know that they were not taught in the former structure of education, just as a product of being alive for this number of years).
So, when the RHP looks at the routes each day, that RHP needs to keep that in mind.
Except I don't know how the RHP does this job (there are certainly tools and considerations I don't know about). I don't know, for certain, that the computer hasn't been told that Street Name NE and Street name NorthEast are the same street (the glitch I experienced yesterday could be something else entirely).
So. In specific, I have questions about how a thing I work with works. In general, I have thoughts about what we know, how we know it, and what we take for granted that "everybody knows" so much that we don't even question knowing it.
Also, Holy Shit, Snow.