apnew

I 100% agree with you about bringing that experience in-house.

My comment was reaction to the fact that there is a forced migration without 1:1 parity in feature set. Most large orgs/teams in my experience heavily rely on automation that has been added over the period of time reduce the cognitive load that is accidental/side-effect. Now if you are going to force them to move; give them a migration path.

Think of this in terms of API contracts. If half of the methods in your new version are not even available; why even make the new API public?

Literally sitting here right now trying to figure out how to get simple things going compared to slack after being forced to move to teams from slack (not GitHub).

I am all for dogfooding here, but if the dog-fooding is not improving the product it shows that the goal is to eat market because of lopsided ecosystem monopoly. Screw MS and MS Teams.

eg. : We need a tag in a shared channel so that we can provide single point of support for other teams, instead of people having to tag the whole channel. Slack made is as easy as breeze to sync on-call person from PD -> a group.

> Last June, the Navy divers, operating under the cover of a widely publicized mid-summer NATO exercise known as BALTOPS 22, planted the remotely triggered explosives that, three months later, destroyed three of the four Nord Stream pipelines, according to a source with direct knowledge of the operational planning.

The third paragraph in the article.

Corey, just wanted to let you know I really appreciate your work. You have been a great source of knowledge over past few years.

TIL! Thank you.

Personally, I think this would be fantastic.

Interesting, TIL.

I am assuming, you are talking about something like this https://www.youtube.com/watch?v=kokO6XqJvAE. If so, it's not sand, it's salt.