171–180 of 840 posts
I find it amazing that we can be about an hour and a half into a service being completely unusable(ie. Slack telling me it 'cannot connect'), yet it's still marked as an 'incident' instead of an 'outage' in their own status page
It's funny that this isn't considered an "Outage" by their status page's standards.
Earlier quoted context omitted.
A lot of organizations essentially took the last two weeks off from work, which is long enough for a 10-day autoscale window to spin down servers, and then get confronted by a load spike that wasn't pre-spun for.
I would be shocked if Slack operations wasn’t aware of this return to work spike and didn’t pre-scale in anticipation.
EDIT: And down goes Notion, too: https://news.ycombinator.com/item?id=25634159
Earlier quoted context omitted.
> But migrating everything is _so painful_ This is a key point is the popularity amongst VCs in investing in B2B SaaS. I take their (and your) word for it. But honestly, I don't actually understand this. Why is migration so hard?
Many reasons, almost none of them technical. Off the top of my head, a few: * Getting out of the Enterprise Contract, or waiting for the year to end. * Training people on new software. * Loss of productivity. (1) Learning a new UI, processes, workflows -- both individually and organizationally. A feature or concept in "Tool A" may exist in a completely different form in "Tool B". Or not exist, and then people need to…
Man it bothers me so much when applications change their UIs on updates for no apparent reason other than "it looks better".
IntelliJ changed the way build and debug buttons looked in some update and it took me days to get used to it and I could find them in a snap again. Slack did a couple of no-reason changes as well.
Earlier quoted context omitted.
I haven't worked at Slack, so I can't speak with high confidence. A traffic spike is a possible reason, but I'm willing to bet that it's not the reason: > Doubt anyone releasing big changes Monday morning. This is definitely an engineering best practice, and by best practice, I mean something that Uber's, I mean Slack's SRE team strongly pushed for, and got politely overruled on. After a code freeze is lifted, it's q…
Does Uber/Slack not release in CI/CD? At least in backend? I don't see any need to deploy a big change at once in the software world today. At worst feature gate the thing you want to do and run it in a beta environment, but still push the actual code down the pipeline.
Every Uber/ex-Uber engineer is nervously chuckling at this comment right now
Earlier quoted context omitted.
I think there should be a new computer science law (if this one doesn't exist already): Things that are easy to migrate from get replaced by things that are hard to migrate from, eventually. IRC is incredibly easy to migrate from.
IRC is easy to migrate from since there is nothing to migrate other then chat history. IRC is also missing so many features that slack provides out the box. And a law like that would not work since you would need to write complicated transformation scripts to transform between services. Also not all services are a 1-1 mapping. I like IRC but it has its limitations. That is why slack succeeded where IRC did not.
The parent meant a law as in "a law of physics", not a piece of legislation.
Earlier quoted context omitted.
What does an incognito browser have to do with anything?
An incognito browser would ignore all client-side cookies, so the Slack web client would not try to - say - resume a previous user's session or re-use any previously saved data. Likewise, incognito mode will also ignore most cached web content, meaning all assets on the Slack web app will get loaded again from scratch. This "clean state" start could, theoretically, get around issues with old - potentially incorrect/o…
Other data points: * iMessage was taking its sweet time sending a few texts this morning. * I had momentary trouble trying to call a business from my Verizon phone, and someone I know had trouble calling from AT&T. Could just be a coincidence, but I wonder if something larger-scale is happening.
* Todoist MacOS app is having trouble talking to its API