So long Slack. It was great while it lasted.
I have yet to see anything that got better because it involved Salesforce.
I have yet to see anything that got better because it involved Salesforce.
As far as I am aware they had python 3 available a long time ago (long before the competition) and they have beta versions of some tools so you can test in advance.
There's nothing wrong with IRC if you are trying to solve the problems of IRC. They don't solve the business problem as well as slack does. Slack is Slack because of search and an easy to use client with a universal extension set.
If it’s internal just stick an ELK stack behind an authentication proxy it’s 20 minutes of work, an hour most with the addition of a log bot which joins public channels.
This is for IRC though, better options exist for things like Zulip or Matrix. (non-exhaustive list, obviously)
Side note though: I find it weird that this is the bar. It comes up every thread but it’s tantamount to a “ha! Gotcha!”, because no -sane- messaging system logs its history in a way that is retrievable immediately because indexing -all that content- is expensive and better off being centralised; additionally chat history (almost by definition) loses relevance quickly.
It’s almost certainly an anti-pattern when you feel the need to refer to things you said 2 years ago, immediately, in the same client you used to write those things.
I don’t know how you’re using slack though, so I guess it’s pretty central to your flow.
EDIT: am I wrong? Is this normal? Someone correct me please if you’re not happy with what I say.
Documentation is the key. Wikis. Code comments. Bug/issue trackers. I've never considered walking up to someone's desk, and talking to them, as something I need documented, and searchable.
And that's what slack/irc/IM/etc is to me. Walking up, and talking to someone at a desk.
Not to mention, if you want any REAL functionality with Slack, you have to pay. And you thereby outsource all backups, and additionally loads of confidential conversations to an external company.
Which then cuts you off if you cancel your account!
Most of the people I know who use Slack, use it "because that's why SV uses".
That requires people to write them and unless there's a strong managerial hand poking constantly, it's often "there's no time right now, we'll do it tomorrow" and, as we know, tomorrow never comes.
Yet Slack isn't really the answer. Frankly, Slack is inept management's attempt to fix their own, and employee's, shortcomings.
Having a new on-board use some search function on Slack, to look through 100s of hours of conversation for "random important things", isn't going to fix that. Nor will people sifting through that junk, help when some bonehead didn't backup, or document key vital parts of a config. Or code.
If it's important, it needs to be documented. Not be stuck in a deluge of endless blather, random docs, zero real version control, the list goes on.
Ah well.
Just been through that and I 100% agree. Unfortunately my push for "everything needs more documentation" has not succeeded because "we don't have time to document stuff!"
I'd imagine someone could write an extension to Hexchat to integrate it directly into the client.
How likely is that scenario? Chat is far less organized compared to email or forums and it's difficult to find the result you're looking for unless you've seen it and have a vague memory of what it was and when it was posted.
When I try to use Slack's search feature, I typically get a bunch of irrelevant results. In fact, I've had better luck scrolling back and finding the message I'm looking for.