121–122 of 122 posts
Earlier quoted context omitted.
Not at all, reread what I wrote. It's getting the data model wrong for the problem at hand.
You admit yourself the data model is ("80% of...") the product.
Earlier quoted context omitted.
The difference though is that financial debt is very easy to measure and quantify but technical debt is not. I like the Tetris analogy because that game has a type of debt that anyone who has played it can understand, yet is not as easily quantifiable as financial debt.
And I might add: what is technical debt in one project, maybe isn't in another project. Engineers sometimes want to overengineer things that would work just fine in that situation. I remember an old link about someone studying the source code of a game (Doom maybe) expecting to find beautiful solutions for every minor problem when in fact he was surprised by how most of it was straightforward. Check what needs to sca…
(bonus: write your code like the next person to work on it is a psychopath and they know where you live)