I think of it as a request for a context switch. If you're mentally occupied - writing a tricky recursive function, say - and somebody walks up and says, "Hey, what's the time complexity of inserts into a red-black tree", it's likely that just parsing the question will kick you out of your current context so you lose track of what you're doing.
Back when I was TA'ing a course in college, about half of the students on average in office hours would start their conversations with me by saying "I just have one small question." I'm not sure what was worse, when they didn't just have one question (or it wasn't small) or when the question was so small they could have gotten an answer by the time they finished assuring me that they weren't going to take up much of my time.
Re: "no hello", I'm not fully with it. Some developers enjoy a more human-like interaction which doesn't play into the unfriendly programmer/BOFH stereotype. Lack of testing will cost the company a lot more time and have more damaging effects than people saying hi to each other (which could be argued to be worth the little extra time it takes to play out):
One pet peeve is people who ask "can I ask you a question?" - this doesn't have the same positive benefit as "hey, how's it going? how was your wknd?", it doesn't seem to serve any purpose. I typically ask people, nicely, to just ask the question directly next time and I'll answer when I'm able, if can't right away. Especially in a chat-type environment in a geographically/timezone-diverse team.