Comment by dirtikiti
4 hours ago
Snap opinion made by a software dev who thinks the entire world revolves around software development and this dev's workflow.
There's any number of reasons an org would choose teams over slack, or any Microsoft product over an alternative, even your example of the cost shows a clear lack of knowledge of information outside your narrow scope.
How do you know your org is paying the price you found on a website?
You realize there are other vendors people pay infrastructure contracts through who bundle Microsoft products in their contract?
Stay in your lane.
Then give devs slack or an equivalent alternative? The point the author making is that forcing devs into Teams, because the org uses it, is a red flag. And they’re right.
It’s an indicator that developer experience pales in comparison to bean-counting, and that is an indicator that the business focuses on ROI in the wrong areas.
I’m sure there are finance teams that love it. I work in marketing and I sure as hell don’t, after it using it in two different full-time roles.
It’s as much as a red flag for me as the author.