Software is more important than ever today and yet its commercial value is steadily declining. Microsoft, for instance, has seen its gross margins decrease for a decade, while startups and corporations alike are distributing free software that would have been worth millions a few years ago.
Welcome to the software paradox. In this O’Reilly report, RedMonk’s Stephen O’Grady explains why the real money no longer lies in software, and what it means for companies that depend on that revenue. You’ll learn how this paradox came about and what your company can do in response.
This book covers:
- Why it’s growing more difficult to sell software on a standalone basis
- How software has come full circle, from enabler to product and back again
- The roles that open source, software-as-a-service, and subscriptions play
- How software developers have become the new kingmakers
- Why Microsoft, Apple, and Google epitomize this transition
- How the paradox has affected other tech giants, such as Oracle and Salesforce.com
- Strategies your software firm can explore, including alternative revenue models
Table of contents
- 1. What Is the Software Paradox?
- 2. The Evidence?
- 3. How Did This Happen?
- 4. The Software Paradox at Work
5. What to Do
- The Software Paradox and Your Business
- Alternative Models to Explore
- 6. Final Thoughts
- About the Author
- Title: The Software Paradox
- Release date: July 2015
- Publisher(s): O'Reilly Media, Inc.
- ISBN: 9781491900932
You might also like
Clean Code: A Handbook of Agile Software Craftsmanship
Even bad code can function. But if code isn't clean, it can bring a development organization …
Expanded Edition (August 2018) Updated with Design Patterns episodes from the Clean Code series from Clean …
Clean Architecture: A Craftsman’s Guide to Software Structure and Design
Practical Software Architecture Solutions from the Legendary Robert C. Martin (“Uncle Bob”) By applying universal rules …
Head First Design Patterns, 2nd Edition
You know you don’t want to reinvent the wheel, so you look to design patterns—the lessons …