←back to thread

858 points cryptophreak | 2 comments | | HN request time: 0.001s | source
Show context
taeric ◴[] No.42934898[source]
I'm growing to the idea that chat is a bad UI pattern, period. It is a great record of correspondence, I think. But it is a terrible UI for doing anything.

In large, I assert this is because the best way to do something is to do that thing. There can be correspondence around the thing, but the artifacts that you are building are separate things.

You could probably take this further and say that narrative is a terrible way to build things. It can be a great way to communicate them, but being a separate entity, it is not necessarily good at making any artifacts.

replies(17): >>42934997 #>>42935058 #>>42935095 #>>42935264 #>>42935288 #>>42935321 #>>42935532 #>>42935611 #>>42935699 #>>42935732 #>>42935789 #>>42935876 #>>42935938 #>>42936034 #>>42936062 #>>42936284 #>>42939864 #
dapperdrake ◴[] No.42935321[source]
Email threads seem better for documenting and searching correspondence.

The last counter argument I read got buried on Discord or Slack somewhere.

replies(4): >>42935388 #>>42935429 #>>42935749 #>>42935911 #
al_borland ◴[] No.42935911[source]
I find things get buried just as easily in email. People on my team are constantly resending each other emails, because they can’t find the thread.

This is why, if something is important, I take it out of email and put it into a document people can reference. The latest and correct information from all the decisions in the thread can also be collected in one place, so everyone reading doesn’t have to figure it out. Not to mention side conversations can influence the results, without being explicitly stated in the email thread.

replies(2): >>42936068 #>>42936944 #
1. kmoser ◴[] No.42936068{3}[source]
> This is why, if something is important, I take it out of email and put it into a document people can reference.

This is how things should be done, regardless of which medium is used to discuss the project. Without isolating and aggregating the final decision of each thread, there is no way to determine what everybody has agreed upon as the final product without looking back, which quickly becomes onerous.

Things get messy when you start having different versions of each feature, but that doesn't change the concept of using email/Slack/Discord/text/etc. for discussion and a separate "living" document for formalizing those decisions.

replies(1): >>42936749 #
2. 6510 ◴[] No.42936749[source]
Lets toss in a minimum number of [digital] signatures.