A lot of things in real estate that you might think qualify as just maintenance actually have to be depreciated. Like, repairing a roof has to be capitalized since the roof will be around for awhile. The devops equivalent might be migrating from docker swarm to k8s-- the k8s cluster will be around for awhile.
Software is a liability, not an asset. Treating the construction and maintenance of this horrible liability knows as “code” is a complete misunderstanding of what software actual is.
Are people assets? Certainly not on the balance sheet I hope.
What about a contract? Is a contract an asset? I’m actually curious, not trying to be a smart ass.
A contract can be an asset. Usually the unrealized future value of the agreement has value should you need to make a deemed disposition (or have some other valuation event). It gets very obviously complicated and fuzzy though, which is where accountants make the big bucks. It's pretty rare that a company chooses to make a contract valuable, but it often comes up in bankruptcy proceedings.
As an example of contracts having value, a few years ago I was involved in the acquisition of some media distribution assets, and one such asset was a transferable "MFN" contract with a major publisher. That was a very, very valuable asset.
Others (say, an investor) might view a contract as an “asset” because of the future value it might bring, but not in a traditional accounting sense.
The book value of the k8s work could be completely expensed as soon as it is replaced.
Also, your belief that "software is a liability" is irrelevant. What matters is that tax law calls software an asset (as does most everyone else, even ones who fundamentally understand it).
This is true everywhere and always.
I agree with you, lots and lots of software definitely has the properties of an asset. There’s also plenty of software that’s hastily written, untested, and basically not fit for use beyond a short expiration date. More like a jug of milk with a shelf life than a fine grand piano with resale value.
without someone maintaining it, it would probably fail by the end of month. That's not considering the constant changes going into it.
Not defending this, but in the eyes of the law there's no distinction between products and features and bug fixes.
So this isn't a new thing to track
> 26 U.S. Code § 174(c)(3):
> (3) Software development
>
> For purposes of this section, any amount paid or incurred in connection with the development of any software shall be treated as a research or experimental expenditure.
I don't think it's the same as we do, and more akin to land development and improvement.
This is relatively easy to do. If an engineer is fixing bugs, helping support team, helping sales in any way, participating in customer onboarding, keeping the servers online, etc, a company can argue the engineer is a cost of doing business rather than true "R&D".
In reality, the % of time most engineers spend exclusively on 100% new products is much smaller than you'd assume at face value. Even at a young startup, I'd guess at most 50% of the work is true R&D.
To reiterate, things like devops, managing infrastructure, patching servers, upgrading code, fixing bugs, professional services, etc... none of that is R&D and it's pretty easy for a small company to say that the majority of their engineering expense is not R&D (extremely difficult for the IRS to argue otherwise if they audit a company unless detailed timesheets are kept).