i feel like this is punch card advice, and fails wrt asynchronicity. the tyranny of call-return seems to be alive and well still in many brains. :-)
having said that, i think most async approaches suck because human brains actually rarely are any good at envisioning async consequences... we would need a LOT of much better tooling help in order to not suck at async / reactive / etc.
eg i strongly believe React's attempt at one way Flow is better in terms of being understandable, and maintenanable, than RxJS.