Why is undefined constantly climbing?

Question

JavaScript

I work with node.js. There is this design:

var result = findUserByHash('hash', function(user){
            console.log (user);
            return user;
        });

        console.log (result);

The moment is that everything is fine inside the callback, however, when console.log (result) is called, it shows undefined .
As far as I understand, this is a feature of asynchrony?
It turns out that you need to build the code in a chain of callbacks?

Answer 1

How many fields do I have this asynchrony feature!?

Correctly understood.

It turns out that you need to build the code in a chain of callbacks?

Not necessary. (for nodejs, of course, it has its own specifics, but the general principles are the same, of course).