alt Hacker News> If you're the kind of engineer who reads the implementation instead of trusting the function name, we'd like to talk.
Functional decomposition, combined with good naming, is what allows engineers to raise the level of abstraction and localise understanding of a large codebase.
Without it, if your only option is "read the implementation" for every line of code, you've lost control of the codebase.
What you're saying touches on a real problem, but in this context it doesn't make sense. It's very normal to read implementations you're not already familiar with. Nobody has "lost control" in that scenario. It doesn't have to be the first thing you do - you should just trust the names and documentation when getting a big-picture view of the codebase, but eventually you should read the implementations.
It's healthy to not trust function names - it doesn't mean the whole codebase is out of control.