We were not literally poor when I was a kid, but my parents had precious little disposable income. The free public library in which they registered me had a strict two-day book exchange policy. If I borrowed a book on Monday, I could not get a new one till Wednesday. It was cruel torture for a book worm like me: I would typically finish the book I borrowed the very same day and would impatiently count the nanoseconds remaining till I was eligible to borrow another book.
Fast forward to 2014 and I am feeling like a stranger in paradise, spoiled rotten by any number of great books, articles, presentations and blog posts on any topic of interest to me – software, chess, military history, classical music, etc. Moreover, I have for all practical purposes access to an “infinite” number of colleagues and friends with whom I can discuss topics of mutual interest ‘real time.’ As a matter of fact, my #1 complaint these days is that I do not have enough time to read and/or discuss all the topics that intrigue me…
It is against this backdrop of inexhaustible reading and intellectual stimulation that I make this strong recommendation for reading Murray Cantor’s just published Self-Insuring Your Software article. It has been years since I last was exposed to such an original concept: the decision to develop your own software is essentially no different than the decision to underwrite your home insurance yourself. It is as simple and as revolutionary as that.
I can rattle about any number of fascinating aspects of the self-insuring your software concept, such as how technical debt fits so nicely in the conceptual framework Murray developed. Rather than doing so, I would suggest you conclude reading my post and jump straight in to Murray’s article. Nothing trumps reading his highly innovative idea in the source.
And, yes, do read it twice! You have my personal guarantee you would not regret it. (Please contact the folks at Cutter if you don’t have access to the article through your license.)