4 ms·
> But I'm also like, whatever is stopping it from being faster, I can't imagine what that is from where I'm sitting! Probably a few thousand features you have
by tshaddox 4y ago
> But I'm also like, whatever is stopping it from being faster, I can't imagine what that is from where I'm sitting!
Probably a few thousand features you have never heard of and will never see or use. And the vast majority of their customers will never see or use. But each one has one or two clients for whom someone decided it was vital at the time to implement that feature to please that client.
You can probably imagine one small feature that only one or two clients use that adds a very tiny, almost imperceptible amount of loading time. Now just multiply that by several thousand.
- brewdad 4y agoEasily solved by introducing Teams Lite and Teams Professional. Maybe Teams Lite Plus and Teams Professional Lite. Eventually everyone can get exactly what they need.
- tshaddox 4y agoUntil you need just one of those thousands of features that are only in Professional.
- azemetre 4y agoI mean isn't this the actual problem? That teams are incentivized to pump out features and not delivery quality software? I remember a time in my career where I had to spend a good 2 months coming up with ways to reduce our build time in like 2014/2015. I was lucky to work at a company where most of leadership were engineers with engineering backgrounds but I can only imagine how bad my environment would have been if the room was full of MBAs. Seems like when you hire bean counters and MBAs, the incentive/value structure of your team/org/company changes for the worse.
- pixl97 4y agoCustomers buy features and not speed in most cases. When your customers do that, the MBA's are making you money.
- mike_hearn 4y agoNote though, that Office and Chrome also have many thousands of features and both start nearly instantly.