Re:GitHub staff are required to use Teams by Sep 1, 2023
by apnew on Monday February 13, 2023 @03:07PM
(#34779559)
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?
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?