Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

amusingly, my understanding is that the original goal for slack was to be an archive.

slack originally stood for: searchable log of all communication and knowledge

but then in practice, i saw message retention locked down to 30 days or less, which kinda defeated the point.

other modern tools, like trello, also seemed to have gaps when it came to logging/searching/archiving what happened. trello is fantastic for organizing "what needs do", "who do", and "when done"... but in my experience is pretty terrible for "what happened" and "why". this is fine i think at smaller scales, but once complexity starts to scale up, it can be a nightmare. it's hard enough fighting issue hysteresis (reoccurring issues and bugs that drag on for years) when there's good historical views and explanations.



Doesn't slack have full history if you pay for it? We use Teams and I regularly find myself searching for stuff I remember I was sent months ago.


It does and today I just learned that there are some companies that don't store all messages sent. Slack works great at my company, I can search for things a year or more back and even write messages to myself as a form of note taking.


My company has slack archives going back ten years. They imported everything from the old chat system.


I don't know of any productivity tool that handles archiving well. You can store done tasks in some way, but all the context is lost. Over time, it's annoying even on a small - individual - scale.


I think Azure DevOps handles context pretty well. I can look at old tasks and see associated commits, conversations, and related work.


yeah, the info is there and you can do the same with most tools, but it often requires a lot to extract it. how well organized is it? how hard is it to go from line of code to complete discussion around when it was last changed?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: