I’m curious why in chapter one the concept of “calling a method” is advocated rather than “sending a message”?
In the Pragmatic Programmer’s article “OO in One Sentence: Keep It DRY, Shy, and Tell the Other Guy”, Andy Hunt and Dave Thomas stress “[A]s an industry, we’ve come to think of software in terms of function calls. Even in OO systems, we view an object’s behavioral interface as a set of function calls. That’s really not a helpful metaphor. Instead of calling software a function, view it as sending a message.”