I think this post points towards something important, which is a bit more than what the title suggests, but I have a problem describing it succinctly. :)
Computer programming is about creating abstractions, and leaky abstractions are a common enough occurrence to have their own wiki page. Most systems are hard to comprehend as a whole, and a human has to break them into parts which can be understood individually. But these are not perfect cuts, the boundaries are wobbly, and the parts “leak” into each other.
Most commonly these leaks happen because of a technical/physical simplification like forgetting that a byte overflows at 255 or electrons have travel time. However, these leaks could happen due to social simplifications too, like getTodayPosts means “the things that get put on the top of the feed” for one and “the things which had the most engagement today” for another. Social errors are often downplayed in technical circles, which is why I think this post has an important message.
I think this post points towards something important, which is a bit more than what the title suggests, but I have a problem describing it succinctly. :)
Computer programming is about creating abstractions, and leaky abstractions are a common enough occurrence to have their own wiki page. Most systems are hard to comprehend as a whole, and a human has to break them into parts which can be understood individually. But these are not perfect cuts, the boundaries are wobbly, and the parts “leak” into each other.
Most commonly these leaks happen because of a technical/physical simplification like forgetting that a byte overflows at 255 or electrons have travel time. However, these leaks could happen due to social simplifications too, like
getTodayPostsmeans “the things that get put on the top of the feed” for one and “the things which had the most engagement today” for another. Social errors are often downplayed in technical circles, which is why I think this post has an important message.