NSF Wants To Know How Much Software Really Costs
eldavojohn writes "It's no secret that the actual cost of software is very complicated. Sure, the companies that write software are spending money on it, but when that software is released, it doesn't stop costing money. You can probably think of a number of relatively tiny things that add up — especially if you're a system administrator — like the man-hours spent patching software to avoid a nasty infection spreading quickly. The bigger debt is that old piece of software you paid a bunch of money for back in 1998 that you're critically dependent on, but it has no support and hasn't been updated in years due to any number of reasons. Well, the National Science Foundation paid Gartner almost half a million dollars to find out what it truly costs to bring an organization to a fully supported environment. According to Gartner, this hidden liability or 'IT debt' is at $500 billion worldwide right now, and in five years it will be at $1 trillion. Along similar lines, a company called Cast that makes software quality tools reported that your average business application comes with a million in IT debt (PDF). And if that's not misapplied enough for you, they estimate that the debt is $2.82 per line of code in the application and also that it's on average higher in the government sector."
Many companies are transitioning to general purpose software as the features expand. High debt software is often replaced with an off the shelf solution with a much lower cost.
As examples, at home, I no longer use Photoshop. Gimp is the replacement. Open Office replaced MS Office. Natulus replaced Nero or EZ CD Creator. Ubuntu replaced Windows on most machines. I don't pay for expensive upgrades when possible. Many small companies are making the same move.
Only one machine has the MS Debt software for the few things that just have to have it. I no longer upgrade high debt software on the various desktops and laptops we use.
Ernie Ball figured this out years ago and published his story online.
http://news.cnet.com/2008-1082_3-5065859.html/
The truth shall set you free!
The NSF wants to know something about the computer industry and they ask Gartner? Gartner, the company that advocated OS/2 and I-CASE?
Because what happens when the "cloud" shuts down? What happens when your internet goes down and you can't even access what should be local files? What happens when the "cloud" has a major security breach and all of the files that normally wouldn't ever leave your company are now able to be downloaded to crackers everywhere?
Taxation is legalized theft, no more, no less.
Software cost = programmer's salary ... ... ... ... ... ... ... ...
+ the cost of the computer the programmer used to write the code
+ the cost of the electricity to power said computer
+ the cost of the software the programmer used to write the code (which may be $0)
+ the salary of the QA staff that test the code
+ the salary of the documentation staff that write the documentation for the code
+ the salary of the HR staff that hired the programmer, QA staff, documentation staff, etc. and ensures they receive their paychecks
+ the rent/mortgage payment for the office where the programmer, QA staff, documentation staff, and HR staff work
etc.
I wonder why /. does not have a section on economics. Isn't it long overdue to have one?
So many stories really belong in economics.
We could discuss what things are worth.
We could point out stories that appear on front pages of various portals and news sites and discuss what really is going on behind the title on them, just like the title I linked to:
Stocks Rise on Renewed Hope for Fed Action
- which sounds as if it is a positive for the economy that stocks rise on 'Hope for Fed Action', when in reality, those who understand can tell you that "Fed Action" means more money printing/borrowing, which implies more inflation and debt, so rising stocks (and rising gold) in this situation means that there is an expectation of yet more inflation, so stocks will go up in nominal terms, but all US holdings will lose more purchasing power.
Isn't /. 'news for nerds' and isn't economy yet another 'nerdy' subject?
You can't handle the truth.
Wait a minute. I'm a manager, and I've been reading a lot of case studies and watching a lot of webcasts about The Cloud. Based on all of this glorious marketing literature, I, as a manager, have absolutely no reason to doubt the safety of any data put in The Cloud.
The case studies all use words like "secure", "MD5", "RSS feeds" and "encryption" to describe the security of The Cloud. I don't know about you, but that sounds damn secure to me! Some Clouds even use SSL and HTTP. That's rock solid in my book.
And don't forget that you have to use Web Services to access The Cloud. Nothing is more secure than SOA and Web Services, with the exception of perhaps SaaS. But I think that Cloud Services 2.0 will combine the tiers into an MVC-compliant stack that uses SaaS to increase the security and partitioning of the data.
My main concern isn't with the security of The Cloud, but rather with getting my Indian team to learn all about it so we can deploy some first-generation The Cloud applications and Web Services to provide the ultimate platform upon which we can layer our business intelligence and reporting, because there are still a few verticals that we need to leverage before we can move to The Cloud 2.0.
"Its okay, this project/software is using 'internal resources'"
"Say, Jim, would you mind working a few extra hours for the next 14 weekends in a row? I know you're salary, but we'll make it up to you once this project is done..."
And that, my friends, is how you completely ignore hidden costs and justify even the most lingering of projects.
At least at my company, anyway.
Which all pales in comparison to....
+ the cost of managements bonuses.
May the Maths Be with you!
"Technology debt" (or "technical debt") is referred to as a debt because it has effects that are very similar to financial debt. First, it has a cost to resolve, which is analogous to the principal of a financial debt. Second, it has imposes ongoing costs until it is resolved, which works like the interest on a financial debt. Thirdly, the starting value of the cost to resolve -- the principal -- is often greater than the costs which could habe been paid out of pocket initially instead of incurring the debt, making it analogous to the various initial costs associate with many financial debts.
The "technical debt" terminology was invented by people who understood the technical problems and the consequences (mostly, of trying to minimize the initial costs of developing or acquiring technology-based solutions to business problems) as a means of explaining the issue to managers and executives, who generally understand financial concepts like "debt" much better than they understand technical processes.