You are not going to write out many times 'the chief engineer on a project'. So let's take a mostly unused term, like architect and stick with that. (Read 'The meaning Liff' where Douglas Adams is having fun with the reverse of this)
Same thing with RPC, you need to have a term for sending a message to a remote process asking it to execute a particular 'function' and send back the result.
At the same time, you don't want write a lot of code in each application to marshall arguments, send a message, wait for the reply, decode the result. So it seems obvious to generate those functions from a description file. And then you have something that looks a bit like a procedure call that is remote.
Of course at some point the discussion derails and people start claiming that the RPC is basis of distributed computing. And then other people start writing critiques.
That doesn't change the fact that a RPC is a nice concept, as long as you keep in mind what it really is, and what its limitations are.