3 ms·
> product-oriented companies (i.e. where code is an asset > IT (i.e. where code is liability You got it backwards. In companies that sell code, code is an asse
by eeZah7Ux 9y ago
> product-oriented companies (i.e. where code is an asset
> IT (i.e. where code is liability
You got it backwards. In companies that sell code, code is an asset.
In companies that sell services code is a necessary evil.
- uiri 9y agoI think you misunderstood him/her. If you're a software developer and you're part of the "IT" department, then you're a liability. Your code is a necessary evil. If you're not part of the "IT" department, then you're working in a product-oriented environment where the company is selling your code (either as a good or as a service) or otherwise making money from the code. In that case, your code is an asset.
- fredophile 9y agoI've always understood it as functionality is an asset and code is a liability. The company wants and uses the functionality to make money. Code has to be maintained, has bugs, etc. Your goal should be to provide the required functionality while reducing the costs incurred by your code.