There's a balance. Like the example the OP gave is abysmal. I do not want that. Have one or two actual sentences and send it, if we're in an actual live conversation. If you can't type that fast enough, take a typing course.

If we're not actively talking, write the whole damn paragraph before you send it! One thing I really dislike is:

    > Hey, how's going?

... some time later ...

    > Can I ask you a question on $TOPIC?

...

Will not get an answer from me. Well maybe once, if we've never talked before and that will be along the lines of "just go ahead and ask, don't bother with the chit chat". Most people 'get' this nowadays but there are some hold-outs. I suppose the hold-outs might be more numerous in non-tech companies or in the non-tech departments of those companies.

You're not alone with this specific gripe. Some of my colleagues include sites similar to https://nohello.net in their staff directory page.

I tend to find the best response to any chat message that boils down to "Hey, can I ask you a question?" is "You just did."

The worst is when I ignore their preamble, waiting on the question and the other person turns around and shoots an email to my manager, cc'ing me and saying 'so and so was away, do you know who I might ask about x?'. Like, no, I was just waiting for you to get to the point!

So much this. I would rather people spit it out than agonize word smithing with me.

I don't know why people treat text as different from speaking.

I read much faster than most people can speak though so I consider stream of consciousness in text as way less demanding than doing it in a meeting.

> if I am waiting

Just don't. It's still asynchronous.