Function-Oriented Programming
I think the term "functional programming" is pretty bad. "Functional" is a very overloaded word, and someone could reasonably idea-fit one of its other meanings onto it in context. For example: "functional" as in "works well" or "has practical utility" as opposed to broken or poorly designed or overly focused on aesthetic.
I think we just got the term "functional" because some professor didn't consider problems with actual pragmatic use in day-to-day conversations among working software developers, and we've kept it due to inertia.
So I've started saying "function-oriented programming" instead, because that's closer to a self-descriptive term that working software developers immediately understand. It is a programming style, and techniques, oriented around functions. You might say it's more than that, such as a focus on "pure" functions, but "functional" does not inherently suggest that any more than "function-oriented" does.
