551–560 of 1001 posts
Thousands of teen coders now hate Salesforce in advance . This is very shortsighted.
Even $5k/year seems insane to me for hosting what is essentially an IRC channel...
Earlier quoted context omitted.
Wait, there are people who actually don't hate Salesforce?
My sales people love it.
This is at a fortune 500 company.
Thousands of teen coders now hate Salesforce in advance . This is very shortsighted.
Thousands of teen coders now hate Salesforce in advance . This is very shortsighted.
That's a 40x increase all at once with a very short grace period, it's bait-and-switch territory. If only 2.5% of targets pay the ransom, Slack breaks even on this racket, so in absence of any protection this strategy is most likely profitable for Slack. This is something you pull if you want to squeeze in the short term, and don't mind losing customers.
Thanks for doing the math. Imagine being the analyst who was paid to optimize this or (infinitely worse?) the executive who demanded it.
It's hard to imagine being GPT-4o.
Earlier quoted context omitted.
> Also, if the data in chat is being held hostage, the org might be using chat wrong. This is so important these days. A lot of project send users to discord, slack for documentation and help but they are not made for this purpose. Searching in chat channel for a specific problem is not a good way to handle documentation. I can't even use search engines to search that.
> Searching in chat channel for a specific problem is not a good way to handle documentation I just wanted to highlight this. I am so happy seeing this written down explicitly and finally. Throughout the years I struggled so much finding relevant and accurate information about a feature of a product because it was scattered in chat channels, inadequate for providing reliable data (out of date or uncertain staleness,…
So why don't all of these people simply write it down in a notion/document store and meticulously keep it all up to date?
Because the business does not want that. We demand efficiency, so we understaff engineering departments sufficiently that there is always a little crunch, so that slightly-too-few engineers have to work slightly-harder-than-they-want to make the business successful. The end result of this intentionally engineered "lack of time" is that things like maintaining meticulous documentation are ignored, and the only time the knowledge is shared is in a frantic slack message.
The business is designed to do this. It's not laziness. It's the standard operating procedure to increase efficiency and profit.
Thousands of teen coders now hate Salesforce in advance . This is very shortsighted.
Are there any coders that like salesforce in the first place? This is firmly one of those ‘foisted on you by management’ kind of products right?
Since you're a nonprofit that teaches coding, it could be a great time to consider self-hosting a FOSS chat tool. Suggestions: Campfire [0] or Zulip [1]. Also, if the data in chat is being held hostage, the org might be using chat wrong. Right tool for right purpose. If starting over, perhaps consider if it would make sense to put that documentation or whatever it is that will get "lost" from Slack into a wiki or rep…
I think it is time we all start moving away from renting software back to owning it (or at the very least, owning a perpetual license). The subscription model is does not exist on a stable plateau. Every company that runs on a subscription model will (and must, by virtue of incentives) to attempt to "develop new revenue streams".
Earlier quoted context omitted.
Funny, this post got me wondering how much the k8s slack cost! Do you have any references where I can read more? I didn’t hear about that
Best place for info is probably the announcements channel on Kubernetes slack. that’s a link which is a good place to start https://kubernetes.slack.com/archives/C9T0QMNG4/p17500871180...
> UPDATE: We’ve received notice from Salesforce that our Slack workspace WILL NOT BE DOWNGRADED on June 20th. Stand by for more details, but for now, there is no urgency to back up private channels or direct messages.