Hacker News new | past | comments | ask | show | jobs | submit login

> More importantly valueless code stops being a liability because you can abandon it. Calling it a liability implies it has value.

This is kind of missing the issue though.

Suppose you pay a million dollars this year to develop something that will also cost a million dollars a year to maintain, but is worth over a million dollars a year, so you do it anyway.

So this year you spend a million dollars, make $1.1M, have a profit of $100k. Next year you'll spend a million dollars, make $1.1M, have a profit of $100k. But if you don't do the maintenance, it ceases to comply with changing regulatory requirements and not only has to be shut down but causes you to incur criminal penalties, or develops public security vulnerabilities and then criminals break in and destroy your business and cause you to be sued into bankruptcy by your customers.

In other words, the code creates an obligation that offsets the value of the asset. These two things can easily cancel out so that the total value is ~0 -- or even negative in ways that don't allow you to walk away, e.g. because you entered into a contract to supply this thing for a defined price but underestimated the maintenance cost.

But now the government is telling you that you have something worth most of a million dollars even though it's not worth a dime without putting another million dollars into it -- and even then it still wouldn't be worth two million dollars.

The reason you continue to do it is that the continued development made you $100k this year, not because what you had left at the end of the year that would be worth something without further investment.






Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: