Build, protect and deploy apps across any platform and mobile device
Deliver Awesome UI with the most complete toolboxes for .NET, Web and Mobile development
Automate UI, load and performance testing for web, desktop and mobile
Rapidly develop, manage and deploy business apps, delivered as SaaS in the cloud
Automate decision processes with a no-code business rules engine
Build mobile apps for iOS, Android and Windows Phone
A complete cloud platform for an app or your entire digital business
Deploy automated machine learning to accurately predict machine failures with technology optimized for Industrial IoT.
Optimize data integration with high-performance connectivity
Connect to any cloud or on-premises data source using a standard interface
Build engaging multi-channel web and digital experiences with intuitive web content management
I figured that since David Bressler did a gratuitous blog posting about his Macbook Air that I needed to do the same about mine.
Now, I'm not a Mac fanboy. This is the first Mac I've owned and I got it mostly for its size and weight since I travel a lot. To be honest, it's probably less reliable than my old XP laptop. The machine itself locks up or crashes about the same amount, and some of the apps (like MacMail) clearly have some annoying bugs in them compared to what I ran on Windows (Outlook).
But, the one thing it beats my old box on is responsiveness. I used to be able to go out for coffee while XP was coming out of sleep or hibernation. But, with the Mac, it takes me longer to type in my password than it takes for the machine to wake from sleep. Starting applications follows the same pattern. Slow on XP versus lightening fast on the Mac.
What does this have to do with SOA? Very little (that's why I called it a gratuitous blog entry after all). No, in reality, it teaches some important lessons: In you can focus on excelling in quality of service, it's probably more important than having the most bug-free services and applications.
Users will reward you for recognizing that their time is important. They can usually figure out how to work around bugs. And, after a while, the workaround becomes second nature to them. But, when something is slow across the board, there are no workarounds: Given the opportunity, users will switch or just not use the system altogether.
So, the next time you're building a service, think carefully about where you put your focus and resources. You have the opportunity to make your service consumers a lot happier with you.
View all posts from dan foody on the Progress blog. Connect with us about all things application development and deployment, data integration and digital business.
Copyright © 2017 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.