3 ms·
When I was back in school, around 2007/2008, I remember reading one of those 'future-of-work' type articles where the author went on about how teams of the near
by jmknoll 11y ago
When I was back in school, around 2007/2008, I remember reading one of those 'future-of-work' type articles where the author went on about how teams of the near future were going to keep each other updated via Twitter. Given the early direction of the product, it seemed like a foregone conclusion.
"@devTeam @productTeam @PMNameHere Currently building out remaining API endpoints. Complete by standup tomorrow #productName"
It feels like Slack ate what should have been Twitter's lunch. I don't understand why they didn't push harder in this direction.
- toyg 11y agoObsessed with becoming an advertising company for the masses, they stopped "productizing" their technology. Amazon doesn't stop other people from selling stuff with AWS servers, but that's basically what Twitter did when it destroyed its own developer ecosystem. The parallel with Slack is very apt. The only real strength of that platform is how easily and freely it integrates with third-party services. If Skype, Facebook or Twitter allowed that freedom and ease, Slack would have never appeared. Instead, they want to maintain an iron grip on who does what (or endorse a model where your corporate sysadmin maintains such grip, like Skype For Business does), and they lose.