3 ms·
Yeah, that really failed for Salesforce and every website ever. And I agree, I really hate it when bugs get fixed without me having to click an update button.
by blazespin 11y ago
Yeah, that really failed for Salesforce and every website ever. And I agree, I really hate it when bugs get fixed without me having to click an update button. That is sooo annoying.
Seriously, how is this the top voted comment???
- rtpg 11y agoI'm more on your side on a personal side, but think if Word 2k3 to 2k7 was an automatic update? All the support requests coming in. The real solution is to do incremental changes in most cases. Though this is a bit troublesome for the whole "I control the code on my machine" thing. In which case you could rip out the updater
- nirvdrum 11y agoThe problem with incremental updates is it's easy to convince yourself they're all beneficial. Most people won't leave your service or app if a new change is slightly annoying. Without attrition, you may not realize the change was essentially negative. Over time these build up and you end up with people that are essentially begrudgingly using your stuff. You can probably grind out a business that way, but it gets hard to upsell or introduce a new product that way. Death by a thousand cuts and all that.
- nirvdrum 11y agoI know a lot of people that are tired of UI changes constantly coming down the pipe in SaaS. But when it's the only game in town, there's not a whole lot you can do about it. There's also a lot of fatigue around release notes that are just "bug fixes and performance improvements." I'll refer you to the massive comment thread about Twitter changing stars to hearts, a change which obviously reached a breaking point for a lot of people. It may work great for you. For a lot of us, it's tiring. It's not as if all these updates end up being bug-free.