[nerpderp83]

Chat breaks the flow, flow is necessary for cohesive elegant solutions. If we develop under a state of distraction, we end up making bulldozer-code.

Furthermore, chat is not high quality communication. It is mostly junk comms. If we wanted to encourage communication that moved the organization forward, we would have a structured medium that would automatically populate a knowledgebase.

Chat is not that medium. Chat is shat.

[com2kid]

> Chat breaks the flow,

Until I encounter a problem, switch into chat, and find that someone else already solved that problem and it was archived by the chat system.

Flow maintained.

My chat apps run on a separate monitor that is purposefully not within my visual range of the monitors used when I'm coding.

[quickthrower2]

Then that's asynchronous messaging. Like email.

The thing I hate is the opposite. When I'm told off for not replying to a message. Ergo need to keep it in visual range and stop what I'm doing on each message. Even if it's an inane broadcast from a team member.

[Too]

With chat everybody has the same persistent view. Email everybody organizes differently.

Some people delete emails after reading them, some put in folders, some tag everything, some have an inbox with 100000 unread emails. If I tell a colleague that I emailed them the info a week ago half of them will not find it and just ask me to send it again.

With chat I can just say "it was posted in the QA chat room about 2 weeks ago" and everybody will find the info equally easy.

[com2kid]

> Then that's asynchronous messaging. Like email.

Except organized differently, and easier to author rich content with. And the performance is better, messages are sent instantly. The overall UI is better in many ways.

That said email having subjects makes it different.

[ec109685]

Look at Chat when you have a free moment. Leave the app icon badge on but turn off intrusive pop-up notifications. Problem solved.