4 ms·
> That's an unbalanced conclusion. Code can be a liability but it can also be an asset. maybe that's why he said: > Not only a liability, but a liability amon
by c0vfefe 7y ago
> That's an unbalanced conclusion. Code can be a liability but it can also be an asset.
maybe that's why he said:
> Not only a liability, but a liability among other things.
- jasode 7y ago>maybe that's why he said: > Not only a liability, but a liability among other things. It was my mistake then and I misinterpreted "among other things" to mean : "Code is not just a liability but it's a liability among the other things I just listed like limited resources and limited brainpower" instead of "Code is a liability among other things I won't say explicitly like code also being an asset". Because I interepreted it the 1st way, I wanted to emphasize the opposite view: that limited brainpower is why code can be an asset to relieve humans from mundane boring calculations to redirect that precious brainpower to higher level creative thinking. Limited resources also motivates new code that can be an asset to expand those resources.
- c0vfefe 7y agoI can understand being confused by that wording, it wasn't the greatest. :)