[hn_throwaway_99]

There is so much misunderstanding about the amortization of software dev costs rule (and yes, I see your correction).

I've worked in large and small companies in my career, and nearly every large company desperately wanted devs to count as much time as possible as capex (vs. opex). Reason being that, if you're a growing software company, counting dev salaries (often your largest expense) as capex can make you look a ton more profitable, which is of course good for your stock price and valuation (indeed, counting opex as capex is one of the oldest frauds in the book - it's what brought down WorldCom 20 years ago). It's just that, in a modern software company, it's really hard to separate any individual dev's time into separate capex vs opex buckets. The reason I hated capitalizing my time as a software engineer is because the line between capex vs. opex is gray beyond belief for modern SaaS companies that do continuous delivery.