For someone who worked on recommendation systems, you really don't seem to understand the concept of an "algorithm" across the abstraction of multiple systems a

For someone who worked on recommendation systems, you really don't seem to understand the concept of an "algorithm" across the abstraction of multiple systems and at different layers of the stack you worked on. In fact, a lot of people here really think what people are talking about is the equivalent of what is handled in a subroutine. No, what people are talking about when they talk about "the algorithm" is anything affecting the result set they're reading. Concepts like eventual consistency and edge computing are... well... a part of a model which laypeople, and even reasonably technical people call an "algorithm." Being pedantic about whether or not this happens in an SQL query, or across multiple codebases, or by region, doesn't escape the question.