4 ms·

Technical debt of any significance is a product of poorly organized data. If the way you construct your data relationships is poor the product will be poor. T

• dragonwriter 6y ago
  > Technical debt of any significance is a product of poorly organized data. Except on the level where code is data, and so is basically everything else, this is not true. > If the way you construct your data relationships is poor the product will be poor. Probably, but that doesn't support the prior claim in any meaningful way. > All other kinds of debt can be refactored slowly over time if the individual refactoring knows what they are doing. So can APIs and other forms of data organization. It may be somewhat less common for people writing code to be proficient in some aspects of data refactoring, but that doesn't change the fact that it can be done. That refactoring can be done incrementally — that it is possible to pay down tech debt — doesn't, in any case, prevent it from being significant.