2 ms·
Modeling code as an asset rather than a liability could create a certain culture that drives you off a cliff. When we were looking at code as an asset, we had
by bob1029 3y ago
Modeling code as an asset rather than a liability could create a certain culture that drives you off a cliff.
When we were looking at code as an asset, we had lots of microservices and sophisticated contracts between them. We advertised this as some kind of inherent product value (it wasn't).
Only once we started thinking about code as a liability did we begin making serious progress with our customers relative to our roadmap.
We do very little in-house code beyond our core product these days. We got away from custom admin web tools, microservices, fancy SQL, etc.
Everything you have to think about is technical debt to me. If you are mentally preoccupied with A, you aren't thinking much about B, C or D. Fewer moving pieces doesn't always mean less code, but it usually does. This also gets into "innovation tokens", etc
- mplanchard 3y agoThis feels in line with TFA to me. The value of your assets were underwater (their liability exceeded their value) because they didn’t match the problem domain of your business. You’ve now jettisoned those liabilities and are focusing solely on the assets that are valuable, because they match up well to the problems you need to solve.
- topaz0 3y agoThe fact that it's an asset doesn't mean its value is proportional to the number of lines that are there. Similarly a house is an asset, but not all 1000 sq ft houses are worth the same amount of money.